Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1 2 3 4 5 6 7 8 9 10
SIMATIC
Migrating projects
First steps Introduction to the TIA Portal Editing projects Editing devices and networks Visualizing processes (Basic) Using online and diagnostics functions
04/2012
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.
Trademarks
All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Table of contents
1 System overview of STEP 7 and WinCC....................................................................................................17 1.1 1.2 1.3 2 2.1 2.1.1 2.1.2 2.1.3 2.2 2.2.1 2.2.2 2.2.3 2.2.3.1 2.2.3.2 2.2.3.3 2.2.3.4 2.2.3.5 2.2.3.6 2.2.3.7 2.2.3.8 2.2.4 2.2.4.1 2.2.4.2 2.2.4.3 2.2.4.4 2.2.5 2.2.5.1 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.4.1 2.3.4.2 2.3.4.3 2.3.4.4 2.3.4.5 2.3.4.6 2.3.4.7 2.3.5 2.3.6 2.3.6.1 Scaling of STEP 7 and WinCC....................................................................................................17 Options for STEP 7 Engineering System....................................................................................18 Options for WinCC Engineering and Runtime systems...............................................................18 General notes..............................................................................................................................21 General notes..............................................................................................................................21 Notes on the installation..............................................................................................................25 Use of communications processors.............................................................................................26 STEP 7 Basic..............................................................................................................................27 Security information.....................................................................................................................27 Notes on use...............................................................................................................................28 Editing devices and networks......................................................................................................29 General information on devices and networks............................................................................29 Use of modules on the S7-1200..................................................................................................29 Replacing the ET 200S pulse generator and positioning modules..............................................30 Setting flow control for CM 1241 (RS232)...................................................................................31 Removing and plugging Ethernet modules..................................................................................31 Notes on online and diagnostics..................................................................................................31 Compiling the hardware of a pulse generator..............................................................................32 Particular aspects at the CP 1242-7 - Telecontrol interface........................................................32 Programming a PLC....................................................................................................................33 General notes on PLC programming...........................................................................................33 SCL..............................................................................................................................................34 Instructions..................................................................................................................................34 Testing the user program............................................................................................................35 Technological functions...............................................................................................................36 Notes on technological functions.................................................................................................36 WinCC Readme...........................................................................................................................36 Security note................................................................................................................................36 Notes on use...............................................................................................................................37 Migration......................................................................................................................................40 Engineering System....................................................................................................................41 Screens and Screen Objects.......................................................................................................41 Tags and connections.................................................................................................................45 Alarm system and alarm displays................................................................................................46 System functions.........................................................................................................................47 Recipes........................................................................................................................................47 User administration......................................................................................................................47 Communication............................................................................................................................47 Compiling and loading.................................................................................................................50 Runtime.......................................................................................................................................53 Notes on operation in Runtime....................................................................................................53
Readme......................................................................................................................................................21
Table of contents
2.3.6.2 2.3.7 2.3.7.1 3 3.1 3.1.1 3.1.2 3.1.2.1 3.1.3 3.1.3.1 3.1.3.2 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.10.1 3.10.2 3.10.3 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.3 4.4 4.5 4.6 4.6.1 4.6.1.1 4.6.1.2 4.6.1.3 4.6.1.4 4.6.2 4.6.2.1 4.6.2.2 4.6.2.3 4.6.2.4
Notes on operation of panels in Runtime....................................................................................54 HMI devices.................................................................................................................................54 Notes on HMI devices.................................................................................................................54 System requirements for installation...........................................................................................57 Notes on the system requirements..............................................................................................57 System requirements STEP 7 Basic...........................................................................................58 Software and hardware requirements STEP 7............................................................................58 System requirement for WinCC Basic.........................................................................................59 Software and hardware requirements.........................................................................................59 Licenses and Powerpacks...........................................................................................................62 Licenses......................................................................................................................................67 Installation log..............................................................................................................................68 Starting installation......................................................................................................................69 Installing Support Packages........................................................................................................71 Displaying the installed software.................................................................................................72 Modifying or updating installed products.....................................................................................73 Repairing installed products........................................................................................................75 Starting to uninstall......................................................................................................................76 Installing and uninstalling the migration tool................................................................................78 System requirements...................................................................................................................78 Installing the migration tool..........................................................................................................78 Uninstalling the migration tool.....................................................................................................79 Migrating projects........................................................................................................................81 Preparing projects with the migration tool...................................................................................82 Migrating projects with the migration tool....................................................................................82 Calling the migration tool.............................................................................................................84 Creating a migration file...............................................................................................................84 Migrating projects........................................................................................................................85 Displaying the history of the migration.........................................................................................86 Displaying the log file of the migration.........................................................................................86 Migrating WinCC flexible projects (Basic)...................................................................................87 Basics (WinCC flexible)...............................................................................................................87 Migration (WinCC flexible)...........................................................................................................87 Basics on migration (WinCC flexible)..........................................................................................88 Projects from Migrating WinCC flexible projects (WinCC flexible)..............................................90 Compiling and loading a migrated project (WinCC flexible)........................................................92 Migrating engineering data (WinCC flexible)..............................................................................93 Supported HMI devices (WinCC flexible)....................................................................................93 Object support during migration (WinCC flexible).......................................................................94 Changes of values of object properties by the migration (WinCC flexible)..................................96 Migration tags (WinCC flexible)...................................................................................................97
Installation...................................................................................................................................................57
Migrating projects.......................................................................................................................................81
Table of contents
4.6.2.5 4.6.2.6 4.6.2.7 4.6.3 4.6.3.1 4.6.3.2 4.6.3.3 4.6.4 4.6.4.1 4.6.4.2 4.6.5 4.6.5.1 4.6.5.2 4.6.5.3 4.6.5.4 4.6.5.5 4.6.5.6 4.6.5.7 4.6.5.8 4.6.5.9 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.7.5 4.7.6 5 6 5.1 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.3 6.1.3.1
Migration of alarm classes and alarm groups (WinCC flexible)...................................................98 Migration of language-dependent contents (WinCC flexible)....................................................100 Migrating libraries (WinCC flexible)...........................................................................................103 Migrating runtime data (WinCC flexible)....................................................................................104 Migrating runtime data (WinCC flexible)....................................................................................104 Backing up recipe data and user administration (WinCC flexible).............................................104 Restoring recipe data and user administration (WinCC flexible)...............................................105 Migrating integrated projects (WinCC flexible)..........................................................................106 Migrating integrated projects (WinCC flexible)..........................................................................106 Migrating an integrated project (WinCC flexible).......................................................................107 Reference (WinCC flexible).......................................................................................................109 Migration of data types (WinCC flexible)...................................................................................109 Migrating data types of Allen-Bradley DF1 (WinCC flexible).....................................................111 Migrating data types of Allen-Bradley Ethernet IP (WinCC flexible)..........................................111 Migrating data types of Mitsubishi FX (WinCC flexible).............................................................112 Migrating data types of Modicon Modbus (WinCC flexible).......................................................112 Migrating data types of Modicon Modbus TCP/IP (WinCC flexible)..........................................113 Migrating data types of Omron Hostlink/Multilink (WinCC flexible)...........................................113 Migrating data types of SIMATIC S7 200 (WinCC flexible).......................................................114 Migrating data types of SIMATIC S7 300/400 (WinCC flexible)................................................114 Post-editing integrated projects.................................................................................................117 Migrating an integrated project..................................................................................................117 Post-editing integrated projects.................................................................................................119 Converting unspecified CPUs into specified CPUs...................................................................120 Creating an integrated HMI connection.....................................................................................122 Re-linking HMI tags...................................................................................................................124 Deleting an unspecified connection...........................................................................................125 Getting Started Documentation.................................................................................................127 User interface and operation.....................................................................................................129 Starting, setting and exiting the TIA Portal...............................................................................129 Starting and exiting the TIA Portal.............................................................................................129 Overview of the program settings..............................................................................................129 Overview of the script and text editor settings...........................................................................131 Overview of the print settings....................................................................................................132 Changing the settings................................................................................................................133 Layout of the user interface.......................................................................................................133 Views.........................................................................................................................................133 Portal view.................................................................................................................................133 Project view...............................................................................................................................135 Project navigation......................................................................................................................137 Work area..................................................................................................................................140 Inspector window.......................................................................................................................148 Task cards.................................................................................................................................150 Details view...............................................................................................................................152 Overview window.......................................................................................................................153 User interface layout..................................................................................................................156 Keyboard shortcuts....................................................................................................................160 Keyboard shortcuts for project editing.......................................................................................160
Table of contents
6.1.3.2 6.1.3.3 6.1.3.4 6.1.3.5 6.1.3.6 6.1.4 6.1.4.1 6.1.4.2 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 7 7.1 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.7.1 7.2.7.2 7.2.7.3 7.2.7.4 7.2.7.5 7.2.7.6 7.2.7.7 7.3 7.3.1 7.3.1.1 7.3.1.2 7.3.2 7.3.2.1 7.3.3 7.3.3.1 7.3.3.2 7.3.4 7.3.4.1 7.3.4.2 7.3.4.3 7.3.4.4 7.3.4.5 7.3.4.6
Keyboard shortcuts for windows................................................................................................161 Keyboard shortcuts in the project tree.......................................................................................161 Keyboard shortcuts in tables.....................................................................................................161 Keyboard shortcuts for text editing............................................................................................162 Using the on-screen keyboard...................................................................................................163 Special features specific to the operating system.....................................................................163 Influence of user rights..............................................................................................................163 Expanding user rights................................................................................................................164 Help on the information system.................................................................................................165 General remarks on the information system..............................................................................165 Opening the Help system..........................................................................................................168 Searching the Help system for keywords..................................................................................169 Full-text searches......................................................................................................................169 Using favorites...........................................................................................................................170 Printing help topics....................................................................................................................171 Disabling the automatic display of tooltip cascades..................................................................171 Safety Guidelines......................................................................................................................172 The basics of projects................................................................................................................175 Creating and managing projects................................................................................................176 Creating a new project...............................................................................................................176 Opening projects.......................................................................................................................176 Displaying properties of the project...........................................................................................177 Saving projects..........................................................................................................................178 Closing projects.........................................................................................................................179 Deleting projects........................................................................................................................179 Working with multi-language projects........................................................................................180 Project text basics.....................................................................................................................180 Select project languages...........................................................................................................181 Setting the editing language......................................................................................................182 Translating texts directly............................................................................................................182 Translating texts using reference texts......................................................................................183 Exporting and importing project texts........................................................................................184 Application examples for multilanguage projects......................................................................186 Editing project data....................................................................................................................187 Compiling and loading project data...........................................................................................187 Compiling project data...............................................................................................................187 Downloading project data..........................................................................................................189 Comparing project data.............................................................................................................194 Basics of project data comparison.............................................................................................194 Protecting project data...............................................................................................................195 Protection concept for project data............................................................................................195 Revoking access rights for devices...........................................................................................196 Printing project contents............................................................................................................196 Documentation settings.............................................................................................................196 Printout of project contents........................................................................................................197 Changing the print settings........................................................................................................198 Specifying the print layout.........................................................................................................199 Entering document information..................................................................................................200 Managing cover pages and frames...........................................................................................201
Editing projects.........................................................................................................................................175
Table of contents
7.3.4.7 7.3.4.8 7.3.4.9 7.4 7.4.1 7.4.2 7.4.3 7.5 7.5.1 7.5.2 7.6 7.6.1 7.6.2 7.6.3 7.6.4 7.7 7.7.1 7.7.2 7.7.3 7.7.4 7.8 7.8.1 7.8.2 7.8.3 7.8.4 7.8.4.1 7.8.4.2 7.8.4.3 7.8.4.4 7.8.4.5 7.8.4.6 7.8.4.7 7.8.5 7.8.5.1 7.8.5.2 7.8.5.3 7.8.5.4 7.8.5.5 7.8.5.6 7.8.5.7 7.8.5.8 7.8.5.9 7.8.5.10 7.8.5.11 7.8.5.12 7.8.5.13 7.8.5.14 7.9 7.9.1
Designing cover pages and frames...........................................................................................204 Displaying print preview.............................................................................................................210 Printing project data...................................................................................................................213 Undoing and redoing actions.....................................................................................................215 Basics of undoing and redoing actions......................................................................................215 Undoing an action......................................................................................................................217 Redoing an action......................................................................................................................218 Finding and replacing in projects...............................................................................................219 Information on the search function............................................................................................219 Search and replace...................................................................................................................219 Working with text lists................................................................................................................221 Text lists....................................................................................................................................221 Creating user-defined text lists..................................................................................................222 Editing user-defined text lists.....................................................................................................223 Editing system-defined text lists................................................................................................224 Using memory cards..................................................................................................................225 Basics about memory cards......................................................................................................225 Adding a user-defined card reader............................................................................................225 Accessing memory cards..........................................................................................................226 Displaying properties of memory cards.....................................................................................226 Using libraries............................................................................................................................227 Library basics............................................................................................................................227 "Libraries" task card...................................................................................................................229 Using the elements and parts view............................................................................................231 Working with the project library.................................................................................................232 Project library basics.................................................................................................................232 Creating folders in the project library.........................................................................................232 Adding elements to the project library.......................................................................................233 Using elements of the project library.........................................................................................235 Editing elements of a project library..........................................................................................237 Removing elements from the project library..............................................................................239 Filtering the view........................................................................................................................240 Working with global libraries......................................................................................................240 Global library basics..................................................................................................................240 Creating a new global library.....................................................................................................241 Opening a global library.............................................................................................................242 Displaying properties of global libraries.....................................................................................243 Saving a global library...............................................................................................................244 Closing a global library..............................................................................................................246 Deleting a global library.............................................................................................................246 Creating folders in the global libraries.......................................................................................247 Adding elements to a global library...........................................................................................248 Using elements of a global library.............................................................................................250 Editing elements of a global library............................................................................................253 Removing elements from a global library..................................................................................255 Using a supplied global library...................................................................................................256 Filtering the view........................................................................................................................257 Using cross-references..............................................................................................................258 Using cross-references..............................................................................................................258
Table of contents
7.10 7.10.1 7.10.2 8 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.2 8.1.2.1 8.1.2.2 8.1.3 8.1.3.1 8.1.3.2 8.1.3.3 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.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.5.13 8.1.6 8.1.6.1 8.1.6.2 8.1.6.3 8.1.6.4
Simulating devices.....................................................................................................................258 Simulation of devices.................................................................................................................258 Starting the simulation...............................................................................................................259 Configuring devices and networks.............................................................................................261 Hardware and network editor....................................................................................................261 Overview of hardware and network editor.................................................................................261 Network view.............................................................................................................................263 Device view...............................................................................................................................265 Topology view............................................................................................................................268 Printing hardware and network configurations..........................................................................270 Activating the page break preview for printout..........................................................................271 Changing the print options.........................................................................................................272 Inspector window ......................................................................................................................272 Hardware catalog .....................................................................................................................274 Information on hardware components.......................................................................................275 Enabling product support...........................................................................................................276 Keyboard action in the hardware and network editor................................................................277 Configuring devices...................................................................................................................278 Basics........................................................................................................................................278 Configuring individual devices...................................................................................................287 Configure networks....................................................................................................................301 Networking devices...................................................................................................................301 Communication via connections................................................................................................319 Displaying and configuring topology..........................................................................................370 Creating configurations..............................................................................................................385 Configurations for automation systems.....................................................................................385 Configurations for PROFIBUS DP.............................................................................................417 Configurations for PROFINET IO..............................................................................................439 Bus coupling with PN/PN coupler..............................................................................................467 Configurations using external tools...........................................................................................468 Loading a configuration.............................................................................................................470 System diagnostics with 'Report System Errors'.......................................................................472 Introduction to system diagnostics with 'Report System Errors'................................................472 Basics of system diagnostics.....................................................................................................473 Components supported.............................................................................................................474 Diagnostics blocks for reporting system errors..........................................................................474 Properties of the blocks.............................................................................................................475 Supported error OBs.................................................................................................................475 Overview of the status DBs.......................................................................................................477 Diagnostics status DB...............................................................................................................477 PROFINET IO DB......................................................................................................................481 PROFIBUS DP DB....................................................................................................................483 Displaying settings of system diagnostics.................................................................................485 Basic settings............................................................................................................................485 Advanced settings.....................................................................................................................488 Displaying alarms......................................................................................................................491 Overview of the alarm display...................................................................................................491 Archive view..............................................................................................................................492 Layout of the alarms in the archive view...................................................................................492 Receiving alarms.......................................................................................................................492
Table of contents
8.1.6.5 8.1.6.6 8.1.6.7 8.1.6.8 8.1.6.9 8.1.6.10 8.1.6.11 8.1.6.12 8.1.7 8.1.7.1 8.1.7.2 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 9 9.1 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.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.2.11 9.1.2.12 9.1.2.13 9.1.2.14 9.1.2.15 9.1.2.16 9.1.2.17
Export archive............................................................................................................................493 Clear archive.............................................................................................................................493 "Active alarms" view..................................................................................................................493 Layout of the alarms in the "Active alarms" view.......................................................................494 Status of the alarms...................................................................................................................494 Acknowledging alarms...............................................................................................................494 Ignoring alarms..........................................................................................................................495 Keyboard commands in the alarm display.................................................................................496 Additional information on configurations....................................................................................496 Functional description of S7-1200 CPUs...................................................................................496 Distributed I/O............................................................................................................................555 Device and network diagnostics................................................................................................584 Hardware diagnostics................................................................................................................584 Overview of hardware diagnostics.............................................................................................584 Showing non-editable and current values of configurable module properties...........................592 Showing the current values of dynamic modules properties.....................................................596 Checking a module for defects..................................................................................................599 Changing the properties of a module or the programming device / PC....................................604 Diagnostics in STOP mode.......................................................................................................612 Online accesses in the Online and Diagnostics view................................................................615 Checking PROFIBUS DP subnets for faults..............................................................................618 Connection diagnostics.............................................................................................................621 Overview of connection diagnostics..........................................................................................621 Displaying the connection status using icons............................................................................622 Detailed connection diagnostics................................................................................................623 Creating screens.......................................................................................................................627 Basics........................................................................................................................................627 Screen basics ...........................................................................................................................627 Availability of screens for specific HMI devices.........................................................................628 Basics........................................................................................................................................630 Working with screens................................................................................................................633 Working with Templates............................................................................................................636 Working with objects..................................................................................................................641 Overview of objects...................................................................................................................641 Options for Editing Objects........................................................................................................644 Inserting an object.....................................................................................................................645 Deleting an Object ....................................................................................................................647 Positioning an object.................................................................................................................648 Resizing an object.....................................................................................................................649 Selecting multiple objects..........................................................................................................650 Aligning objects.........................................................................................................................652 Moving an object forward or backward......................................................................................654 Show objects outside the screen area.......................................................................................655 Rotating objects.........................................................................................................................656 Flipping objects..........................................................................................................................657 Designing an object...................................................................................................................658 Inserting multiple objects of the same type (stamping tool).......................................................658 Repositioning and resizing multiple objects...............................................................................660 External graphics.......................................................................................................................660 Managing external graphics......................................................................................................661
Table of contents
9.1.2.18 9.1.2.19 9.1.2.20 9.1.2.21 9.1.3 9.1.3.1 9.1.3.2 9.1.4 9.1.4.1 9.1.4.2 9.1.4.3 9.1.4.4 9.1.5 9.1.5.1 9.1.5.2 9.1.5.3 9.1.5.4 9.1.5.5 9.1.5.6 9.1.5.7 9.1.6 9.1.6.1 9.1.6.2 9.1.6.3 9.1.6.4 9.1.6.5 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 9.1.7.8 9.1.7.9 9.1.7.10 9.1.8 9.1.8.1 9.1.8.2 9.1.9 9.1.9.1 9.1.9.2 9.1.9.3 9.2 9.2.1 9.2.1.1 9.2.1.2 9.2.1.3 9.2.1.4 9.2.1.5 9.2.2
Storing an external image in the graphics library......................................................................663 Working with object groups.......................................................................................................665 Configuring the keyboard access..............................................................................................671 Examples...................................................................................................................................674 Working with text lists and graphics lists...................................................................................677 Working with text lists................................................................................................................677 Working with graphics lists........................................................................................................684 Dynamizing screens..................................................................................................................692 Basics on dynamization.............................................................................................................692 Dynamization in the inspector window......................................................................................692 Dynamization with animations...................................................................................................694 Dynamize with system functions...............................................................................................703 Working with function keys........................................................................................................705 Working with function keys .......................................................................................................705 Assigning function keys globally................................................................................................707 Local assignment of function keys.............................................................................................709 Assigning a function key to a function.......................................................................................710 Assigning operator authorization for a function key...................................................................711 Assigning a function key to a graphic........................................................................................713 Example: Using function keys for screen navigation.................................................................715 Working with layers...................................................................................................................717 Basics on working with layers....................................................................................................717 Moving objects between layers.................................................................................................718 Setting the active layer..............................................................................................................718 Show and hide layers................................................................................................................719 Renaming layers........................................................................................................................721 Working with libraries................................................................................................................722 Basics on libraries.....................................................................................................................722 Copy templates and types.........................................................................................................723 Libraries in WinCC.....................................................................................................................724 Displaying library objects...........................................................................................................726 Managing library objects............................................................................................................729 Storing an object in a library......................................................................................................730 Inserting a library object............................................................................................................731 Creating a global library.............................................................................................................731 Saving a global library...............................................................................................................732 Opening a global library.............................................................................................................733 Display and operating objects...................................................................................................734 Device-Specific Nature of the Objects.......................................................................................734 Objects......................................................................................................................................735 Configuring screen navigation...................................................................................................762 Basics for screen navigation......................................................................................................762 Assign button with screen change.............................................................................................763 Assign screen change to function key.......................................................................................764 Working with Tags.....................................................................................................................765 Basics........................................................................................................................................765 Basics of tags............................................................................................................................765 Overview of HMI tag tables.......................................................................................................766 External tags..............................................................................................................................767 Addressing external tags...........................................................................................................768 Internal tags...............................................................................................................................770 Working with tags......................................................................................................................771
10
Table of contents
9.2.2.1 9.2.2.2 9.2.2.3 9.2.3 9.2.3.1 9.2.3.2 9.2.3.3 9.2.4 9.2.4.1 9.2.5 9.2.5.1 9.2.5.2 9.3 9.3.1 9.3.1.1 9.3.1.2 9.3.1.3 9.3.1.4 9.3.1.5 9.3.1.6 9.3.1.7 9.3.2 9.3.2.1 9.3.2.2 9.3.2.3 9.3.2.4 9.3.3 9.3.3.1 9.3.3.2 9.3.3.3 9.3.3.4 9.3.4 9.3.4.1 9.3.4.2 9.4 9.4.1 9.4.1.1 9.4.1.2 9.4.1.3 9.4.1.4 9.4.1.5 9.4.1.6 9.4.2 9.4.2.1 9.4.3 9.4.3.1 9.4.3.2 9.4.4 9.4.4.1 9.4.4.2 9.4.4.3
Creating tags.............................................................................................................................771 Editing tags................................................................................................................................776 Configuring tags........................................................................................................................781 Working with arrays...................................................................................................................798 Basics on arrays........................................................................................................................798 Creating array tags....................................................................................................................800 Examples of arrays....................................................................................................................801 Working with cycles...................................................................................................................801 Cycle basics..............................................................................................................................801 Displaying tags..........................................................................................................................802 Outputting tag values in screens...............................................................................................802 Configuring trend displays for values from the PLC..................................................................803 Working with alarms..................................................................................................................804 Basics........................................................................................................................................804 Alarm system in WinCC.............................................................................................................804 Alarm types................................................................................................................................805 Alarm states ..............................................................................................................................807 Alarm classes............................................................................................................................809 Acknowledgment.......................................................................................................................810 Alarm groups.............................................................................................................................812 Alarm number............................................................................................................................813 Working with alarms..................................................................................................................813 Alarm components and properties.............................................................................................813 Configuring alarms....................................................................................................................815 Configuring alarm output...........................................................................................................827 Acknowledging alarms...............................................................................................................834 Operating alarms in Runtime.....................................................................................................837 Alarms in Runtime.....................................................................................................................837 Simple alarm view, simple alarm window in runtime ................................................................839 Alarm indicator in Runtime........................................................................................................840 Acknowledging alarms...............................................................................................................841 Reference..................................................................................................................................842 System functions for alarms......................................................................................................842 System events...........................................................................................................................842 Working with recipes.................................................................................................................864 Basics........................................................................................................................................864 Definition and applications.........................................................................................................864 Examples for using recipes.......................................................................................................866 Structure of recipes...................................................................................................................866 Displaying recipes.....................................................................................................................867 Flow of data for recipes.............................................................................................................868 Synchronization of recipe data records with the PLC................................................................869 Elements and basic settings......................................................................................................870 "Recipes" editor.........................................................................................................................870 Displaying and editing recipes in Runtime.................................................................................873 Simple recipe view.....................................................................................................................873 Behavior of the recipe view in Runtime.....................................................................................874 Configuring recipes....................................................................................................................875 General configuration procedure ..............................................................................................875 Creating and Editing Recipes....................................................................................................876 Configuring the display of recipes.............................................................................................884
11
Table of contents
9.4.5 9.4.5.1 9.4.6 9.4.6.1 9.5 9.5.1 9.5.2 9.5.3 9.5.3.1 9.5.3.2 9.5.3.3 9.5.3.4 9.5.3.5 9.5.4 9.5.4.1 9.5.4.2 9.5.4.3 9.5.4.4 9.5.5 9.5.5.1 9.5.5.2 9.5.6 9.5.6.1 9.5.6.2 9.5.6.3 9.6 9.6.1 9.6.1.1 9.6.1.2 9.6.2 9.6.2.1 9.6.2.2 9.6.2.3 9.6.2.4 9.6.2.5 9.6.3 9.6.3.1 9.6.4 9.6.4.1 9.6.4.2 9.7 9.7.1 9.7.2 9.7.3 9.7.3.1 9.7.3.2 9.7.3.3 9.7.3.4 9.7.4 9.7.4.1
Using recipes in Runtime...........................................................................................................887 Using the simple recipe view.....................................................................................................887 Example.....................................................................................................................................893 Example of creating a recipe.....................................................................................................893 Configuring user administration.................................................................................................895 Field of application of the user administration...........................................................................895 Form of the user administration.................................................................................................895 Basics........................................................................................................................................896 Users.........................................................................................................................................896 Users work area........................................................................................................................897 User groups...............................................................................................................................898 User groups work area..............................................................................................................898 Settings for the user administration...........................................................................................899 Setting up the user administration.............................................................................................901 Basics on user administration....................................................................................................901 Administering users for Runtime...............................................................................................902 Managing users in Runtime.......................................................................................................909 Configuring access protection...................................................................................................916 Reference..................................................................................................................................917 Objects with access protection..................................................................................................917 Default user groups and authorizations.....................................................................................917 Examples...................................................................................................................................918 Example: Configuring a button with logon dialog box...............................................................918 Example: Logging the logon and logoff events.........................................................................919 Example of user management...................................................................................................920 Working with system functions..................................................................................................927 Basics........................................................................................................................................927 System functions.......................................................................................................................927 Use of system functions ...........................................................................................................929 Working with function lists.........................................................................................................929 Basic of the functions list...........................................................................................................929 Properties of a function list........................................................................................................930 Configuring a function list..........................................................................................................931 Editing a function list..................................................................................................................933 Executing a function list in Runtime ..........................................................................................934 Example.....................................................................................................................................934 Changing the operating mode on the HMI device with the current display...............................934 Reference..................................................................................................................................937 Function list...............................................................................................................................937 Events........................................................................................................................................995 Planning tasks.........................................................................................................................1010 Field of application of the Scheduler.......................................................................................1010 Working with tasks and triggers...............................................................................................1012 Basics......................................................................................................................................1013 Work area of the "Scheduler" editor........................................................................................1013 Function list.............................................................................................................................1014 Triggers...................................................................................................................................1014 Planning tasks with event triggers...........................................................................................1015 Examples.................................................................................................................................1017 Example: Update user following change of user.....................................................................1017
12
Table of contents
9.8 9.8.1 9.8.1.1 9.8.1.2 9.8.1.3 9.8.1.4 9.8.1.5 9.8.2 9.8.2.1 9.8.2.2 9.8.3 9.8.3.1 9.8.3.2 9.8.4 9.8.4.1 9.8.5 9.8.5.1 9.8.5.2 9.8.5.3 9.8.5.4 9.8.5.5 9.8.5.6 9.8.6 9.8.6.1 9.8.6.2 9.8.6.3 9.8.6.4 9.8.6.5 9.8.6.6 9.8.6.7 9.8.7 9.8.7.1 9.8.7.2 9.8.7.3 9.8.7.4 9.8.7.5 9.8.8 9.8.8.1 9.8.8.2 9.8.8.3 9.8.8.4 9.9 9.9.1 9.9.2 9.9.2.1 9.9.2.2 9.9.2.3 9.9.2.4 9.9.2.5 9.9.2.6 9.9.3
Communicating with PLCs......................................................................................................1019 Basics of communication.........................................................................................................1019 Communication between devices............................................................................................1019 Devices and networks in the automation system....................................................................1020 Data exchange using tags.......................................................................................................1025 Data exchange using area pointers.........................................................................................1026 Communication drivers............................................................................................................1026 Networks and connections......................................................................................................1027 SIMATIC communication networks.........................................................................................1027 Configuring networks and connections....................................................................................1031 Data exchange........................................................................................................................1039 Data exchange using tags.......................................................................................................1039 Data exchange using area pointers.........................................................................................1045 Device dependency.................................................................................................................1051 Basic Panel..............................................................................................................................1051 Communicating with SIMATIC S7 1200..................................................................................1055 Communication with SIMATIC S7 1200..................................................................................1055 Communication via PROFINET...............................................................................................1056 Communication via PROFIBUS...............................................................................................1068 Data exchange .......................................................................................................................1076 Performance features of communication.................................................................................1094 Creating connections in the "Connections" editor...................................................................1096 Communicating with SIMATIC S7 300/400.............................................................................1104 Communication with SIMATIC S7 300/400.............................................................................1104 Communication via PROFINET...............................................................................................1105 Communication via PROFIBUS...............................................................................................1118 Communication via MPI...........................................................................................................1126 Data exchange........................................................................................................................1133 Performance features of communication.................................................................................1150 Creating connections in the "Connections" editor...................................................................1151 Communicating with SIMATIC S7 200....................................................................................1163 Communication with SIMATIC S7 200....................................................................................1163 Creating a connection to SIMATIC S7 200..............................................................................1163 Parameters for the connection................................................................................................1165 Data exchange .......................................................................................................................1172 Performance features of communication.................................................................................1189 Communication with other PLCs.............................................................................................1190 Communication with other PLCs.............................................................................................1190 Distinctive features when configuring......................................................................................1191 Communication drivers............................................................................................................1191 Data exchange using area pointers.........................................................................................1297 Using global functions.............................................................................................................1311 HMI device wizard basics........................................................................................................1311 Importing and exporting project data.......................................................................................1312 Importing and exporting project data.......................................................................................1312 Importing and exporting recipes..............................................................................................1314 Importing and exporting alarms...............................................................................................1317 Importing and exporting tags...................................................................................................1325 Importing and exporting text lists.............................................................................................1330 Importing and exporting project texts......................................................................................1335 Using cross-references............................................................................................................1338
13
Table of contents
9.9.3.1 9.9.3.2 9.9.3.3 9.9.3.4 9.9.4 9.9.4.1 9.9.4.2 9.9.4.3 9.9.4.4 9.9.4.5 9.9.4.6 9.9.4.7 9.9.4.8 9.9.5 9.9.5.1 9.9.5.2 9.9.5.3 9.9.6 9.9.6.1 9.9.6.2 9.10 9.10.1 9.10.1.1 9.10.1.2 9.10.1.3 9.10.1.4 9.10.2 9.10.2.1 9.10.2.2 9.10.2.3 9.10.3 9.10.3.1 9.10.3.2 9.10.3.3 9.10.3.4 9.10.3.5 9.10.4 9.10.4.1 9.10.4.2 9.10.4.3 9.11 9.11.1 9.11.1.1 9.11.1.2 9.11.1.3 9.11.2 9.11.2.1 9.11.2.2 9.11.2.3 9.11.2.4 9.11.2.5
General information about cross references...........................................................................1338 Displaying the cross-reference list...........................................................................................1338 Structure of the cross-reference list.........................................................................................1339 Displaying cross-references in the Inspector window..............................................................1340 Managing languages...............................................................................................................1342 Languages in WinCC...............................................................................................................1342 Language settings in the operating system.............................................................................1343 Operating system settings for Asian languages......................................................................1344 Setting project languages........................................................................................................1345 Creating one project in multiple languages.............................................................................1348 Using language-specific graphics............................................................................................1356 Languages in runtime..............................................................................................................1360 Example of multilingual configuration......................................................................................1367 Replacing devices...................................................................................................................1370 Basics......................................................................................................................................1370 Device-specific functions.........................................................................................................1371 Adjusting screens to the new device.......................................................................................1374 Copying between devices and editors.....................................................................................1378 Basics......................................................................................................................................1378 Copying and pasting................................................................................................................1380 Compiling and loading.............................................................................................................1384 Compiling and loading projects...............................................................................................1384 Overview of compiling and loading projects............................................................................1384 Compiling a project..................................................................................................................1385 Loading projects......................................................................................................................1386 Runtime start...........................................................................................................................1389 Simulating projects..................................................................................................................1390 Simulation basics.....................................................................................................................1390 Simulating a project.................................................................................................................1392 Working with the tag simulator................................................................................................1394 Servicing the HMI device.........................................................................................................1396 ProSave...................................................................................................................................1396 Backup of HMI data.................................................................................................................1396 Backing up and restoring data of the HMI device....................................................................1397 Updating the operating system................................................................................................1398 Updating the HMI device operating system.............................................................................1399 Reference................................................................................................................................1401 Error messages during loading of projects..............................................................................1401 Adapting the project for another HMI device...........................................................................1402 Establishing a connection to the HMI device...........................................................................1404 Operating in Runtime...............................................................................................................1405 Basics......................................................................................................................................1405 Overview..................................................................................................................................1405 Tags in Runtime......................................................................................................................1406 System functions in Runtime...................................................................................................1406 Commissioning projects..........................................................................................................1407 Settings in the Runtime software ............................................................................................1407 Loading projects......................................................................................................................1408 Starting Runtime on the Engineering Station..........................................................................1409 Starting Runtime on the HMI device........................................................................................1410 Testing a project......................................................................................................................1410
14
Table of contents
9.11.2.6 9.11.2.7 9.11.3 9.11.3.1 9.11.3.2 9.11.3.3 9.11.3.4 9.11.3.5 9.11.4 9.11.4.1 9.11.4.2 9.11.4.3 9.11.4.4 9.11.4.5 9.12 9.12.1 9.12.2 9.12.3 9.12.3.1 9.12.3.2 9.13 9.13.1 9.13.2 9.13.3 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.10.1 10.10.2 10.10.3 10.10.4 10.10.5 10.10.6 10.10.7
Closing a project......................................................................................................................1411 Backing up and restoring data of the HMI device....................................................................1412 Languages in runtime..............................................................................................................1413 Languages in runtime..............................................................................................................1413 Setting a runtime language......................................................................................................1413 Setting the font for a runtime language...................................................................................1414 Configuring language switching...............................................................................................1415 Specific features of Asian and Eastern languages in runtime.................................................1416 Operating projects...................................................................................................................1417 Basics......................................................................................................................................1417 Operating objects....................................................................................................................1424 Project security........................................................................................................................1437 Operating alarms.....................................................................................................................1444 Operating recipes....................................................................................................................1451 Performance features..............................................................................................................1461 Engineering system.................................................................................................................1461 Basic Panel..............................................................................................................................1463 General technical data.............................................................................................................1467 Recommended printers...........................................................................................................1467 Memory requirements of recipes for Basic Panels..................................................................1467 Migration to WinCC V11..........................................................................................................1468 Overview of migration to WinCC V11......................................................................................1468 Libraries...................................................................................................................................1469 Screens and templates............................................................................................................1471 General information about online mode..................................................................................1473 View in online mode................................................................................................................1475 Online access..........................................................................................................................1476 Displaying accessible devices.................................................................................................1478 Opening the properties of an interface....................................................................................1480 Establishing and canceling an online connection....................................................................1480 Connecting online with several devices...................................................................................1482 Basics of assigning parameters for the PG/PC interface........................................................1483 Adding interfaces.....................................................................................................................1483 Setting parameters for the Ethernet interface..........................................................................1484 Setting parameters for the Industrial Ethernet interface..........................................................1484 Displaying operating system parameters................................................................................1485 Connecting the PG/PC interface to a subnet...........................................................................1486 Setting parameters for the Ethernet interface..........................................................................1486 Assigning a temporary IP address...........................................................................................1487 Managing temporary IP addresses..........................................................................................1487 Resetting the TCP/IP configuration.........................................................................................1488
10.11 Setting parameters for the MPI and PROFIBUS interfaces.....................................................1489 10.11.1 Setting parameters for the MPI and PROFIBUS interfaces.....................................................1489 10.11.2 Setting MPI or PROFIBUS interface parameters automatically..............................................1490
15
Table of contents
Setting parameters for the MPI interface.................................................................................1490 Setting parameters for the PROFIBUS interface.....................................................................1492 Overview of the bus parameters for PROFIBUS.....................................................................1495 Resetting the MPI or PROFIBUS configuration.......................................................................1496
10.12 Establishing a remote connection with TeleService................................................................1497 10.12.1 Basics of working with TeleService.........................................................................................1497 10.12.1.1 Introduction to TeleService.................................................................................................1497 10.12.1.2 TeleService functionality....................................................................................................1498 10.12.1.3 Telephone book at TeleService..........................................................................................1498 10.12.2 Telephone networks and modems..........................................................................................1499 10.12.2.1 Supported telephone networks and modems.....................................................................1499 10.12.2.2 Installing the local modem..................................................................................................1500 10.12.2.3 Connecting and configuring the remote modem................................................................1501 10.12.2.4 Initialization string requirements.........................................................................................1502 10.12.3 Using a TS adapter to establish a remote connection.............................................................1502 10.12.3.1 Basics of using a TS adapter.............................................................................................1502 10.12.3.2 Installing TS adapter software............................................................................................1504 10.12.3.3 TS adapter MPI..................................................................................................................1504 10.12.3.4 TS adapter IE.....................................................................................................................1511 10.12.4 Access protection for TeleService and the TS Adapter...........................................................1516 10.12.4.1 Access protection information............................................................................................1516 10.12.4.2 TeleService callback options..............................................................................................1517 10.12.4.3 Levels of protection............................................................................................................1517 10.12.4.4 Setting up access protection and callback number for the TS adapter..............................1518 10.12.4.5 Complete a callback in TeleService...................................................................................1519 10.12.5 Establishing a remote connection to a remote plant................................................................1521 10.12.5.1 Establishing a remote connection......................................................................................1521 10.12.5.2 Terminating a remote connection.......................................................................................1522 10.12.5.3 Checklist for troubleshooting the modem...........................................................................1522 10.12.6 Working with the phone book..................................................................................................1523 10.12.6.1 Basics on working with the phone book.............................................................................1523 10.12.6.2 Structure of the phone book...............................................................................................1524 10.12.6.3 Symbols in the phone book................................................................................................1525 10.12.6.4 Manage phone book...........................................................................................................1525 10.12.7 CPU controlled TeleService remote connections ...................................................................1527 10.12.7.1 Overview of CPU controlled remote connections...............................................................1527 10.12.7.2 Establishing a connection from and to remote systens (PG-AS-remote coupling).............1528 10.12.7.3 Data exchange between remote systems (AS-AS-remote coupling).................................1530 10.12.7.4 Send SMS from a system...................................................................................................1532 10.12.7.5 Send an email from a system.............................................................................................1533 10.12.8 Troubleshooting.......................................................................................................................1535 10.12.8.1 General information on troubleshooting.............................................................................1535 10.12.8.2 Recording a log file for the modem....................................................................................1535 10.12.8.3 Remote connection to the TS adapter is not established...................................................1536 10.12.8.4 Remote connection from the TS adapter is not established...............................................1537 10.12.8.5 Modem connection is interrupted.......................................................................................1538 10.12.8.6 Modem alarms....................................................................................................................1539 Index.......................................................................................................................................................1541
16
STEP 7
STEP 7 (TIA Portal) is the engineering software for configuring the SIMATIC S7-1200, S7-300/400, and WinAC controller families. STEP 7 (TIA Portal) is available in 2 editions, depending on the configurable controller families: STEP 7 Basic for configuring the S7-1200 STEP 7 Professional for configuring S7-1200, S7-300/400, and WinAC
17
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 4 editions, depending on the configurable operator control systems: WinCC Basic for configuring Basic Panels WinCC Basic is included with every STEP 7 Basic and STEP 7 Professional product. WinCC Comfort for configuring all panels (including Comfort Panels, Mobile Panels) WinCC Advanced for configuring all panels and PCs with the WinCC Runtime Advanced visualization software WinCC Runtime Advanced is a visualization software for PC-based single-station systems. WinCC Runtime Advanced can be purchased with licenses for 128, 512, 2k, 4k as well as 8k PowerTags (tags with a process interface). WinCC Professional for configuring panels and PCs with WinCC Runtime Advanced or SCADA System WinCC Runtime Professional WinCC Runtime Professional is a SCADA system for structuring a configuration ranging from single-station systems to multi-station systems including standard clients or web clients. WinCC Runtime Professional can be purchased with licenses for 128, 512, 2k, 4k, 8k, 64k, 102400, 153600 as well as 262144 PowerTags (tags with a process interface). With WinCC (TIA Portal), it is also possible to configure a SINUMERIK PC with WinCC Runtime Advanced or WinCC Runtime Professional and HMI devices with SINUMERIK HMI Pro sl RT or SINUMERIK Operate WinCC RT Basic.
1.2
1.3
18
System overview of STEP 7 and WinCC 1.3 Options for WinCC Engineering and Runtime systems
19
Readme
2.1
2.1.1
2
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.
General notes
General notes
Contents
The readme contains the following information: Information that could not be included in the online help. The following additional information for V11 SP2 Second Edition: Installation problems with virtual drives have been resolved. The current Automation License Manager V5.1 SP1 Update 3 is integrated.
Security settings
In order to operate the software packages in the TIA Portal, port 4410 for TCP must be entered as an exception in the Windows firewall during installation.
Notes on handling
If a project in the list of projects last used is located on a network drive that is not connected, you may experience delays when opening the "Project" menu. When you insert a CPU, you may need to wait for some time if the project editor is open at the same time. This generally takes longer when you insert the first CPU in a newly created project. To be able to continue working more quickly, you should close the project editor before inserting a CPU. The message "Application is not responding" may appear in Windows 7 with functions that take a long time to run (loading the CPU for example). If this occurs, wait until the function has correctly finished.
WinCC Basic V11.0 SP2 System Manual, 04/2012,
21
22
Note on SD cards
The SD cards have been formatted and initialized by Siemens for use with S7-1200 modules. This format must not be overwritten otherwise the card will no longer be accepted by the S7-1200 modules. Formatting with Windows tools is therefore not permitted.
23
Screen display
After long periods of work, it can happen in the case of certain computer configurations with Windows XP that parts of the TIA Portal interface are no longer updated. Reducing the graphic hardware acceleration can correct this problem. You can find the setting for this by clicking on the desktop and selecting "Properties > Settings > Advanced > Troubleshoot > Slider Hardware acceleration" by means of the right mouse button. In this dialog, move the slider "Hardware acceleration" gradually to the left and apply this setting until the contents of the screen are displayed correctly again.
Tablet PCs
For the TIA Portal V11, tablet PCs are only released with the operating system Windows 7, not with Windows XP.
SQL Server
During the installation of the SQL Server 2005 or the SQL Server 2005 Express, an error can occur if the product SQL Server 2008 is already installed on your system. In order to be able to use both varieties of the SQL Server in parallel, the SQL Server 2005 must be installed before the SQL Server 2008. To do this, follow these steps: 1. Remove the SQL Server 2008 version, without deleting the databases. 2. Install WinCC. The SQL Server 2005 is hereby installed and set up on your system. 3. Install the SQL Server 2008 again. Now you can continue to use the databases already created in the SQL Server 2008.
24
See also
Notes on the installation (Page 25)
2.1.2
Contents
Installation of STEP 7 Basic V11 and STEP 7 Professional V11 under Windows XP with Turkish Regional and Language Options
Installation of STEP 7 Basic V11 and STEP 7 Professional V11 under Windows XP may be cancelled, if the regional and language options are set to Turkish. In this case change the regional and language options from Turkish to English or German. 1. Open the Control Panel under Windows with one of the following commands: "Start > Control Panel" (Start menu under Windows XP) "Start > Settings > Control Panel" (classic start menu) 2. Open the "Regional and Language Options". 3. Select the "Regional Options" tab. 4. Under "Standards and formats" select "German" or "English" in the drop-down list. 5. Click "Apply" and confirm with OK.
25
Removing
In rare cases removal of the program can cause the computer to freeze, even when a full version of SQL Server 2005 is installed. In this occurs, disconnect the computer from the network to continue the removal process.
Installation of the SIMATIC USB driver under Windows server 2003 R2 StdE SP2
An operating system message relating to the SIMATIC USB driver is issued on the operating system Windows Server 2003 R2 StdE SP2. This message must be acknowledged with "Yes" as soon as possible after the message has been issued. The message may be in the background and therefore may not be immediately visible. After a certain period of time, the setup continues with the next component. The SIMATIC USB drivers are then not installed and cannot be used.
2.1.3
Contents
26
See also
Service & Support (http://support.automation.siemens.com/WW/view/en/12660737)
2.2
2.2.1
STEP 7 Basic
Security information
Siemens offers IT security mechanisms for its automation and drive product portfolio in order to support the safe operation of the plant/machine. Our products are also continuously developed further with regard to IT security. We therefore recommend that you keep yourself informed about updates and upgrades for our products and always use the latest version of each product. You can find information on this at: http://support.automation.siemens.com (http://support.automation.siemens.com). You can register for a product-specific newsletter here. For the safe operation of a plant/machine, however, it is also necessary to integrate the automation components into an overall IT security concept for the entire plant/machine, which corresponds to the state-of-the-art IT technology. You can find information on this at:
27
2.2.2
Contents
Notes on use
The readme contains the following information: Information that could not be included in the online help. The following additional information for STEP 7 Basic V11 SP2 Second Edition: Use of constants as array index (Page 33) S7-1200 web server (Page 29)
Online operation
The simultaneous online operation of STEP 7 V5.5 or earlier and STEP 7 Basic V11 has not been approved.
28
2.2.3
2.2.3.1 Contents
2.2.3.2 Contents
29
Diagnostics repeater 6ES7 972-0AB01-0XA0 1 Count 24 V 1 Count 5 V 1 Step 5 V 2 pulses 1 SI 1 SI Modbus 1 SSI 1 Pos Universal SIWAREX
ET 200M
SIWAREX
2.2.3.3 Contents
30
2.2.3.4 Contents
2.2.3.5 Contents
2.2.3.6 Contents
31
Assigning an IP address
If an IP address is assigned directly to a PLC via the diagnostics and online function with "Functions > Assigning an IP address", this IP address will be set permanently and retained even after a restart or power failure.
2.2.3.7 Contents
2.2.3.8 Contents
32
2.2.4
2.2.4.1 Contents
Programming a PLC
General notes on PLC programming
33
2.2.4.2 Contents
SCL
MUX: Multiplexing
As of V11 SP2 parameter numbering of the MUX instruction no longer begins with IN0 but with IN1. If you want to import the MUX instruction from a source of a previous version of the TIA portal, please correct the calls by increasing the parameter numbers of each call by 1.
2.2.4.3 Contents
Instructions
MODBUS library
The instruction "MB_SLAVE" was updated in STEP 7 V10.5 SP2. If you have already used "MB_SLAVE" V1.0 in a project that was created with STEP 7 V10.5 SP1, you must manually replace this version with the new version MB_SLAVE" V1.1 after the installation of STEP 7 V11. To do this, follow these steps: 1. Delete "MB_SLAVE" V1.0 from all blocks in the project. 2. Delete "MB_SLAVE" V1.0 from the project library. 3. Insert "MB_SLAVE" V1.1 in all required locations of use. 4. Compile the project.
34
Using instructions with parameters of type VARIANT in logic blocks with different access types (S7-1200)
Logic blocks (FBs/FCs) and data blocks (DBs) can be created with different access types ("standard" and "optimized"). In logic 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 logic blocks of different access types are called reciprocally. This could cause the following to occur: A structure from a standard data block is directly or indirectly passed to an optimized logic block, which forwards this structure directly or indirectly to one of the blocks mentioned above. The reverse scenario, whereby a structure from an optimized logic 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.4.4
35
2.2.5
2.2.5.1
Technological functions
Notes on technological functions
PID_Compact V1.0
PID_Compact V1.0 is out of date. A CPU with firmware V2.0 is required as of PID_Compact V1.1. Update the CPU firmware and select a newer version from the Task Card "Instructions".
2.3
2.3.1
WinCC Readme
Security note
Security information
Siemens offers IT security mechanisms for its portfolio of automation and drive products in order to support secure operation of the plant/machine. Our products are also continuously developed further with regard to IT security. We therefore recommend that you keep yourself
36
2.3.2
Contents
Notes on use
37
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.
38
39
2.3.3
Contents
Migration
Information that could not be included in the online help. Note The most efficient way to locate scripting errors in the course of the initial test run after migration is to use an installed Script Debugger and the diagnostics controls.
The display names of the alarm classes can be changed as necessary after migration.
40
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.
2.3.4
2.3.4.1 Contents
Engineering System
Screens and Screen Objects
41
Event names in case of alarms in the "Info" tab of the Inspector window
In some alarms of the Inspector window the event names in the "Info" tab will deviate from the names in the "Properties" tab.
Name in the "Properties" tab of the Inspector window Cleared Loaded Enable Change When a dialog is opened When a dialog is closed User change Screen change Disable Press Outgoing Incoming Name in the "Info" tab of the Inspector window ClearScreen GenerateScreen Activate Change ONMODALBEGIN ONMODALEND PASSWORD SCREEN Deactivate Press Going Coming
42
Faceplates
Faceplates cannot be rotated or mirrored.
43
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 "Display format" 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.
44
2.3.4.2 Contents
Tag names
HMI tag names may not start with the character @.
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.
45
2.3.4.3 Contents
46
2.3.4.4 Contents
System functions
2.3.4.5 Contents
Recipes
2.3.4.6 Contents
User administration
2.3.4.7 Content
Communication
Opening projects in WinCC V11 (no service pack) with communication via Modicon Modbus RTU, Modicon TCPIP, Allen Bradley DF1
The following HMI devices are affected: OP 77A TP177 A Basic Panel
47
48
49
2.3.5
Contents
50
51
52
2.3.6
2.3.6.1 Contents
Runtime
Notes on operation in Runtime
Information that could not be included in the online help. CAUTION Ethernet communication 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.
53
2.3.6.2 Contents
2.3.7
2.3.7.1 Contents
HMI devices
Notes on HMI devices
Information that could not be included in the online help. If the PC goes into standby or hibernate mode while the transfer is in progress, the panel status after interruption of the transfer is not defined.
54
KP400 Basic, TP1500 Comfort, KP1500 Comfort, TP1900 Comfort, TP2200 Comfort
The devices are already described in the online help, but cannot yet be configured in WinCC. To be able to configure these devices, you have to install the HSP that will be released soon.
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
55
56
Installation
3.1
3.1.1
See also
Licenses (Page 67) Starting installation (Page 69) Displaying the installed software (Page 72) Modifying or updating installed products (Page 73) Repairing installed products (Page 75) Starting to uninstall (Page 76)
57
3.1.2
3.1.2.1
* For more detailed information on operating systems, refer to the help on Microsoft Windows or the Microsoft homepage.
Recommended hardware
The following table shows the recommended hardware for the operation of STEP 7.
Hardware Computer Processor RAM Hard disk Monitor Optical drive Requirement SIMATIC FIELD PG M2 PREMIUM (or similar PC) 2.2 GHZ CORE 2 DUO (T7500) 1X2GB DDR2 RAM 250GB S-ATA HDD 15" SXGA+ DISPLAY (1400 X 1050) DL MULTISTANDARD DVD RW
58
3.1.3
3.1.3.1
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 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 installation of the "SIMATIC WinCC Professional" software package:
Hardware/software Processor type RAM Free hard disk space Requirement Pentium M, 1.6 GHz or similar 2 GB 2 GB on system drive "C:"
59
* For more detailed information on operating systems, refer to the help on Microsoft Windows or the Microsoft homepage.
60
Recommended hardware
The following table shows the recommended hardware for the operation of SIMATIC WinCC.
Hardware Computer Processor RAM Hard disk Monitor Optical drive Requirement SIMATIC FIELD PG M2 PREMIUM 2.2 GHZ CORE 2 DUO (T7500) 1X2GB DDR2 RAM 250GB S-ATA HDD 15" SXGA+ DISPLAY (1400 X 1050) DL MULTISTANDARD DVD RW
61
See also
Licensing of WinCC Engineering System (Page 62)
3.1.3.2
62
See also
Software and hardware requirements (Page 59) Licensing of HMI devices (Page 63) Working with license keys (Page 65)
License key
To be able to license non-PC-based HMI devices with license keys, you require the "SIMATIC HMI License Manager Panel Plug-in" add-on.
63
Data backup
CAUTION Destruction of license keys on non-PC-based HMI devices Installed license keys and authorizations are destroyed by the backup/restore processes on the HMI devices listed below. 270 series 370 series Carry out the following before beginning restoring: Use the Automation License Manager and ProSave to check whether license keys are installed on the HMI device. Remove any license keys present on the HMI device. After restoring has been carried out, re-install the license keys on the HMI device.
Non-licensed mode
Runtime add-ons can also be used without a license without restriction. An alert for nonlicensed mode is presented every 10 minutes by a window requiring acknowledgment.
See also
Licensing of WinCC Engineering System (Page 62)
64
Data backup
Remove the license keys on the HMI device when backing up data on the HMI device and when creating a backup during device replacement. You use the Automation License Manager to back up license keys of a HMI device to the storage area of the license key. CAUTION Destruction of license keys on non-PC-based HMI devices Installed license keys are destroyed by backup/restore processes on the HMI devices listed below. 270 series 370 series Carry out the following before beginning restoring: Use the Automation License Manager and ProSave to check whether license keys are on the HMI device. Remove any license keys present on the HMI device. After restoring has been carried out, re-install the license keys on the HMI device.
65
Read the description of Automation License Manager ("Start > Simatic Automation > Documentation"). Observe all warnings and notices. The license key storage location on PC-based HMI devices and on non-PC-based HMI devices where Automation License Manager is used may contain multiple license keys. This capability means you can store multiple licenses of the same type at one location. Save all license keys of the HMI device to the same storage location. CAUTION Always keep the original storage location of the license keys.
Defective license
A license is defective in the following cases: If the license key is no longer accessible at the storage area. If the license key disappears during its transfer to the destination drive. You can use the Automation License Manager to repair the defective license. Use the "Restore" function or the "Restore Wizard" of the Automation License Manager for this purpose. Contact
66
See also
Licensing of WinCC Engineering System (Page 62)
3.2
Licenses
Availability of licenses
The licenses for the products of the TIA Portal are usually supplied on the installation data medium and installed automatically by the Automation Licence Manager during the installation process of the TIA Portal. If you remove the TIA Portal, the corresponding licenses are also removed automatically. Licenses still required should be secured.
67
Note For additional information on how to manage your licenses with the Automation License Manager , refer to the documentation supplied with the Automation License Manager .
See also
Notes on the system requirements (Page 57) Starting installation (Page 69) Displaying the installed software (Page 72) Modifying or updating installed products (Page 73) Repairing installed products (Page 75) Starting to uninstall (Page 76) Installation log (Page 68)
3.3
Installation log
68
See also
Licenses (Page 67) Starting installation (Page 69) Installing Support Packages (Page 71) Displaying the installed software (Page 72) Modifying or updating installed products (Page 73) Repairing installed products (Page 75) Starting to uninstall (Page 76)
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.
69
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".
70
Result
The TIA Portal along with the products and licenses you have ordered and the Automation License Manager have been installed on your computer.
See also
Installation log (Page 68) Notes on the system requirements (Page 57) Licenses (Page 67) Displaying the installed software (Page 72) Modifying or updating installed products (Page 73) Repairing installed products (Page 75) Starting to uninstall (Page 76)
3.5
71
Procedure
To install a Support Package, follow these steps: 1. Click "Support packages" in the "Options" menu. The "Detailed information" dialog opens. A table lists all support packages from the directory that you selected as the storage location for support packages in the settings. 2. If you want to install a support package that is not in the list, you have the following options: If the support package is already on your computer, you can add it to the list by selecting "Add from the file system". If you add a support package from the "Service & Support" page on the Internet, first you download it by selecting "Download from the Internet". Then you can add it from the file system. 3. Select the support package that you want to install. 4. Click "Install." 5. Close and then restart the TIA Portal.
See also
Installation log (Page 68)
3.6
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.
72
See also
Notes on the system requirements (Page 57) Licenses (Page 67) Starting installation (Page 69) Modifying or updating installed products (Page 73) Repairing installed products (Page 75) Starting to uninstall (Page 76) Installation log (Page 68)
3.7
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.
73
Result
The existing installation has been modified on your computer.
74
See also
Notes on the system requirements (Page 57) Licenses (Page 67) Starting installation (Page 69) Displaying the installed software (Page 72) Repairing installed products (Page 75) Starting to uninstall (Page 76) Installation log (Page 68)
3.8
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.
75
Result
The installed products have been reinstalled.
See also
Notes on the system requirements (Page 57) Licenses (Page 67) Starting installation (Page 69) Displaying the installed software (Page 72) Modifying or updating installed products (Page 73) Starting to uninstall (Page 76) Installation log (Page 68)
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.
76
77
See also
Installation log (Page 68) Notes on the system requirements (Page 57) Licenses (Page 67) Starting installation (Page 69) Displaying the installed software (Page 72) Modifying or updating installed products (Page 73) Repairing installed products (Page 75)
3.10
3.10.1
3.10.2
78
Procedure
To install the migration tool, proceed as follows: 1. Download the installation file from the Service & Support area on the Siemens website. 2. Run the downloaded file. The setup program for the migration tool will open. 3. First, select the language in which the setup should be displayed and click the "Next" button. The page for selecting the software language is displayed. 4. Since the migration tool is provided exclusively in English, you cannot choose any other language for the installation. Therefore, click "Next" to proceed to the next step. The page for selecting the product is displayed. 5. The migration tool consists solely of a software component. Therefore, the migration tool is already selected. To create a Desktop icon for starting the migration tool, select the check box "Create Desktop icon". Then click the "Next" button. The page for confirming the licensing terms is shown. 6. Click on an entry in the list of license terms to read the selected license term. If you agree with all license terms, select the check box "I accept the terms of the displayed license agreement". Then click the "Next" button. An overview of the installation is displayed. 7. Click the "Install" button. The installation is performed with the displayed settings.
3.10.3
Procedure
To remove the migration tool, follow these steps: 1. Open the Control Panel. 2. Double click on "Add or Remove Programs" in the Control Panel. The "Add or Remove Programs" dialog opens. 3. Select the "TIA Portal Migration Tool V11" entry in the "Add or Remove Programs" dialog, and click the "Remove" button. A confirmation prompt appears. 4. Click the "Uninstall" button to confirm this prompt. The migration tool will be removed.
79
Migrating projects
4.1 Migrating projects
81
See also
Displaying the log file of the migration (Page 86) Scaling of STEP 7 and WinCC (Page 17)
4.2
4.2.1
82
See also
Migrating projects (Page 81) Migrating projects (Page 85) Calling the migration tool (Page 84) Creating a migration file (Page 84)
83
4.2.2
See also
Creating a migration file (Page 84)
4.2.3
Requirement
The suitable, original software with a valid license is installed for all configurations used in the initial project. The initial project is not provided with access protection. The initial project must be consistent, otherwise problem-free migration cannot be assured.
Procedure
To create the migration file, follow these steps: 1. Choose the path of the source file for the migration in the "Storage Location (Path)" field. 2. Select the check box "Exclude hardware configuration" to migrate the software only. 3. Choose the path and the file name for the migration file in the "Intermediate file". 4. Click the "Migrate" button.
Result:
A migration file is created. Finally, copy this file to the target system and migrate this file in the TIA Portal.
84
See also
Migrating projects (Page 85) Calling the migration tool (Page 84) Migrating projects with the migration tool (Page 82)
4.3
Migrating projects
Requirement
There is already a converted file in the format AM11 available or the original software with a valid license is installed for all the configurations in the initial project. The initial project is not provided with access protection. The initial project must be consistent, otherwise problem-free migration cannot be assured. Read the additional information on the requirements in the help for the respective products installed. Note System hibernation during the migration While a migration is running, the system should not be changed to the standby or hibernate mode. Otherwise the migration will be aborted.
Procedure
To migrate a project, follow these steps: 1. Select the "Migrate project" command in the "Project" menu. The "Migrate project" dialog opens. 2. Specify the path and the file name for the project to be migrated in the "Source path" field. Choose either a project in the AM11 migration format or in the format of the initial project. 3. Select the check box "Exclude hardware configuration" to migrate the software only. If you have selected a migration file that was created using the migration tool, the check box is disabled. In this case, you must specify if you wish to exclude the hardware configuration of the migration before the conversion with the migration tool . 4. Choose a name for the new project in the "Project name" box. 5. Choose a path in the "Target path" box where the new project will be created. 6. Enter your name or the name of another person responsible for the project in the "Author" field. 7. Enter a comment in the "Comment" box, if you require one. 8. Click "Migrate".
85
Result
The initial project is converted. The system outputs a message when the migration is complete. From here, you can directly open a log for the migration. The newly created project then opens in the project view. The migration log is also displayed in the Inspector window.
See also
Post-editing integrated projects (Page 119) Migrating projects with the migration tool (Page 82) Creating a migration file (Page 84)
4.4
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 177)
4.5
86
Procedure
To display the log file of the migration, follow these steps: 1. Select the open project in the project tree. 2. Select "Properties" in the shortcut menu of the project. The dialog with the properties of the project opens. 3. Select the "Project history" group in the area navigation. The overview table is displayed. 4. Click on the link to the log file in the "Log file" column. The log file is displayed in the Microsoft Internet Explorer.
See also
Migrating projects (Page 81)
4.6
4.6.1
4.6.1.1
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.
87
See also
Object support during migration (WinCC flexible) (Page 94) Projects from Migrating WinCC flexible projects (WinCC flexible) (Page 90) Compiling and loading a migrated project (WinCC flexible) (Page 92) Migrating runtime data (WinCC flexible) (Page 104) Migrating integrated projects (WinCC flexible) (Page 106) Supported HMI devices (WinCC flexible) (Page 93) Migration of data types (WinCC flexible) (Page 109)
4.6.1.2
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. See Engineering system (Page 1461) for additional information.
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 Folder_1/Tag_1 Folder_1/Tag_2 Folder_2/Tag_1 Folder_2/Tag_2 After migration Folder_1/Tag_1 Folder_1/Tag_2 Folder_2/Tag_1#Mig1 Folder_2/Tag_2#Mig1
88
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. 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.
See also
Engineering system (Page 1461)
89
4.6.1.3
Introduction
When you migrate a project, data from a WinCC flexible project is loaded into a new project for WinCC. A new project is therefore created automatically for project migration. You cannot migrate to an existing project. The migration can be started in both the Portal view and the Project view. You should only migrate a project in a newly started TIA portal. Information on the migration of integrated project can be found in the Chapter Migrating integrated projects (WinCC flexible) (Page 106). 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.
90
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.
91
See also
Migrating integrated projects (WinCC flexible) (Page 106)
4.6.1.4
92
4.6.2
4.6.2.1
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.
93
See also
Object support during migration (WinCC flexible) (Page 94) Migration (WinCC flexible) (Page 87) Migration of alarm classes and alarm groups (WinCC flexible) (Page 98) Migration of language-dependent contents (WinCC flexible) (Page 100) Migrating libraries (WinCC flexible) (Page 103) Migration tags (WinCC flexible) (Page 97) Changes of values of object properties by the migration (WinCC flexible) (Page 96)
4.6.2.2
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.
94
95
See also
Supported HMI devices (WinCC flexible) (Page 93) Changes of values of object properties by the migration (WinCC flexible) (Page 96)
4.6.2.3
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.
96
See also
Supported HMI devices (WinCC flexible) (Page 93) Object support during migration (WinCC flexible) (Page 94)
4.6.2.4
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 tags
Tags are always fully migrated. Only the data type names and tag names may change due to migration.
See also
Basics on migration (WinCC flexible) (Page 88) Migration of data types (WinCC flexible) (Page 109) Supported HMI devices (WinCC flexible) (Page 93)
97
4.6.2.5
The names of the alarm classes can be changed as necessary after migration.
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.
98
The names of the alarm classes can be changed as necessary after migration.
99
See also
Supported HMI devices (WinCC flexible) (Page 93)
4.6.2.6
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.
100
101
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
102
See also
Supported HMI devices (WinCC flexible) (Page 93)
4.6.2.7
Introduction
You need to consider two different cases when migrating from libraries: 1. Migrating a project library 2. Migrating a global library
See also
Supported HMI devices (WinCC flexible) (Page 93)
103
4.6.3
4.6.3.1
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.
See also
Migration (WinCC flexible) (Page 87) Backing up recipe data and user administration (WinCC flexible) (Page 104) Restoring recipe data and user administration (WinCC flexible) (Page 105)
4.6.3.2
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.
104
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 104) Restoring recipe data and user administration (WinCC flexible) (Page 105)
4.6.3.3
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.
105
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 104) Backing up recipe data and user administration (WinCC flexible) (Page 104)
4.6.4
4.6.4.1
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.
106
See also
Basics on migration (WinCC flexible) (Page 88)
4.6.4.2
Introduction
When migrating an integrated project, the components from both the WinCC flexible project and the STEP 7 project will be migrated. This means you need to select the project file with the file extension "*.s7p" for migration. During migration, the data is copied from the existing project and migrated to a new project. You cannot migrate to an existing project. The migration can be started in both the Portal view and the Project view. You should only migrate a project in a newly started TIA portal. If you only want to save the project in migration format, you can use the migration tool. See Basics on migration (WinCC flexible) (Page 88) for additional information.
Requirement
STEP 7 V5.4 SP5 or STEP 7 V5.5 and all add-on packages used are installed. STEP 7 and all add-on packages used are installed. The TIA portal is newly started. No project is open in WinCC.
107
Procedure
Proceed as follows to migrate an integrated project in the Portal view: 1. Select the action "Start > Migrate Project".
2. In the "Source path" box, navigate to the project you want to migrate.
3. Select the "*.s7p" project file. 4. Change the information for the project to be created, if necessary. For example, change the project name or project path. The data to be migrated is created in the new project.
108
See also
Basics on migration (WinCC flexible) (Page 88)
4.6.5
4.6.5.1
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.
109
See also
Migration (WinCC flexible) (Page 87) Migrating data types of Allen-Bradley DF1 (WinCC flexible) (Page 111) Migrating data types of Allen-Bradley Ethernet IP (WinCC flexible) (Page 111) Migrating data types of Mitsubishi FX (WinCC flexible) (Page 112) Migrating data types of Modicon Modbus (WinCC flexible) (Page 112) Migrating data types of Modicon Modbus TCP/IP (WinCC flexible) (Page 113) Migrating data types of Omron Hostlink/Multilink (WinCC flexible) (Page 113) Migrating data types of SIMATIC S7 200 (WinCC flexible) (Page 114) Migrating data types of SIMATIC S7 300/400 (WinCC flexible) (Page 114)
110
4.6.5.2
See also
Migration of data types (WinCC flexible) (Page 109)
4.6.5.3
See also
Migration of data types (WinCC flexible) (Page 109)
111
4.6.5.4
See also
Migration of data types (WinCC flexible) (Page 109)
4.6.5.5
112
See also
Migration of data types (WinCC flexible) (Page 109)
4.6.5.6
See also
Migration of data types (WinCC flexible) (Page 109)
4.6.5.7
113
See also
Migration of data types (WinCC flexible) (Page 109)
4.6.5.8
See also
Migration of data types (WinCC flexible) (Page 109)
4.6.5.9
114
115
WinCC
Tag Counter_Actual_Value Counter_Setpoint_Value Counter_Setpoint_Value#2 S7 data type Counter Word Word Address %C10 %DB10.%DB W200 %MW20 Coding <Standard> SimaticBCDCounter SimaticBCDCounter Comment BCD coded counter value BCD coded counter value BCD coded counter value
116
WinCC
Tag Timer_Actual_Value Timer_Setpoint_Value Timer_Setpoint_Value#2 S7 data type Timer S5Time S5Time Address %T10 %DB10.%DBW200 %MW20 Comment BCD coded timer value BCD coded timer value BCD coded timer value
See also
Migration of data types (WinCC flexible) (Page 109)
4.7
4.7.1
Introduction
When an integrated project is migrated, the complete project will be migrated with components from Wind and STEP 7. Configured connections between control and visualization remain intact.
117
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.
118
See also
Post-editing integrated projects (Page 119)
4.7.2
Procedure
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.
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.
119
See also
Converting unspecified CPUs into specified CPUs (Page 120) Creating an integrated HMI connection (Page 122) Re-linking HMI tags (Page 124) Deleting an unspecified connection (Page 125)
4.7.3
120
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 122)
121
4.7.4
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.
122
Result
The following figure shows the state after the integrated connection has been created:
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 124)
123
4.7.5
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.
124
See also
Deleting an unspecified connection (Page 125)
4.7.6
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.
125
First steps
5.1 Getting Started Documentation
5
The Getting Started documentation is available to help you begin using the TIA portal. The Getting Started documentation contains instructions which show you, step-by-step how to create a project in the TIA portal and give you the chance to get a quick overview of all the possibilities the TIA portal offers you.
Contents
The Getting Started documents describe the creation of a single, continuous project that is extended with each chapter. You start with simple basic functions, and use more complex ones as you continue with the creation of the project. In addition to the step-by-step instructions, the Getting Started documents also give you background information that explains the functions used and illustrate how they relate to each other.
Target audience
The Getting Started documents are intended for beginners, but are also useful for users migrating from a previous version of SIMATIC STEP 7 and WinCC.
Download
The documentation is available, free of charge at the Service&Support (https:// support.automation.siemens.com) portal in PDF form. You can download the documents here: STEP 7 Basic (http://support.automation.siemens.com/WW/view/en/40263542/0/en) STEP 7 Professional (http://support.automation.siemens.com/WW/view/en/ 28919804/133300)
127
6.1.1.2 Overview
The following table shows the application settings that you can make:
129
130
See also
Starting and exiting the TIA Portal (Page 129) Resetting the user interface layout (Page 159) Changing the settings (Page 133)
6.1.1.3 Overview
The following table shows the available settings for script and text editors:
Group Font Font colors Setting Font type and size Color settings Description Sets the font type and size for the text in text editors. You can choose the colors for individual text elements from the respective drop-down lists in the text editors. Optional settings are available for the following text elements: Text Keywords Comments Translatable comments Instructions Scripts Standard functions System functions Constant strings Constant tags Tags Object models Formal parameters Reset to default Tabs Tab width Use tabs Use spaces Indent Indention at start of paragraph Resets all font colors in editors to their factory settings. Sets the width of tabs. Enables the use of tabs. Specifies use of space characters instead of tabs. Specifies whether the start of a new paragraph is to be indented. The following selection options are available: None No indentation is used at the beginning of a paragraph in editors. Block The first line of a paragraph in the editors is automatically indented. Smart The program code is detected and the paragraphs are automatically indented to improve readability of the syntax.
131
See also
Changing the settings (Page 133)
6.1.1.4 Overview
See also
Changing the settings (Page 133)
132
6.1.1.5 Procedure
To change the settings, proceed as follows: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. Select the "General" group in the area navigation to change the settings described in the previous sections. Or click on one of the other entries in area navigation to make settings for your installed products. 3. Change the settings.
Result
The change will be adopted immediately, there is no need to save it explicitly.
See also
Overview of the program settings (Page 129) Overview of the script and text editor settings (Page 131) Overview of the print settings (Page 132)
6.1.2
6.1.2.1 Views
Two different views are available for your automation project: The portal view is a task-oriented view of the project tasks. The project view is a view of the components of the project, as well as the relevant work areas and editors. You can change over between the two views using a link.
6.1.2.2
Portal view
133
Portals
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
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.
134
See also
Project navigation (Page 137) Basics of the work area (Page 140) Inspector window (Page 148) Basics on task cards (Page 150) Details view (Page 152)
6.1.2.3
Project view
135
Title bar Menu bar Toolbar Project tree (Page 137) Work area (Page 140) Task cards (Page 150) Details view (Page 152) Inspector window (Page 148) Changing to the Portal view (Page 133) Editor bar Status bar with progress display
136
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.
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.
6.1.2.4
Project navigation
137
138
Title bar
Common data Document information Languages & resources Online access SIMATIC Card Reader
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 142)
Toolbar
You can do the following tasks in the toolbar of the project tree: Create a new user folder; for example, in order to group blocks in the "Program blocks" folder. Navigate forward to the source of a link and back to the link itself. There are two buttons for links in the project tree. You can use these to navigate from the link to the source and back. Show an overview of the selected object in the work area. When the overview is displayed, the lower-level objects and actions of the elements in the project tree are hidden.
Project
You will find all the objects and actions related to the project in the "Project" folder, e.g.: Devices Languages & resources Online access
Device
There is a separate folder for each device in the project, which has an internal project name. Objects and actions belonging to the device are arranged inside this folder.
Common data
This folder contains data that you can use across more than one device, such as common message classes, scripts and text lists.
139
Document information
In this folder, you can specify the layout for project documentation to be printed at a later point.
Online access
This folder contains all the interfaces of the programming device / PC, even if they are not used for communication with a module.
See also
Portal view (Page 133) Project view (Page 135) Basics of the work area (Page 140) Inspector window (Page 148) Basics on task cards (Page 150) Details view (Page 152)
6.1.2.5
Work area
140
Title bar of left-hand editor Work area of left-hand editor Title bar of right-hand editor Work area of right-hand editor
141
See also
Maximizing and minimizing the work area (Page 142) Splitting the work area (Page 144) Floating the work area elements (Page 144) Using grouped elements of the work area (Page 145) Minimizing and maximizing elements of the work area (Page 147) Switching between the elements in the work area (Page 147) Saving a layout of editors and tables (Page 158) Save user interface layout (Page 156)
142
See also
Basics of the work area (Page 140) Splitting the work area (Page 144) Floating the work area elements (Page 144) Using grouped elements of the work area (Page 145) Minimizing and maximizing elements of the work area (Page 147) Switching between the elements in the work area (Page 147) Saving a layout of editors and tables (Page 158)
143
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 140) Maximizing and minimizing the work area (Page 142) Floating the work area elements (Page 144) Using grouped elements of the work area (Page 145) Minimizing and maximizing elements of the work area (Page 147) Switching between the elements in the work area (Page 147) Saving a layout of editors and tables (Page 158)
144
See also
Basics of the work area (Page 140) Maximizing and minimizing the work area (Page 142) Splitting the work area (Page 144) Using grouped elements of the work area (Page 145) Minimizing and maximizing elements of the work area (Page 147) Switching between the elements in the work area (Page 147) Saving a layout of editors and tables (Page 158)
145
See also
Basics of the work area (Page 140) Maximizing and minimizing the work area (Page 142) Splitting the work area (Page 144) Floating the work area elements (Page 144) Minimizing and maximizing elements of the work area (Page 147) Switching between the elements in the work area (Page 147) Saving a layout of editors and tables (Page 158)
146
See also
Basics of the work area (Page 140) Maximizing and minimizing the work area (Page 142) Splitting the work area (Page 144) Floating the work area elements (Page 144) Using grouped elements of the work area (Page 145) Switching between the elements in the work area (Page 147) Saving a layout of editors and tables (Page 158)
147
See also
Basics of the work area (Page 140) Maximizing and minimizing the work area (Page 142) Splitting the work area (Page 144) Floating the work area elements (Page 144) Using grouped elements of the work area (Page 145) Minimizing and maximizing elements of the work area (Page 147) Saving a layout of editors and tables (Page 158)
6.1.2.6
Inspector window
4 5
148
"Properties" tab "Info" tab "Diagnostics" tab Navigation within the tabs: Area navigation within the "Properties" tab Lower-level tabs in the "Info" and "Diagnostics" tabs
"Properties" tab
This tab displays the properties of the object selected. You can change editable properties here.
"Info" tab
This tab displays additional information on the object selected, as well as alarms on the actions executed (such as compiling).
"Diagnostics" tab
This tab provides information on system diagnostics events, configured alarm events, and connection diagnostics.
149
See also
Project navigation (Page 137) Basics of the work area (Page 140) Portal view (Page 133) Project view (Page 135) Basics on task cards (Page 150) Details view (Page 152)
6.1.2.7
Task cards
150
See also
Task cards closed "Libraries" task card open "Project library" pane open "Global libraries" pane closed
Changing the pane mode (Page 152) Project navigation (Page 137) Basics of the work area (Page 140) Inspector window (Page 148) Portal view (Page 133) Project view (Page 135) Details view (Page 152)
151
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 150)
6.1.2.8
Details view
152
Title bar
The arrow for closing the details view is located in the title bar of the details view. After it has closed, the direction in which the arrow is pointing changes from left to right. It can now be used to reopen the details view.
Objects
The displayed content varies depending on the selected object. You can move the content of objects from the details view to the required location using drag-and-drop.
See also
Project navigation (Page 137) Basics of the work area (Page 140) Inspector window (Page 148) Basics on task cards (Page 150) Portal view (Page 133) Project view (Page 135)
6.1.2.9
Overview window
153
Overview window Switch to the Details view Switch to the List view Switch to the Icon view Move to higher level Split the overview window in two. Either the right or left half of the overview window is synchronized. Clicking again cancels the split. Contents of the object selected in the project tree.
154
See also
Comparing objects (Page 155) Showing or hiding additional columns (Page 155)
Comparing objects
You can display the contents of two folders or objects side by side in the Overview window. The Overview window is split in half and you can display different contents on the left and right sides. In addition, you can use a drag-and-drop operation to move objects between the split windows. Thus, for example, you can move contents from one window to the other.
Procedure
To split the Overview window in half or cancel the split, follow these steps: 1. In the toolbar, click on the "Synchronize left side" or "Synchronize right side" icon to split the overview window. Either the left or the right side of the overview window synchronized with the contents of the selected object in the project tree. 2. To cancel the split, click again on the previously selected icon.
See also
Overview window (Page 153)
155
Procedure
To show or hide additional table columns, follow these steps: 1. Right-click the title bar of the table. 2. Select the "Show/Hide" command in the shortcut menu, and select the columns you want to display.
See also
Overview window (Page 153)
6.1.2.10
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 156) Load window layout (Page 157) Managing window layouts (Page 158) Saving a layout of editors and tables (Page 158) Resetting the user interface layout (Page 159) Basics of the work area (Page 140)
156
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. 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 156)
157
See also
Save user interface layout (Page 156)
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 156)
158
Procedure
To save the layout of editors and tables in the work area, follow these steps: 1. Adapt the editor or table according to your requirements. 2. Click the "Remember Layout" button in the editor or table.
Result
The layout is saved. When you reopen the editor or table, this layout will be used.
See also
Basics of the work area (Page 140) Maximizing and minimizing the work area (Page 142) Splitting the work area (Page 144) Floating the work area elements (Page 144) Using grouped elements of the work area (Page 145) Minimizing and maximizing elements of the work area (Page 147) Switching between the elements in the work area (Page 147) Save user interface layout (Page 156)
Procedure
To reset the user interface settings to the factory settings, follow these steps: 1. Select the "Settings" command in the "Options" menu. The "Settings" window is displayed in the work area. 2. Select the "General" group in the area navigation. 3. Click the "Reset to default" button under "Layout > Reset layout".
Result
The default settings for the user interface are restored.
159
See also
Overview of the program settings (Page 129) Save user interface layout (Page 156)
6.1.3
6.1.3.1
Keyboard shortcuts
Keyboard shortcuts for project editing
Editing a project
Function Open a project Close a project Save a project Save a project under a different name Print project Compile a project Undo last action Redo last action Key combination <Ctrl+O> <Ctrl+W> <Ctrl+S> <Ctrl+Shift+S> <Ctrl+P> <Ctrl+B> <Ctrl+Z> <Ctrl+Y> Menu command Project > Open Project > Close Project > Save Project > Save as Project > Print Edit > Compile Edit > Undo Edit > Redo
160
6.1.3.2
6.1.3.3
6.1.3.4
161
Navigate in tables
Function Go to the next cell Go to the next editable cell on the right Go to the next editable cell on the left Move a screen upwards Move a screen downwards Go to the first cell in the row Go to the last cell in the row Go to the first cell in the table Go to the last cell in the table Go to the top cell in the column Go to the bottom cell in the column Key combination <Arrow keys> <Tab> <Shift+Tab> <PgUp> <PgDn> <Home> <End> <Ctrl+Home> <Ctrl+End> <Ctrl+up arrow> <Ctrl+down arrow>
Switch to insert or overwrite mode Exit edit mode Delete Delete characters
162
6.1.3.6
Introduction
When working with the TIA portal, you also have the Microsoft on-screen keyboard available.
6.1.4
6.1.4.1
163
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
164
6.2
6.2.1
165
Help
The Help system describes concepts, instructions and functions. It also contains reference information and examples. The help opens in a separate window. A navigation pane appears on the left side of the help window. You can also hide the navigation pane to make room on the screen. The navigation pane provides you with the following functions: Table of contents Search in the index Full text search of the entire Help Favorites
Roll-out
Certain text boxes offer information that rolls out and helps you to enter valid parameters and values. The roll-out informs you about permissible value ranges and data types of the text boxes. The following figure shows a roll-out (yellow) and a roll-out error message (red), which indicates an invalid value:
166
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 appears to the corresponding Help topic in the cascade. If you click on the link, the corresponding topic opens in Help. The following figure shows a tooltip with opened cascade:
167
See also
Disabling the automatic display of tooltip cascades (Page 171)
6.2.2
168
6.2.3
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.
169
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.
170
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 information
You can either print all the contents of the Help system or individual topics only.
Procedure
To select the topics you would like to print, follow these steps: 1. Click the "Display printing dialog" button. The table of contents opens in a separate window. 2. Select the check boxes for the folders and help topics to be printed in the "Print help topics" dialog. 3. Click the "Print" button to print the selected information. The "Print" dialog opens. 4. Select the printer on which you want print the help topics. 5. Click "Properties" if you want to make additional printer settings. 6. Confirm your entries with "OK". The help topics are printed out on the selected printer.
6.2.7
171
Procedure
To disable the automatic display of tooltip cascades, follow these steps: 1. In the "Options" menu, select the "Settings" command. 2. Select the "General" group in the area navigation. 3. Disable the "Open cascade automatically in tooltips" check box in the "General settings". If you want to display a tooltip cascade manually, click on the arrow icon within the tooltip.
See also
General remarks on the information system (Page 165)
6.2.8
Safety Guidelines
Safety guidelines
This Help manual contains you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger. DANGER indicates that death or severe personal injury will result if proper precautions are not taken. WARNING indicates that death or severe personal injury may result if proper precautions are not taken. CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken. CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken. NOTICE indicates that an unintended result or situation can occur if the corresponding information is not taken into account.
172
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning and operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes in this documentation qualified persons are defined as persons who are authorized to commission, ground and label devices, systems and circuits in accordance with established safety practices and standards.
Prescribed Usage
Note the following: WARNING This device may only be used for the applications described in the catalog or the technical description and only in connection with devices or components from other manufacturers which have been approved or recommended by Siemens. Correct, reliable operation of the product requires proper transport, storage, positioning and assembly as well as careful operation and maintenance.
Trademarks
All names identified by are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
173
Editing projects
7.1 The basics of projects
Introduction
Projects are used to organize the storage of data and programs resulting from the creation of an automation solution. The data that makes up a project includes the following: Configuration data on the hardware structure and parameter assignment data for modules Project engineering data for communication over networks Project engineering data for the devices
Project hierarchy
Data is stored in a project in the form of objects. Within the project, the objects are arranged in a tree structure (project hierarchy). The project hierarchy is based on the devices and stations along with the configuration data and programs belonging to them. Common data of the project and online access, for example, are also displayed in the project tree.
See also
Creating a new project (Page 176) Opening projects (Page 176) Saving projects (Page 178) Deleting projects (Page 179)
175
7.2
7.2.1
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 175) Opening projects (Page 176) Saving projects (Page 178) Deleting projects (Page 179)
7.2.2
Procedure
Opening projects
To open an existing project, follow these steps: 1. Select the "Open" command in the "Project" menu. The "Open project" dialog opens and includes the list of most recently used projects. 2. Select a project from the list and click "Open". 3. If the project you require is not included in the list, click the "Browse" button. Navigate to the desired project folder, and open the project file. Projects of the TIA Portal V11 have the extension ".ap11", while older projects from the TIA Portal V10 have the extension "ap10".
Result
The project opens in the project view.
176
Notes on compatibility
When you open a project that was created with an older version of the TIA Portal, the project is converted automatically to the current file format and saved as a new project. The designation "_V11" is added to the file name of the new project. If you want to open a project from a newer version, this is possible if the following conditions are met: The project was created with a different version of the TIA Portal V11, for example, a version with an installed service pack. The project does not contain any data that is incompatible with the current installation. If the project to be opened contains data that was created with optional software, but the corresponding software product is not installed, the following cases can occur: Software components are missing, but none of them are essential: A dialog appears listing the missing software components. After the project is opened, its properties are displayed. You now have the opportunity to install the missing products. All the devices contained in the project are available even if you do not install the missing products. However, you can only work with the devices that are supported by the currently installed software. If devices are not supported because software is missing, they are marked with the following symbol in the project tree: At least one software package is required in order to open the project: A dialog appears listing the missing software components. The essential package(s) are marked. The project can only be opened if you install the missing components.
See also
The basics of projects (Page 175) Creating a new project (Page 176) Saving projects (Page 178) Deleting projects (Page 179)
7.2.3
177
Procedure
To display the project properties, follow these steps: 1. Select the open project in the project tree. 2. Select "Properties" in the shortcut menu of the project. The dialog with the properties of the project opens. 3. Select the project properties in the area navigation that you want to have displayed.
7.2.4
Saving projects
You can save the project at any time either under the same or a different name. You can even save a project when it still contains elements with errors.
Saving a project
To save a project, follow these steps: 1. Select the "Save" command in the "Project" menu. All changes to the project are saved under the current project name.
Project Save as
To save a project under another name, follow these steps: 1. Select the "Save as" command in the "Project" menu. The "Save current project as" dialog opens. 2. Select the project folder in the "Save in" box. 3. Enter the new project name in the "File name" box. 4. Confirm your entry with "Save". The project is saved under the new name and opened.
See also
The basics of projects (Page 175) Creating a new project (Page 176) Opening projects (Page 176) Deleting projects (Page 179)
178
7.2.5
Procedure
Closing projects
To close a project, follow these steps: 1. Select the "Close" command in the "Project" menu. If you have made changes to the project since the last time you saved it, a message is displayed. 2. Decide whether or not you want to save the changes.
7.2.6
Deleting projects
NOTICE When you delete a project, the entire project data is removed from the storage medium.
Requirements
The project you want to delete is not open.
Procedure
Follow the steps below to delete an existing project: 1. Select the "Delete project" command in the "Project" menu. The "Delete project" dialog opens and includes the list of most recently used projects. 2. Select a project from the list. If the project you require is not included in the list, click the "Browse" button. Navigate to the required project folder, and open the project file with the extension ".ap11". 3. Click the "Delete" button. 4. Click "Yes" to confirm. This starts the deletion of the project.
Result
The entire project folder is deleted from the file system.
See also
The basics of projects (Page 175) Creating a new project (Page 176) Opening projects (Page 176) Saving projects (Page 178)
179
7.2.7
7.2.7.1
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".
180
Translating texts
There are three ways of translating texts. Translating texts directly You can enter the translations for the individual project languages directly in the "Project texts" table. You will find this in the project tree under "Languages & Resources > Project texts". Translating texts using reference texts You can change the editing language for shorter texts. All the text cells are filled again with the default values and can be filled in the current language. As orientation, you can display what you last entered in the box in the reference language. To do this, select the "Tasks" task card and open the "Languages & resources". Exporting texts and translating them externally With larger volumes of text, you can export the texts to an Office Open XML file and translate them with a normal table calculation program. You then import the translated texts again into the TIA Portal. Note Using Asian project languages East Asian project languages are only displayed correctly in Windows XP, if the option "Install files for East Asian languages" is selected on the Languages tab of Regional and Language Options in the Control Panel of Windows XP Professional.
See also
Overview of the program settings (Page 129) Changing the settings (Page 133) Application examples for multilanguage projects (Page 186)
7.2.7.2
181
Requirement
You are in the project view. A project is open.
Procedure
To select the project languages, follow these steps: 1. Click on the arrow symbol to the left of "Languages & Resources" in the project tree. The elements below this are displayed. 2. Double-click on "Project languages". In the work area, you will see a list of languages that you can select. 3. Select the required languages.
Result
All texts can be displayed in the activated languages if there is already a translation for these languages.
7.2.7.3
Requirement
You are in the project view. A project is open.
Procedure
To change the editing language, follow these steps: 1. Click on the arrow symbol to the left of "Languages & Resources" in the project tree. The lower-level elements are displayed. 2. Double-click on "Project languages". The possible settings for the project languages are displayed in the work area. 3. Select the editing language in "General > Editing language".
7.2.7.4
182
Requirement
You are in the project view. A project is open. You have selected at least one further project language.
Procedure
To translate individual texts, follow these steps: 1. Click on the arrow symbol to the left of "Languages & Resources" in the project tree. The elements below this are displayed. 2. Double-click "Project texts". A list with the user texts in the project is displayed in the work area. 3. Click on "System texts" if you you want to edit the list of system texts rather than the user texts. 4. You can improve the clarity of the lists if you have a lot of texts. To group identical texts and to translate them all at once, click the "Switch on/off grouping" button in the toolbar. To hide texts that do not have a translation, click the "Filter for empty texts on/off" button in the toolbar. To further limit the displayed project texts to certain devices, select the devices for which you want to display project texts in the drop-down list. 5. Enter the translation of the project texts in the relevant column. Note If there is no translation for a text in a particular language, the English text is displayed.
7.2.7.5
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.
183
Requirement
There is at least one translation into a different project language for an input field.
Procedure
To display the translation of an input cell in a reference language, follow these steps: 1. In the "Tasks" task card, select the "Languages & Resources" pane. 2. Select a reference language from the "Reference language" drop-down list.
Result
The reference language is preset. If you click in a text box, translations that already exist in other project languages are shown in the "Tasks > Languages & Resources" task card.
See also
Application examples for multilanguage projects (Page 186)
7.2.7.6
184
185
See also
Application examples for multilanguage projects (Page 186)
7.2.7.7
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.
186
See also
Project text basics (Page 180) Exporting and importing project texts (Page 184) Translating texts using reference texts (Page 183)
7.3
7.3.1
7.3.1.1
187
See also
Compiling project data (Page 188)
Procedure
To compile project data, follow these steps: 1. In the project tree, right-click on the device for which you want to compile the project data. 2. Select the option you require in "Compile" submenu of the shortcut menu. Note Note that the options available to you depend on the selected device. The project data is compiled. You can check whether or not the compilation was successful in the Inspector window with "Info > Compile".
See also
General information on compiling project data (Page 187)
188
7.3.1.2
See also
Downloading project data to a device (Page 190) Loading project data to an accessible device (Page 191) Downloading project data to a memory card (Page 192) Uploading project data from a device (Page 192)
189
Requirement
The project data is consistent. Each device to which you want to download is accessible via an online access.
Procedure
To download the project data to the selected devices, follow these steps: 1. Select one or more devices systems in the project tree. 2. Right-click on a selected element. The shortcut menu opens. 3. Select the option you require in the shortcut menu of the "Download to device" submenu. Note Note that the options available to you depend on the selected device. When necessary, the project data is compiled. If you had previously established an online connection, the "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for downloading. If you had not previously established an online connection, the "Extended download to device" dialog opens, and you must first select the interfaces via which you want to establish the online connection to the device. See also: Establishing and canceling an online connection (Page 1480) 4. Check the messages in the "Load preview" dialog, and select the actions in the "Action" column, if necessary. NOTICE Performing the proposed actions while the plant is in operation can cause serious bodily injury and property damage in the event of malfunctions or program errors. Make sure that no dangerous situations can arise before you start the actions! As soon as loading becomes possible, the "Load" button is enabled. 5. Click the "Load" button. 6. The loading operation is performed. The "Load results" dialog then opens. In this dialog, you can check whether or not the loading operation was successful and take any further action that may be necessary. 7. Click the "Finish" button.
190
Result
The selected project data was downloaded to the devices.
See also
General information on loading (Page 189) Loading project data to an accessible device (Page 191) Downloading project data to a memory card (Page 192) Uploading project data from a device (Page 192)
Requirement
The accessible devices are displayed. See also: Displaying accessible devices (Page 1478)
Procedure
To load project data to an accessible device, follow these steps: 1. In the project tree, drag the folder containing your device to the accessible device. The "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for downloading. 2. Check the messages, and select the actions in the "Action" column, if necessary. NOTICE Performing the proposed actions while the plant is in operation can cause serious bodily injury and property damage in the event of malfunctions or program errors. Make sure that no dangerous situations can arise before you start the actions! 3. As soon as loading becomes possible, the "Load" button is enabled. 4. Click the "Load" button. The loading operation is performed. The "Load results" dialog then opens. In this dialog, you can check whether or not the loading operation was successful and take any further action that may be necessary. 5. Click the "Finish" button.
191
See also
General information on loading (Page 189) Downloading project data to a device (Page 190) Downloading project data to a memory card (Page 192) Uploading project data from a device (Page 192)
Procedure
To download project data to a memory card, follow these steps: 1. Use a drag-and-drop operation in the project tree to take the project data you want to download and move it to the memory card. The "Load preview" dialog opens. This dialog displays messages and proposes actions necessary for downloading. 2. Check the messages, and select the actions in the "Action" column, if necessary. As soon as loading becomes possible, the "Load" button is enabled. 3. Click the "Load" button. The loading operation is performed. The "Load results" dialog then opens. In this dialog, you can check whether or not the loading operation was successful and take any further action that may be necessary. 4. Click the "Finish" button.
See also
General information on loading (Page 189) Downloading project data to a device (Page 190) Loading project data to an accessible device (Page 191) Uploading project data from a device (Page 192)
192
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.
193
See also
General information on loading (Page 189) Downloading project data to a device (Page 190) Loading project data to an accessible device (Page 191) Downloading project data to a memory card (Page 192)
7.3.2
7.3.2.1 Function
You have the option of comparing project data of the same type in order to determine possible discrepancies. For example, you can compare a hardware configuration with another hardware configuration. A simple online-online comparison is already performed when you establish an online connection. During this process, comparable objects in the project tree are marked with icons that represent the result of the comparison. Beyond this marking, you can use the comparison editor to compare project data and have detailed information displayed. You can also select actions for non-identical objects in the comparison editor. In addition to the online-offline comparison, there is also an offline-offline comparison available. This allows you to compare project data of two devices within one project or from different projects. Which project data you can compare depends on the products installed.
194
Comparison icons
The result of the comparison is indicated by means of icons. The following table shows the relevant icons and their meaning:
Icon Meaning Folder contains objects whose online and offline versions differ Comparison result is not known Online and offline versions of the object are identical Online and offline versions of the object are different Object only exists offline Object only exists online
7.3.3
7.3.3.1
Introduction
You can protect your project data from unauthorized access. These include, for example: Access protection for devices Copy and display protection of objects Restrictions for printouts of know-how-protected objects Note that every protection mechanism is not available for all objects. How to protect specific objects is described in the online help of the product.
195
See also
Printing project data (Page 213)
7.3.3.2
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 195)
7.3.4
7.3.4.1
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.
196
See also
Creating a frame (Page 202) Creating a cover page (Page 203) Editing cover pages and frames (Page 204) Entering document information (Page 200)
7.3.4.2
197
Scope of printout
To be able to print, at least one printable element has to be selected. If a selected object is printed, all subordinate objects are also printed. For example, if a device is selected in the project tree, all of its data is also printed. When table contents are printed, all lines in the table in which a cell is selected are printed. In order to print one or more table columns, the desired columns must be selected. If no individual cells or columns are selected, the entire table is printed.
See also
Printing project data (Page 213)
7.3.4.3
198
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
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 132)
7.3.4.4
199
7.3.4.5
200
Procedure
To add metadata, follow these steps: 1. To create new document information, double-click "Add new document information" under "Documentation information > Document information" in the project tree. The new document information is created and opened immediately. 2. Enter a name for the set in the "Name" field. 3. Fill in the individual fields with the metadata for the project.
7.3.4.6
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.
201
See also
Library basics (Page 227) "Libraries" task card (Page 229) Global library basics (Page 240) Designing cover pages and frames (Page 204) Using ready-made frames and cover pages (Page 203)
Creating a frame
You can create any number of frames for each project. The frames are stored in the project tree below the "Documentation information > Frames" group. You can assign a frame to all document information. When you select document information for printing, its associated frame is used.
Procedure
To create a new frame, follow these steps: 1. Double-click the entry "Add new frame" below the "Documentation information > Frames" group in the project tree. The "Add new frame" dialog opens. 2. Enter a name for the frame in the "Name" field. 3. Choose the paper size from the "Paper type" drop-down list. 4. Choose whether the page is to be created in portrait or landscape format in the "Orientation" drop-down list. Click the "Add" button.
Result
A new frame is created. The frame is then opened automatically in the documentation editor where it can be edited.
See also
Editing cover pages and frames (Page 204) Creating a cover page (Page 203)
202
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 204) Creating a frame (Page 202)
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.
203
See also
Using cover pages and frames (Page 201) Editing cover pages and frames (Page 204)
7.3.4.7
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 203) Creating a frame (Page 202) General operation of the documentation editor (Page 205)
204
205
Toolbar The toolbar provides the following tools (from left to right): Insert background image Inserts a background image into the template or cover page. Arrow tool Enables object selection. Navigation tool Allows shifting of the partial page. Zoom-in button Magnifies the page display incrementally. Zoom-out button Reduces the page display incrementally. Selecting a zoom factor Adapts the page size to the area selected with the lasso zoom tool. Dynamic zoom Adapts the page width to the work area. Work area You can design the cover page or frame in the work area. "Toolbox" task card The "Toolbox" task card contains various types of placeholders that you can use on the cover sheet or frame. The placeholders can be placed in the work place using a drag-and-drop operation. Properties in the Inspector window You can display and modify the properties of the currently selected object in the "Properties" tab of the Inspector window. For example, you can modify the properties of the page, format text, specify the position of objects on the page, etc.
206
207
See also
Editing cover pages and frames (Page 204) Inserting a background image (Page 208) Specifying the print area (Page 208) Inserting placeholders for metadata (Page 209)
Requirement
The background image must be in EMF or PDF format. A cover page is open in the documentation editor.
Procedure
To insert a background image, follow these steps: 1. Click the "Add background image" button. The "Open" dialog box opens. 2. Select the background image in the file system. 3. Click the "Open" button. The background image is inserted in its original size at the top left page margin.
See also
Creating a cover page (Page 203) General operation of the documentation editor (Page 205)
208
Requirement
A frame is open in the documentation editor.
Procedure
To define an area for the printed contents, follow these steps: 1. Click on the slightly darker area within the page display in the documentation editor to select the area for the print content. This opens the properties of the area to be printed in the Inspector window. 2. Enter the position of the print area on the X and Y axes in the Inspector window. 3. Specify the width and height of the print area in cm in the Inspector window. Alternatively, you can change the width and position of the print area in the graphic display of the page. To do so, use the mouse to drag the margins of the print area until the desired size and position are achieved.
See also
Creating a frame (Page 202) General operation of the documentation editor (Page 205)
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.
209
Requirement
An cover page or frame is open in the documentation editor.
Procedure
To insert placeholders for metadata on the cover sheet or in a frame, follow these steps: 1. Drag a field from the "Toolbox > Elements" task card to the work area of the documentation editor. The placeholder is inserted. The placeholder properties are shown in the Inspector window and can be edited there. 2. Select the metadata to be inserted during printing from the "Text" drop-down list in the Inspector window under "Properties > General > Text box". Alternatively, you have the option of entering free text or selecting an image depending on the type of placeholder. 3. In the Inspector window under "Properties > General > Position and size", specify the position of the placeholder on the X and Y axis and enter the width and height of the text box in cm. You specify the sequence of the objects in the "Z-Order" field, if these overlap. The smaller the value, the further down an object is located. 4. In the Inspector window, go to "Properties > View" and select the font formatting and the orientation of the text as well as the alignment of the text. You cannot make this setting for images.
See also
General operation of the documentation editor (Page 205)
7.3.4.8
210
Procedure
To create a print preview and to set the scope of the later printout, follow these steps: 1. Select the "Print preview" command in the "Project" menu. The "Print preview" dialog opens. 2. Select the frame layout you want to use for the printout. In the "Document information" drop-down list, select the documentation information you want to use later for the printout. Select the "Print cover page" check box to print the cover page, which is specified in the selected document information. Select the "Print table of contents" check box to add a table of contents to the printout. The check boxes for printing the cover page and the table of contents can only be selected if you have started the printout in the project tree. 3. Under "Print objects/area", select what is to be printed. The selection is only possible if you have started the printout from an editor that supports this function. Choose "All" to print out the entire content of the editor. Choose "Selection" to print only the objects currently selected in the editor. 4. Select the print scope under "Properties". Choose "All" to print all configuration data of the selected objects. Choose "Visible" to print the information of an editor that is currently visible on the screen. This option can only be chosen if you have started the printout from an editor that supports this function. Choose "Compact" to print out an abbreviated version of the project data. 5. Click "Preview" to generate the preview. A print preview is created in the work area. Note Wait time for extensive documents It can take several minutes to generate the print preview in the case of very extensive projects. You can continue working normally in the meantime on systems with adequate resources. The progress of the print preview is shown in the status bar.
See also
Operation within the print preview (Page 212)
211
Operation within the print preview Functions within the print preview
The print preview shows an exact image of the subsequent printout. You can use the buttons in the toolbar to modify the print preview display. The following functions are available (from left to right): Navigation mode Allows shifting of the partial page. To change the partial page with the navigation tool, select the arrow button in the toolbar. Then, click anywhere on the page and hold the mouse button down while moving the page to the desired position. Zoom function "Zoom in" and "Zoom out" Magnifies or reduces the page display. To zoom in or zoom out the display incrementally, select the corresponding button. Then click on the page in order to magnify (zoom in) or reduce (zoom out) the page incrementally. To zoom in on a particular area, select the "Lasso zoom" button and use the mouse to drag an outline around the area you want to focus on. To select an area to focus on, select the button "Zoom in / zoom out with rectangle". With the mouse, drag a border around the area to focus on it. To zoom dynamically through the page, select the button "Zoom in / zoom out dynamically". With pressed mouse button, scroll down over the page to zoom in. Scroll up to zoom out. Percentage value in the drop-down list Specifies the display size of the page in percent. Enter a percentage value or select a percentage value from the drop-down list. Alternatively, choose the the "Fit to page" option from the drop-down list to adapt the page size to the work area. Or, choose "Fit to width" to adapt the page width to the work area.
212
See also
Creating a print preview (Page 210)
7.3.4.9
Requirement
At least one printer is configured. The objects to be printed are not protected. If printing is restricted by access protection, you must temporarily cancel the password protection in order to release the objects for printing. Otherwise, protected objects will not be included in the printout.
213
214
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.
See also
Protection concept for project data (Page 195) Revoking access rights for devices (Page 196) Printout of project contents (Page 197) Designing cover pages and frames (Page 204)
7.4
7.4.1
Function
You can undo performed actions at any time. For this purpose, every action you perform is saved in an action stack. When undoing actions, the stack is processed from top to bottom. In other words, if you undo an action that lies further down in the stack, all actions located above it in the stack will also be undone automatically. You can redo previously undone actions until you execute a new action. Once you execute a new action, it is no longer possible to redo previously undone actions.
215
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.
216
See also
Undoing an action (Page 217) Redoing an action (Page 218)
7.4.2
Undoing an action
The following options are available for undoing actions: Undoing the last action only Only the last action performed is undone. Undoing as many actions as required Multiple actions in the action stack are undone in a single step.
See also
Basics of undoing and redoing actions (Page 215) Redoing an action (Page 218)
217
7.4.3
Redoing an action
You have the option of redoing an action that has been undone, so that you can return to the status present before "Undo" was performed. However, this is only possible until you perform a new action. The following options are available for redoing actions: Redoing the last undone action only Only the last undone action is redone. Redoing as many undone actions as required Multiple undone actions in the action stack are redone in a single step.
See also
Basics of undoing and redoing actions (Page 215) Undoing an action (Page 217)
218
7.5
7.5.1
See also
Search and replace (Page 219)
7.5.2
Using Find
The "Find and replace" function enables you to search for or replace texts in an editor.
219
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.
220
See also
Information on the search function (Page 219)
7.6
7.6.1
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".
221
See also
Exporting and importing project texts (Page 184)
7.6.2
222
Requirement
You are in the project view. A project is open. The project includes a least one device.
Procedure
To create user-defined text lists, follow these steps: 1. Click on the arrow to the left of a device in the project tree. The elements arranged below the device are displayed. 2. Double-click on "Text lists". All the text lists assigned to the device are displayed in the work area listed in a table. 3. Double-click on the first free row in the table. A new user-defined text list is created. 4. Enter a name for your new text list in the "Name" column. 5. From the drop-down list in the "Selection" column, select whether you want to specify the value ranges in decimal, binary or in bits. Depending on the device, there may be further options available at this point. 6. Enter a comment in the "Comment" column. A new user-defined text list has been created and you can now enter the value ranges and texts.
7.6.3
Requirement
You are in the project view. A project is open. The project includes a least one device.
223
7.6.4
Requirement
You are in the project view. A project is open. The project includes a least one device.
224
7.7
7.7.1
Introduction
Memory cards are plug-in cards that come in a variety of types and can be used for a variety of purposes. Depending on the device type or device family, memory cards can be used for purposes, such as: Load memory of a CPU Storage medium for projects, firmware backups, or any other files Storage medium for performing a firmware update Storage medium for the PROFINET device name For information regarding the technical variants of the respective memory cards and general information on their handling, refer to the respective documentation for the device. For information on handling memory cards in the TIA Portal, refer to the online help under keyword "Memory Card". CAUTION Do not use memory cards for non-SIMATIC-related purposes, and do not use third-party devices or Windows tools to format them. This will irrevocably overwrite the internal structure of the memory card, rendering it unusable for SIMATIC devices!
See also
Adding a user-defined card reader (Page 225) Accessing memory cards (Page 226) Displaying properties of memory cards (Page 226)
7.7.2
Introduction
If your card reader is not detected automatically, you can add it manually.
Requirement
The project view is open.
225
Procedure
To add a card reader, follow these steps: 1. Open the project tree. 2. Select "SIMATIC Card Reader > Add user-defined Card Reader" in the "Project" menu. The "Add user-defined Card Reader" dialog opens. 3. In the drop-down list box, select the path for the card reader. 4. Confirm your entries with "OK".
See also
Basics about memory cards (Page 225) Accessing memory cards (Page 226) Displaying properties of memory cards (Page 226)
7.7.3
Requirement
A memory card is inserted in the card reader. The project view is open.
Procedure
To access memory cards, follow these steps: 1. Open the project tree. 2. Select "SIMATIC Card Reader > Show SIMATIC Card Reader" in the "Project" menu. The "SIMATIC Card Reader" folder is displayed in the project tree. 3. Open the "SIMATIC Card Reader" folder. You can now access the memory card.
See also
Basics about memory cards (Page 225) Adding a user-defined card reader (Page 225) Displaying properties of memory cards (Page 226)
7.7.4
226
Requirement
A memory card is inserted in the card reader. The project view is open.
Procedure
To display the properties of a memory card, follow these steps: 1. Right-click on the memory card for which you want to display the properties. 2. Select the "Properties" command in the shortcut menu. The "Memory Card <name of the memory card>" dialog opens. The properties are displayed in this dialog.
See also
Basics about memory cards (Page 225) Adding a user-defined card reader (Page 225) Accessing memory cards (Page 226)
7.8
7.8.1
Using libraries
Library basics
Introduction
You can store objects you want to use more than once in libraries. It is possible to reuse the stored objects throughout a project or across projects. This means you can, for example, create block templates for use in different projects and adapt them to the particular requirements of your automation task.
227
Library types
Depending on the task, you can use one of the following library types: Project library Each project has its own library. Here, you store the objects you want to use more than once in the project. This project library is always opened, saved, and closed together with the current project. Global libraries You can also create other libraries in addition to the project library. Here, you store the objects you want to use in more than one project. You can create, change, save, and transfer these global libraries independent of projects. In the global libraries area, you will also find libraries that ship with the software. These include off-the-peg functions and function blocks that you can use within your project. You cannot modify the supplied libraries.
Library objects
Libraries can accommodate a large number of objects. These include, for example: Functions (FCs) Function blocks (FBs) Data blocks (DBs) Devices PLC data types Watch and force tables Process screens Faceplates For objects with know-how protection, this protection is also retained after the object is inserted into a library.
Use types
You can use the library elements as either a copy template or a type. You can use copy templates to generate copies of the library element that are independent of one another. Copy templates are marked with a black triangle in the "Libraries" task card. You can derive and use instances from types. These instances are tied to their respective type, and changes to one instance also change all other instances. Types are marked with a green triangle in the "Libraries" task card. Note Please note the following: The use as a type is not available for every object. You can only create types in the project library.
228
See also
Project library basics (Page 232) Global library basics (Page 240) "Libraries" task card (Page 229)
7.8.2
229
"Project library" pane
"Project library" pane "Global libraries" pane "Elements" pane "Parts" pane "Types" folder "Master copies" folder
In this pane, you can store the objects that you want to use more than once in the project.
230
"Elements" pane
In this pane, you can display the elements of a library.
"Parts" pane
In this pane, you can display the contents of the library elements.
"Types" folder
In this directory, you can create types of your objects in the project library and insert them as instances. You cannot create types in a global library. You can copy a type in the project library and paste it into the "Types" folder of a global library.
See also
Library basics (Page 227) Working with the project library (Page 232) Working with global libraries (Page 240) Using the elements and parts view (Page 231)
7.8.3
Introduction
When you open the "Libraries" task card the first time, the "Project library" and "Global libraries" panes are opened and the "Parts" pane is closed. You need to open the "Elements" pane explicitly. The elements view shows the elements of the selected library. You can select one of the following views:
231
Requirement
The "Libraries" task card is displayed.
Procedure
To use the elements and parts view, follow these steps: 1. Click "Open or close the element view" in the "Project library" or "Global libraries" pane.
See also
Library basics (Page 227) "Libraries" task card (Page 229) Working with the project library (Page 232) Working with global libraries (Page 240)
7.8.4
7.8.4.1 Function
In the project library, you can store the elements that you want to use more than once in the project. The project library is generated and saved automatically with the project.
See also
Library basics (Page 227)
7.8.4.2
Requirement
The "Libraries" task card is displayed.
232
Procedure
To create a new folder, follow these steps: 1. Right-click any folder within the project library. 2. Select "Add folder" from the shortcut menu. A new folder is created. 3. Enter a name for the new folder.
See also
Project library basics (Page 232) Adding elements to the project library (Page 233) Using elements of the project library (Page 235) Editing elements of a project library (Page 237) Removing elements from the project library (Page 239) Filtering the view (Page 240)
7.8.4.3
Procedure
To add a new copy template to the project library, follow these steps: 1. Open the project library in the "Project library" pane of the "Libraries" task card. 2. Select the element you want to add as a copy template to the project library, and use a drag-and-drop operation to move it to the "Master copies" folder or any of its subfolders in the project library. Release the left mouse button when a small plus symbol appears below the mouse pointer.
Result
The element is inserted into the project library as a copy template. You can generate copies from this template and use them anywhere in the TIA Portal where it is permissible.
233
See also
Library basics (Page 227) Project library basics (Page 232) Adding types to the project library (Page 234)
Procedure
To add a new type to the project library, follow these steps: 1. Open the project library in the "Project library" pane of the "Libraries" task card. 2. Right-click the "Types" folder or any of its subfolders. 3. Select the "Add new type" command in the shortcut menu. The dialog for generating types opens. Note If your installed products do not contain any objects from which types can be generated, the "Add new type" command is not available. Use master copies in this case. 4. In the dialog, choose the element from which you want to generate a type. 5. Specify all other necessary data. 6. Click "OK".
Result
A new type is generated and inserted into the project library. You can generate instances from this type and use them anywhere in the TIA Portal where it is permissible. The instances are tied to the type, i.e., changes to one instance are passed on to the other instances.
See also
Library basics (Page 227) Project library basics (Page 232) Adding master copies to the project library (Page 233)
234
7.8.4.4
Requirement
The "Libraries" task card is displayed.
Procedure
To generate and use a copy from a copy template, follow these steps: 1. Open the "Master copies" folder or any of its subfolders in the project library so that you looking at the master copy from which you want to generate a copy. 2. Use a drag-and-drop operation to move the copy template from the project library to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. A copy based on the copy template is inserted. If there is already an element with the same name at this location, the "Paste" dialog opens. In this dialog, you can decide whether to replace the existing element or to insert the copy with a different name. Note The "Paste" dialog is not displayed for all elements. The elements for which the dialog is available depends on the installed products.
Or: 1. Open the element view. 2. Use a drag-and-drop operation to move the copy template from the "Elements" pane to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. A copy based on the copy template is inserted. If there is already an element with the same name at this location, the "Paste" dialog opens. In this dialog, you can decide whether to replace the existing element or to insert the copy with a different name. Note The "Paste" dialog is not displayed for all elements. The elements for which the dialog is available depends on the installed products.
Result
A copy is generated from the copy template and inserted at the location where you want to use it. You can create any number of copies from a copy template.
235
See also
Library basics (Page 227) Project library basics (Page 232) Using types (Page 236) Using the elements and parts view (Page 231)
Using types
You use the types you inserted into the project library in order to generate instances of elements and insert them in the TIA Portal, where permissible. The instances are generated and used in a single operation.
Requirement
The "Libraries" task card is displayed.
Procedure
To generate and use an instance from a type, follow these steps: 1. Open the "Types" folder or any of its subfolders in the project library so that you looking at the type from which you want to generate an instance. 2. Use a drag-and-drop operation to move the type from the project library to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. The type is inserted as an instance. If there is already an element with the same name at this location, the "Paste" dialog opens. In this dialog, you can decide whether to replace the existing element or to insert the instance with a different name. Note The "Paste" dialog is not displayed for all elements. The elements for which the dialog is available depends on the installed products. Or: 1. Open the element view. 2. Use a drag-and-drop operation to move the type from the "Elements" pane to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. The type is inserted as an instance. If there is already an element with the same name at this location, the "Paste" dialog opens. In this dialog, you can decide whether to replace the existing element or to insert the instance with a different name. Note The "Paste" dialog is not displayed for all elements. The elements for which the dialog is available depends on the installed products.
236
Result
An instance is generated from the type and inserted at the location where you want to use it. You can create any number of instances from a type. The instances are tied to the type, i.e., changes to one instance are passed on to the other instances.
See also
Library basics (Page 227) Project library basics (Page 232) Using master copies (Page 235)
7.8.4.5
Requirement
The "Libraries" task card is displayed.
Copying elements
To copy a library element, follow these steps: 1. Right-click on the library element you want to copy. 2. Select the "Copy" command in the shortcut menu.
Cutting elements
To cut a library element, follow these steps: 1. Right-click on the library element you want to cut. 2. Select the "Cut" command in the shortcut menu.
237
Note 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 elements
To paste a library element, follow these steps: 1. Copy a library element. 2. Right-click the library where you want to paste the element. 3. Select the "Paste" command in the shortcut menu.
Moving elements
To move a library element, follow these steps: 1. Select the library element you want to move. 2. Use a drag-and-drop operation to move the library element to the folder where you want to insert the element. Note Note the following: When you move an element from one library to another, the element is copied and not moved. You cannot move master copies into a type folder or a type into a master copies folder.
Renaming elements
To rename a library element, follow these steps: 1. Right-click the element you want to rename. 2. Select the "Rename" command in the shortcut menu. 3. Enter the new name.
238
See also
Library basics (Page 227) Project library basics (Page 232) Creating folders in the project library (Page 232) Adding elements to the project library (Page 233) Using elements of the project library (Page 235) Removing elements from the project library (Page 239) Filtering the view (Page 240)
7.8.4.6
Requirements
The "Libraries" task card is displayed.
Procedure
To remove an element from the project library, follow these steps: 1. In the "Project library" pane, maximize the folder containing the element you want to remove. 2. Right-click the element. 3. Select the "Delete" command in the shortcut menu. Or: 1. Open the element view. 2. Right-click the element you want to remove in the "Elements" pane. 3. Select the "Delete" command in the shortcut menu.
See also
Library basics (Page 227) Project library basics (Page 232) Creating folders in the project library (Page 232) Adding elements to the project library (Page 233) Using elements of the project library (Page 235) Editing elements of a project library (Page 237) Filtering the view (Page 240)
239
7.8.4.7
Requirement
The "Libraries" task card is displayed.
Procedure
To filter the view, follow these steps: 1. Open either the "Project library" pane or "Global libraries" pane. 2. In the drop-down list, select the object type for which you want to display the library elements.
Result
Only the library elements that are available for the object type are displayed. You can set the filter to "All" at any time to revert to an unfiltered view.
See also
Library basics (Page 227) Project library basics (Page 232) Creating folders in the project library (Page 232) Adding elements to the project library (Page 233) Using elements of the project library (Page 235) Editing elements of a project library (Page 237) Removing elements from the project library (Page 239)
7.8.5
7.8.5.1 Function
You can store elements that you want to reuse in other projects in global libraries. You must create global libraries explicitly. Depending on the products installed, global libraries supplied by Siemens are also installed. You can use, but not change, the elements of these libraries.
240
See also
Library basics (Page 227)
7.8.5.2
Requirement
The "Libraries" task card is displayed.
Procedure
To create a new global library, follow these steps: 1. Click "Create new global library" in the toolbar of the "Global libraries" pane or select the menu command "Options > Global libraries > Create new library". 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".
Result
The new global library is generated and inserted into the "Global libraries" pane. 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 ".al11".
241
See also
Library basics (Page 227) Global library basics (Page 240) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Using a supplied global library (Page 256) Filtering the view (Page 257)
7.8.5.3
Requirement
The "Libraries" task card is displayed.
Procedure
To open a global library, follow these steps: 1. Click "Open global library" in the toolbar of the "Global libraries" pane or select the menu command "Options > Global libraries > Open library". 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 ".al11".
242
See also
Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Using a supplied global library (Page 256) Filtering the view (Page 257)
7.8.5.4
243
Requirement
The "Libraries" task card is displayed.
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 242) Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Using a supplied global library (Page 256) Filtering the view (Page 257)
7.8.5.5
244
Requirement
The "Libraries" task card is displayed. The global library is not write protected.
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.
See also
Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Using a supplied global library (Page 256) Filtering the view (Page 257)
245
7.8.5.6
Requirement
The "Libraries" task card is displayed.
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. 3. If you make changes to the global library, a dialog box opens where you can choose whether you want to save the changes to the global library. Click "Yes" or "No", depending on whether or not you would like to save your changes. The global library is closed.
See also
Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Library basics (Page 227) Global library basics (Page 240) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Using a supplied global library (Page 256) Filtering the view (Page 257)
7.8.5.7
246
Requirements
The "Libraries" task card is displayed.
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" pane and deleted from the file system.
See also
Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Using a supplied global library (Page 256) Filtering the view (Page 257)
7.8.5.8
Requirements
The "Libraries" task card is displayed. The global library is not write protected.
247
Procedure
To create a new folder, follow these steps: 1. Right-click any folder within the global library. 2. Select "Add folder" from the shortcut menu. A new folder is created. 3. Enter a name for the new folder.
See also
Global library basics (Page 240) Library basics (Page 227) Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Using a supplied global library (Page 256) Filtering the view (Page 257)
7.8.5.9
248
Procedure
To add a new copy template to a global library, follow these steps: 1. In the Global libraries" pane of the "Libraries" task card, open the global library to which you want to add the copy template. 2. Select the element you want to add as a master copy to the global library, and use a dragand-drop operation to move it to the "Master copies" folder or any of its subfolders in the global library. Release the left mouse button when a small plus symbol appears below the mouse pointer.
Result
The element is inserted into the global library as a copy template. You can generate copies from this template and use them anywhere in the TIA Portal where it is permissible.
See also
Library basics (Page 227) Global library basics (Page 240) Adding types to a global library (Page 249)
Requirement
The "Libraries" task card is displayed. A type is available in the project library.
Procedure
To add a type to a global library, follow these steps: 1. Open the project library in the "Project library" pane of the "Libraries" task card. 2. Right-click the type which you want to paste into the global library. 3. In the shortcut menu, select "Copy". 4. Right-click the type which you want to paste into the global library. 5. In the shortcut menu, select "Paste".
Result
The type is inserted in the global library. You can generate instances from this type and use them anywhere in the TIA Portal where it is permissible. The instances are tied to the type, i.e., changes to one instance are passed on to the other instances.
249
See also
Library basics (Page 227) Global library basics (Page 240) Adding master copies to a global library (Page 248)
7.8.5.10
Requirements
The "Libraries" task card is displayed.
Procedure
To generate and use a copy from a copy template, follow these steps: 1. Open the "Master copies" folder or any of its subfolders in the global library so that you looking at the master copy from which you want to generate a copy. 2. Use a drag-and-drop operation to move the copy template from the global library to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. A copy based on the copy template is inserted. If there is already an element with the same name at this location, the "Paste" dialog opens. In this dialog, you can decide whether to replace the existing element or to insert the copy with a different name. Note The "Paste" dialog is not displayed for all elements. The elements for which the dialog is available depends on the installed products. Or:
250
Result
A copy is generated from the copy template and inserted at the location where you want to use it. You can create any number of copies from a copy template.
See also
Library basics (Page 227) Global library basics (Page 240) Using types (Page 251) Using the elements and parts view (Page 231)
Using types
You use the types you inserted into a global library in order to generate instances of elements and insert them in the TIA Portal, where permissible. The instances are generated and used in a single operation.
Requirements
The "Libraries" task card is displayed.
251
Procedure
To generate and use an instance from a type, follow these steps: 1. Open the "Types" folder or any of its subfolders in the global library so that you looking at the type from which you want to generate an instance. 2. Use a drag-and-drop operation to move the type from the global library to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. The type is inserted as an instance. If there is already an element with the same name at this location, the "Paste" dialog opens. In this dialog, you can decide whether to replace the existing element or to insert the instance with a different name. Note The "Paste" dialog is not displayed for all elements. The elements for which the dialog is available depends on the installed products. Or: 1. Open the element view. 2. Use a drag-and-drop operation to move the type from the "Elements" pane to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. The type is inserted as an instance. If there is already an element with the same name at this location, the "Paste" dialog opens. In this dialog, you can decide whether to replace the existing element or to insert the instance with a different name. Note The "Paste" dialog is not displayed for all elements. The elements for which the dialog is available depends on the installed products.
Result
An instance is generated from the type and inserted at the location where you want to use it. You can create any number of instances from a type. The instances are tied to the type, i.e., changes to one instance are passed on to the other instances.
See also
Library basics (Page 227) Global library basics (Page 240) Using master copies (Page 250) Using the elements and parts view (Page 231)
252
7.8.5.11
Requirements
The "Libraries" task card is displayed. The global library is not write protected.
Copying elements
To copy a library element, follow these steps: 1. Right-click on the library element you want to copy. 2. Select the "Copy" command in the shortcut menu.
Cutting elements
To cut a library element, follow these steps: 1. Right-click on the library element you want to cut. 2. Select the "Cut" command in the shortcut menu. Note 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 elements
To paste a library element, follow these steps: 1. Copy a library element. 2. Right-click the library where you want to paste the element. 3. Select the "Paste" command in the shortcut menu.
253
Moving elements
To move a library element within a library, follow these steps: 1. Select the library element you want to move. 2. Drag the library element to the library where you want to insert the element. Note When you move an element from one library to another, the element is copied and not moved.
Renaming elements
To rename a library element, follow these steps: 1. Right-click the element you want to rename. 2. Select the "Rename" command in the shortcut menu. 3. Enter the new name.
See also
Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Removing elements from a global library (Page 255) Using a supplied global library (Page 256) Filtering the view (Page 257)
254
7.8.5.12
Requirements
The "Libraries" task card is displayed. The global library is not write protected.
Procedure
To remove an element from a global library, follow these steps: 1. In the "Global libraries" pane, maximize the folder containing the element you want to remove. 2. Right-click the element. 3. Select the "Delete" command in the shortcut menu. Or: 1. Open the element view. 2. Right-click the element you want to remove in the "Elements" pane. 3. Select the "Delete" command in the shortcut menu.
See also
Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Using a supplied global library (Page 256) Filtering the view (Page 257)
255
7.8.5.13
Requirement
The "Libraries" task card is displayed.
Procedure
To use an element from a supplied global library in your project, follow these steps: 1. Open the relevant library so that you can see the elements of the library. 2. Drag the element from the "Global libraries" pane and drop it on the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash. Or: 1. Open the element view. 2. Use a drag-and-drop operation to move the element from the "Parts" pane to the location where you want to use it. If you are not permitted to insert it at this location, the mouse pointer changes to a circle with a slash.
See also
Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Filtering the view (Page 257)
256
7.8.5.14
Requirement
The "Libraries" task card is displayed.
Procedure
To filter the view, follow these steps: 1. Open either the "Project library" pane or "Global libraries" pane. 2. In the drop-down list, select the object type for which you want to display the library elements.
Result
Only the library elements that are available for the object type are displayed. You can set the filter to "All" at any time to revert to an unfiltered view.
See also
Library basics (Page 227) Global library basics (Page 240) Creating a new global library (Page 241) Opening a global library (Page 242) Displaying properties of global libraries (Page 243) Saving a global library (Page 244) Closing a global library (Page 246) Deleting a global library (Page 246) Creating folders in the global libraries (Page 247) Adding elements to a global library (Page 248) Using elements of a global library (Page 250) Editing elements of a global library (Page 253) Removing elements from a global library (Page 255) Using a supplied global library (Page 256)
257
7.9
7.9.1
Using cross-references
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.
7.10
7.10.1
Simulating devices
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.
See also
Starting the simulation (Page 259)
258
7.10.2
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 258)
259
261
Device view (Page 265), network view (Page 263), topology view (Page 268) Inspector window (Page 272) Hardware catalog (Page 274)
The hardware and network editor provides you with three views of your project. You can switch between these three views at any time depending on whether you want to produce and edit individual devices and modules, entire networks and device configurations or the topological structure of your project. The inspector window contains information on the object currently marked. Here you can change the settings for the object marked. Drag the devices and modules you need for your automation system from the hardware catalog to the network, device ot topology view.
262
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 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.
263
Toolbar
The toolbar provides the following functions:
Symbol Meaning Mode to network devices. Mode to create connections. You can define the connection type using the 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 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 page break preview. Dotted 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.
264
See also
Adding a device to the hardware configuration (Page 289) Layout of the user interface (Page 133) Determination of online status and display using symbols (Page 586) Networking devices in the network view (Page 302) Tabular network overview (Page 305)
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
265
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 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:
Symbol 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.
266
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 282) Network view (Page 263) Area for unplugged modules (Page 286) Inserting a module into a rack (Page 291) Objects in the device view (Page 284) Layout of the user interface (Page 133) Determination of online status and display using symbols (Page 586)
267
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 Identify and minimize 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 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.
268
Toolbar
The toolbar provides the following functions:
Symbol Meaning Adjusting the zoom setting. You can select the zoom setting via the 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 page break preview. Dotted 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. See: Adding a device to the hardware configuration (Page 289)
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.
See also
Layout of the user interface (Page 133) Determination of online status and display using symbols (Page 586)
269
8.1.1.5
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
270
See also
Changing the print options (Page 272) Documentation settings (Page 196) Creating a print preview (Page 210) Printing project data (Page 213) Activating the page break preview for printout (Page 271)
8.1.1.6
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.
271
8.1.1.7
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.
See also
Printing hardware and network configurations (Page 270)
8.1.1.8
Inspector window
The properties and parameters shown for the object selected can be edited in the inspector window.
272
Structure
The inspector window consists of the following components:
Switch between various 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 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.
See also
Editing properties and parameters (Page 297) Overview of hardware and network editor (Page 261)
273
8.1.1.9
Hardware catalog
The "Hardware catalog" task card gives you easy access to a wide range of hardware components.
Structure
The "Hardware catalog" task card consists of the following panes:
"Catalog" pane, search and filter function "Catalog" pane, component selection "Information" pane
274
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 Version number Order number Brief description
See also
Browsing the hardware catalog (Page 281) Overview of hardware and network editor (Page 261) Information on hardware components (Page 275)
8.1.1.10
275
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.
See also
Hardware catalog (Page 274) Enabling product support (Page 276)
8.1.1.11
276
Requirement
The software must have access to the Internet.
Procedure
To enable the Service & Support function, proceed as follows: 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.
Result
You can now access product support, FAQs and manuals from the hardware catalog via the shortcut menu for the module.
See also
Information on hardware components (Page 275)
8.1.1.12
Selected objects
Function Select object Move object Copy object Paste object Key combination Mouse click <Ctrl+X>, then <Ctrl+V> <Ctrl+C> <Ctrl+V> Comments Copy selected object to move and then paste in new position Copy selected object to clipboard Paste object from clipboard to selection
277
8.1.2
8.1.2.1
Configuring devices
Basics
Configuring
"Configuring" is understood to mean arranging, setting 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 setpoint configuration produced by the software with the system's actual configuration. Possible errors can be detected and reported straight away.
Assigning parameters
"Assigning parameters" is understood to mean setting the properties of the components used. Hardware components and settings for the exchange of data are assigned: Properties of modules with selectable parameters Settings for data exchange between components The parameters are loaded into the CPU and transferred to the corresponding modules when the CPU starts up. Modules can be replaced with ease since the parameters set are automatically loaded into the new module during startup.
278
See also
Changing properties of the modules (Page 516)
279
See also
Opening projects (Page 176)
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.
280
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
281
See also
Hardware catalog (Page 274) Information on hardware components (Page 275)
282
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 265).
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:
283
Groups of slots into which modules have already been plugged cannot be collapsed.
284
In the upper part, you can see the graphic view showing how the rack is occupied by various modules in slots 1 to 3 as well as 101. In the lower part you can see a tabular representation of the rack in the device overview. Each line in the device overview represents one slot. The key information for each slot is displayed in the various columns:
Column Module Slot I address Q address Type Order no. Firmware Comments Meaning Name of module, can be edited in any way Slot number Input address area, can be edited in any way Output address area, can be edited in any way Catalog name of module Module order number Firmware version of module Optional comments
See also
Device view (Page 265)
285
You open the area of unplugged modules with the respective symbol in the toolbar of the device view (Page 265).
Symbol 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 that have already been parameterized out of the configuration without deleting them.
286
8.1.2.2
Requirement
The hardware catalog is open. You must be in the network view.
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.
287
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 281) Adding a device to the hardware configuration (Page 289) Inserting a module into a rack (Page 291) Working with racks (Page 282) Creating an unspecified CPU (Page 290) Information on hardware components (Page 275)
288
289
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 263) Creating an unspecified CPU (Page 290) Information on hardware components (Page 275) Topology view (Page 268)
290
See also
Selecting a CPU (Page 287) Adding a device to the hardware configuration (Page 289)
291
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.
292
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 265) Area for unplugged modules (Page 286) Information on hardware components (Page 275) General slot rules (Page 280)
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.
293
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, for example infringement of slot rules. Inconsistencies are reported during the consistency check. Correct the inconsistencies by taking appropriate action, for example, make sure that slot rules are kept to.
See also
Keyboard action in the hardware and network editor (Page 277)
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. 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.
294
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 286). Note You can use <Ctrl> and drag-and-drop to directly copy a selected hardware component.
See also
Keyboard action in the hardware and network editor (Page 277)
295
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. 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.
296
See also
Keyboard action in the hardware and network editor (Page 277)
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.
297
Requirements
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.
298
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 272)
299
Requirements
You have created a device configuration. You have installed an update or an optional package at a later date. As a result of this installation, the module version of at least one module type was updated in the hardware catalog, whereby the new version is incompatible with the previous version. You have used such modules in your device configuration and want to use the modified or added properties.
Procedure
Perform the following step for each affected module type. 1. Select the affected module in the device view. 2. In the Inspector window, go to "Properties > General > Catalog Information". Click the "Update module version" button there. 3. In the query that then appears, specify whether you want to update the module version only for the selected module or for all modules of this type in the current project.
Result
The selected modules are replaced by the same modules with updated module version in the the current project.
300
8.1.3
8.1.3.1
Configure networks
Networking devices
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.
301
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.
302
303
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.
304
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.
305
306
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.
307
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 302)
308
309
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.
See also
What you need to know about PROFIBUS bus parameters (Page 311)
310
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.
311
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 310) Description of the bus parameters (Page 312)
Max. Tsdr Min. Tsdr Tset Tqui GAP factor Retry limit Tslot
312
Ttr typical
Response monitoring
See also
What you need to know about PROFIBUS bus parameters (Page 311)
313
Meaning of profiles
Profile DP Meaning 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. 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.
Universal (DP/FMS)
Note Both mono-master mode and multi-master mode are possible with all PROFIBUS profiles.
314
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
315
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.
316
IP address
The IP parameters are visible if the module capable of communication supports the TCP/IP protocol. This is usually the case for all Ethernet modules. The IP address consists of 4 decimal figures in the range of 0 to 255. The decimal figures are separated from one another by a dot. Example: 140.80.0.2 The IP address consists of: Address of the (sub) net Address of the node (generally also called host or network node)
Subnet mask
The subnet mask splits these two addresses. It determines which part of the IP address addresses the network and which part of the IP address addresses the node. The set bits of the subnet mask determine the network part of the IP address. Example: Subnet mask: 255.255.0.0 = 11111111.11111111.00000000.00000000 In the example given for the above IP address, the subnet mask shown here has the following meaning: The first 2 bytes of the IP address identify the subnet - i.e. 140.80. The last two bytes address the node, thus 0.2. It is generally true that: The network address results from AND linking the IP address and subnet mask. The device address results from AND NOT linking the IP address and subnet mask.
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.
317
Result: All nodes with addresses between 129.80.001.xxx and 129.80.127.xxx are on one subnet, all nodes with addresses between 129.80.128.xxx and 129.80.255.xxx are on another subnet.
Router
The task of the routers is to connect the subnets. If an IP datagram is to be sent to another network, it first has to be conveyed to a router. To make this possible, you have to enter the address of the router for each node in the subnet. The IP address of a node in the subnet and the address of the router may only differ at the points at which there is a "0" in the subnet mask.
318
8.1.3.2
319
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"
320
321
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.
322
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:
323
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.
324
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.
325
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.
326
Deleting connections
You can delete configured connections via the network view or the connection table. In the network view you can delete a highlighted connection. In the connection table you can delete one or more connections.
Procedure
To delete a connection, proceed as follows: 1. Select the connection to be deleted: In the network view: Select the connection to be deleted. In the connection table: Select the rows of the connections to be deleted (multiple selection possible). 2. Open the shortcut menu with a right mouse click. 3. Select the "Delete" command. The selected connection will be completely deleted.
327
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.
Remedies
To assign a closed connection path to an existing open connection path, expand the device configuration in such a way that the interfaces required for the connection type are available for both partners. At "Properties > General > Interface" in the Inspector window, you can use the "Find connection path" button to create a connection to an existing partner.
328
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.
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.
329
330
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).
331
332
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.
333
Specifying a connection
If both partners for the connection type selected are networked on the same network, use the graphic or interactive selection of both communication partners to create a fully specified connection. This connection is entered automatically 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:
334
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.
335
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.
336
See also
Creating a new connection graphically (Page 334)
337
Deleting connections
You can delete configured connections via the network view or the connection table. In the network view you can delete a highlighted connection. In the connection table you can delete one or more connections.
Procedure
To delete a connection, proceed as follows: 1. Select the connection to be deleted: In the network view: Select the connection to be deleted. In the connection table: Select the rows of the connections to be deleted (multiple selection possible). 2. Open the shortcut menu with a right mouse click. 3. Select the "Delete" command. The selected connection will be completely deleted.
Copying a project
When you copy a project all configured connections will also be copied. No settings whatsoever are required for the copied connections because the connections remain consistent.
Copying devices
If you copy devices for which connections have been configured (HMI devices), the connections are copied as well. To complete the connection path, you must still finalize the networking.
338
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.
339
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.
340
Connection establishment
For Open User Communication, instructions for establishing and terminating the connection must exist for both communications partners. One communications partner sends its data using TSEND, TUSEND or TSEND_C while the other communications partner receives the data using TRCV, TURCV or TRCV_C. One of the communications partners starts the connection establishment as the active partner. The other communications partner reacts by starting its connection establishment as the passive partner. If both communication partners have initiated their connection establishment, the communication connection is fully established.
341
See also
Principle of operation of connection-oriented protocols (Page 351)
342
343
344
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 parameter assignment. 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. NOTICE The connection configuration does not check whether the connection IDs and port numbers (TCP, UDP) or TSAPs (ISO-on-TCP) are unique. When you configure Open User Communication, you should, therefore, make sure that the parameter settings are unique within a device.
See also
Parameters of communication connections (Page 353)
345
346
See also
Parameters of communication connections (Page 353) Assignment of port numbers (Page 355) TSAP structure (Page 357) Examples of TSAP assignment (Page 359) Ability to read back connection description parameters (Page 356) Creating and assigning parameters to connections (Page 348)
Requirements
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. 4. Click "OK" to complete your entry.
Result
A corresponding instance DB is created for the inserted instruction TSEND_C, TRCV_C or TCON.
347
See also
Creating and assigning parameters to connections (Page 348)
Requirement
A CPU exists with a TCON, TSEND_C or TRCV_C communication instruction.
Procedure
To create a connection for Open User Communication, proceed as follows: 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 communications partner. Certain connection parameters are then entered automatically. The following parameters are set: Interface 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.
348
349
See also
Description of the connection parameters (Page 345) Starting connection parameter assignment (Page 347) TSAP structure (Page 357) Assignment of port numbers (Page 355) Parameters of communication connections (Page 353)
Requirement
You have created an Open User Communication connection.
Procedure
To delete a connection, proceed as follows: 1. Select a communications partner for Open User Communication in the project tree. 2. Open the "Program blocks" folder below the selected communications partner. 3. Select the "Delete" command from the shortcut menu of the data block with the connection parameter assignment.
350
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 used by other blocks of the extended instructions, then the corresponding calls, their instance DBs and the combination blocks TSEND_C and TRCV_C are also deleted from the block folder, provided they are not used elsewhere. This action prevents the program from being inconsistent.
Result
You have deleted the connection. Note Insert an extended instruction TCON, TSEND_C or TRCV_C again to reference an existing connection description with the TCON_Param structure via the "Connection data" parameter.
351
Characteristics of TCP
During data transmission via a TCP connection, no information about the length or about the start and end of a message is transmitted. This does not pose a problem during sending because the sender knows the amount of data to be transmitted. However, the receiver has no means of recognizing 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 will occur: 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.
Characteristics of ISO-on-TCP
During data transmission via an ISO-on-TCP connection, information regarding the length and the end of a message is also supplied. If the length of the sent data and the length of the expected data do not match, the following will occur: 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).
Characteristics of UDP
Information on the length and the end of a message is also supplied 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 will occur:
352
See also
Basics of Open User Communication (Page 340)
0 1 block_length 2 3 id
353
rem_staddr
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
354
spare
W#16#0000
Reserved.
See also
Principle of operation of connection-oriented protocols (Page 351) Description of the connection parameters (Page 345) Ability to read back connection description parameters (Page 356) Overview of connection parameter assignment (Page 342) TSAP structure (Page 357) Assignment of port numbers (Page 355)
355
* These ports are used by TSEND_C and TRCV_C with the TCP and UDP connection types. ** These ports are blocked depending on the function scope of the utilized S7-1200 CPU. The documentation of the respective CPUs provides the assignment of these ports.
See also
Description of the connection parameters (Page 345) Creating and assigning parameters to connections (Page 348)
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 parameter assignment in the connection description DB. You can change the parameter values of the connection description DB outside of the connection parameter assignment in the user program. The structure of the connection description cannot be changed. Connection description DBs containing values you changed subsequently can be read back from the connection parameter assignment. Under "Properties > Configuration > Connection parameters", the Inspector window displays only the connection parameters stored in the connection description DB. The connection parameter assignment does not support nested entries of connection descriptions in DB types that can only be found via offset referencing (for example, Global-DB).
356
See also
Parameters of communication connections (Page 353) Description of the connection parameters (Page 345)
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):
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.
357
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.
*A recognized CPU is normally inserted on rack 0 in slot 1. For this reason, hex value 01 is valid for the second place of the TSAP-ID with extension. If the connection partner is an
358
See also
Examples of TSAP assignment (Page 359) Description of the connection parameters (Page 345) Creating and assigning parameters to connections (Page 348)
359
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.
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.
360
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).
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.
See also
TSAP structure (Page 357) Description of the connection parameters (Page 345)
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.
361
Requirement
To be able to use the PUT and GET instructions, the following requirements must be satisfied: At least one S7-300/400/1200 CPU must be created in the project. Firmware 2.0 or higher must be installed on the 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 parameter assignment (Page 362) Assigning parameters to start request (Page 367) PUT: Set parameters for write and send area (Page 368) GET: Set parameters for read and memory area (Page 369)
362
"Configuration" tab
Communication instruction for PUT or GET "Configuration" tab in the "Properties" tab Area navigation of the "Configuration" tab General properties of 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 parameter assignment. 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.
363
See also
Assigning parameters to start request (Page 367) PUT: Set parameters for write and send area (Page 368) GET: Set parameters for read and memory area (Page 369)
Connection name
364
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/400 CPUs, a function block is created additionally 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 365) Deleting connections (Page 366)
365
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.
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.
WinCC Basic V11.0 SP2 System Manual, 04/2012,
366
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.
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. 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.
367
See also
PUT: Set parameters for write and send area (Page 368) GET: Set parameters for read and memory area (Page 369)
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).
See also
GET: Set parameters for read and memory area (Page 369)
368
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 368)
369
8.1.3.3
370
Which functions are there in the graphic view and which functions are there in the table view?
Displaying the Ethernet topology
Function Displaying all the PROFINET devices and passive Ethernet components of the project along with their ports Display interconnections between the ports (including type of medium) Displaying corresponding logical networks Displaying properties of the cables between the ports Display diagnostic information of all ports Graphic view yes yes no no yes Table view yes yes yes yes yes
Identifying and minimizing differences between the desired and actual topology
Function Running an offline/online comparison of Ethernet modules, ports and port interconnections Adopting existing online topology information in the offline project Graphic view no no Table view yes yes
Procedure
To start the topology view of your project, follow these steps: 1. Click on the "Topology view" tab. Or:
371
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
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.
372
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 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
373
Displaying the diagnostics status of ports and cables in the graphic view Requirements
The graphic view of the topology view is open.
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: Determination of online status and display using symbols (Page 586)
374
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. For the possible diagnostics icons for hardware components, refer to the description of hardware diagnostics. See: Determination of online status and display using symbols (Page 586) Note The display of the diagnostics status of hardware components in the topology overview table and the network overview table is identical.
375
Procedure
To find the differences between the configured and the actual topology, follow these steps: 1. Click the "Compare offline/online" 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 Update Synchronize Meaning The detection of the existing online topology is started again. Adopt the port interconnections identified online in the project (Page 383) Adopt the devices identified online in the project (Page 384)
After the actual topology has been identified, the added columns are filled. This is discussed 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.
376
"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
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 378) in the graphic view of a tool changer (Page 379) in the table view (Page 379)
377
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 when a port interconnection is created between two devices that are not networked, this subnet is used. 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.
378
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: Create new port interconnection Modify existing port interconnection Delete 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 on the drop-down list there. 3. Select the required partner port (when creating a new interconnection or changing the 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) is displayed in the "Partner port" column otherwise the "Select port" entry (after deleting a port interconnection).
Interconnecting a port with more than one partner port in the graphic view Requirement
You have assigned parameters to a port of a PROFINET device with the "Alternative partners" property and have specified the possible partner ports. The graphic view of the topology view is open.
379
Procedure
1. Interconnect this port (called source port below) with one of the partner ports you have specified (called target port below). 2. Interconnect the source port with an additional target port. You can do this in several ways: Drag the mouse pointer from an already interconnected partner port 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 an already interconnected partner port. 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 multiple 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: Create new port interconnection Modify existing port interconnection Delete existing port interconnection
Requirement
You have assigned parameters to a port of a PROFINET device with the "Alternative partners" property and have specified the possible partner ports. 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 to one or more partner ports 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 on the drop-down list there. 3. Select the required partner port (when creating a new interconnection or changing the port interconnection) or the "Not interconnected" entry (when deleting a port interconnection).
380
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 make a change, the new partner port is displayed in the "Partner port" column. If you are deleting, 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 several partner ports. 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.
381
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: 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 383) No action
382
The interconnection only exists in the configuration. The following actions are possible:
"Action" column Meaning Adopt the online interconnection (Page 383), in other words, the interconnection in the configuration will be deleted No action
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 384).
383
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.
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.
384
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.4
8.1.4.1
Creating configurations
Configurations for automation systems
I/O address
I/O addresses are required to read inputs and/or set outputs in the user program. Input and output addresses are assigned automatically when inserting modules 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 derived from the modulespecific address length.
385
The hardware ID is assigned automatically when components are inserted in the device or network view and in the constants table of the PLC tags. A name is also assigned automatically for the hardware ID. These entries in the constants table of the PLC tags cannot be changed either.
See also
Specifying input and output addresses (Page 386) Assigning addresses to a location in the program (Page 387) Introduction to loading a configuration (Page 470)
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. 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.
386
See also
Editing properties and parameters (Page 297)
Requirement
The device view of the hardware and network editor as well as the instruction window of the program editor must be opened and arranged one below the other.
Procedure
Proceed as follows to assign addresses of modules and locations in the program: 1. In the device view, navigate to the module with the desired I/O channel. 2. Use the zoom function to specify a magnification of at least 200%: At a magnification level of 200% and higher, the labels of the individual address channels are displayed and can be edited.
387
The module address or tag will be assigned to the location in the program, or the address or tag in the program will be assigned to a module I/O channel.
388
Requirement
The hardware catalog is open. The S7-1200 CPU has a free slot for the signal board.
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.
389
Configurations for Web server What you need to know about web servers 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. Messages and status information are visualized on HTML pages.
Web browser
You need a web browser that supports HTML 1.1 to access the HTML pages of the CPU. The following web browsers, for example, are suitable for communication with the CPU: Internet Explorer (version 6.0 and higher) Mozilla Firefox (V1.5 and higher) Opera (version 9.0 and higher) Netscape Navigator (version 8.1 and higher)
390
User Pages User pages (if custom web pages have been configured and loaded)
Requirements
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. To execute certain actions, such as changing the operating state of the CPU or for write access, the user must be logged on as "admin". The logon input boxes are on the top left of each standard web page.
391
If you log on as "admin", you must enter the user name and password there. Name: admin. Password: configured CPU password (for password-protected CPU).
See also
Access for HTTPS (Page 392)
392
393
Creating and loading custom web pages What you need to know about custom web pages Concept
The concept of custom 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 custom 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".
Initialization
Custom 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 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. Data blocks that contain coded web pages are termed "Fragment DBs".
394
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 Assemble and send back data to the web browser making the 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.
395
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).
396
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, :. A small example for a custom web page should make clear the basic design.
Requirements
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".
397
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
398
See also
Reading tags (Page 399) Writing tags (Page 401) Special tags (Page 402)
Reading tags
Custom 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 CPU tag but also a complete tag path to a structure element.
399
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 "abc:de" "abc\de" PLC tag in HTML code :="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 398)
400
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\"" -->
401
See also
Requirements for web access (Page 391) AWP commands (Page 398)
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.
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:
402
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:
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:
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.
403
Examples:
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 .
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 .
See also
AWP commands (Page 398)
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:
For example, for English values, to be saved as an HTML file in the "en" folder of the HTML directory:
404
Assigning enums
Tags are assigned from the user program to the individual enum texts using a special AWP command:
<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.
Example
Enum type "state" is defined with values "0" and "1". "0" means "off", "1" means "on":
The following code is contained in the HTML code of the web page to be output:
Depending on the value of the "operating state" tag, the result displayed is no longer "0" or "1", but "off" or "on".
405
Defining fragments
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. 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.
Syntax
406
Example
HTML code within a web page that declares a fragment:
Example
HTML code within another web page that imports the declared fragment:
Procedure
To create data blocks from the source files for custom web pages in STEP 7, proceed as follows: 1. Select the CPU, for example, in the device configuration. 2. Select the properties for custom 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.
407
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.
408
409
"WEB-Control_DB".requesttab[x].repeat
"WEB-Control_DB".requesttab[x].abort "WEB-Control_DB".requesttab[x].finish
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.
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>
410
411
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:
412
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).
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.
413
Requirements
The language-dependent HTML; pages must be stored in a folder structure containing folders with the respective language abbreviations:
414
415
416
See also
Overview of point-to-point communication (Page 529) General information on high-speed counters (Page 524)
8.1.4.2
417
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.
418
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 polls each of the configured DP slaves in its polling list within the DP master system in succession, sending the output data to the slaves and receiving the input data back from the slaves.
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.
419
Requirements
DP master and DP slaves are placed in the network view.
420
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.
421
DP master
You can use any of the following devices as a DP master: CM 12435
Requirements
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.
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:
422
There are various ways of removing the highlighting from a DP master system:
423
Requirements
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.
424
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)
425
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.
Requirements
You must be in the network view. A DP master system must have been created.
426
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.
427
Applications
Configurations involving intelligent DP slaves: I slave <> DP master data exchange Direct DP slave > I slave data exchange
Procedure
To add an I slave to a DP master system, follow these steps: 1. Drag two devices with PROFIBUS DP interface for configuration as DP master and I slave from the hardware catalog to the network view. 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.
428
Configuring the transfer area for data with DP slaves of the S7-1200
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".
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.
429
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
430
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.
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.
431
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.
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.
432
Requirements
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
433
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 reserve 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 reserve 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.
Additional information
For additional information on the assignment and significance of bytes within the process image, option handling with PROFIBUS and the use of reserve modules, please refer to the documentation for the ET 200S distributed I/O system.
434
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.
435
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 Operation when target configuration does not match actual configuration Diagnostics interrupt (OB 82) Insert/remove interrupt (OB 83) DPV0 mode Fully available DPV1 mode Fully available
Fully available Fully available Only available when addresses are not packed. "Startup when target configuration does not match actual configuration" is activated automatically along with an insert/remove interrupt.
436
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
437
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.
Requirements
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.
438
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.3
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.
439
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.
440
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. Proxy functionality allows a PROFIBUS device that can communicate with all devices on the PROFINET and not just with its master. Using PROFINET, 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 to establish communication via PROFINET.
441
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.
442
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".
Segment 1 Segment 2
443
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.
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. 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. 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.
444
device-1.machine-1.plant-1.vendor If you assign this name, to a CPU for example, STEP 7 will not convert it.
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.
See also
Assigning the device name and IP address (Page 445) Retentivity of IP address parameters and device names (Page 452)
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 the configuration of PROFINET interface, you have to set the following: IP address is set in the project. IP address is set using a different method.
445
Option: Set IP address in the project: Assign online via MPI/PROFIBUS interface
Option "Use different method to obtain IP address" Assign online Assign via user program Higher-level IO controller (only with I devices)
Assigning device names for IO devices when the "Device replacement without removable media/PG" option is enabled
For IO devices where the "Device replacement without removable media/PG" option is activated, it is not necessary to assign the device name in the case of a device replacement.
446
Assigning a device name and address for an IO device (exception in the case device exchange without media change/PG)
The following graphic illustrates the process for assigning the device name and address.
Each device receives a name; STEP 7 automatically assigns an IP address. STEP 7 generates a PROFINET device name from the name. This is then assigned to an IP device online (MAC address) and is written into the device. The configuration is downloaded to the IO controller. The IO controller assigns the appropriate IP address to the IO device with the assigned PROFINET device name during startup.
A device name is assigned to each IO device. You can change the name and IP address manually. You have two options for downloading configured data to the PROFINET IO device:
447
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 for the respective PROFINET device. 3. Select the "Use different method to obtain IP address" option or "Different method for obtaining device name" option.
Rules
If the "Different method for obtaining IP address / device name" option is used in 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 router.
448
See also
Calling the name assignment function from the project tree or via the "Online" menu (Page 611)
Requirements
You must be in the network view. A CPU 1214C (V2.0 or higher) must be available in the network view. An IM 151-3PN is available. The PROFINET interfaces of both modules are networked.
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 IM. Make sure that you have selected only the IM and not the complete device ET200S! 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.
449
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.
450
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.
451
Recommendation
If possible, use the "Set IP address in project" and specify an appropriate IP address. In this case, the IP address is assigned retentively.
452
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.
453
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.
454
Requirements
IO controller and IO devices are placed in the network view.
455
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.
Interconnecting ports
If an IO device is assigned to an IO controller, this does not yet specify that the ports are connected to each other. Although a port interconnection is not required to use the PROFINET functions, it does however offer the following advantages: A setpoint topology is assigned with the port interconnection. Based on an online-offline comparison, it is possible to conduct a setpoint-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.
456
Setting the send clock Shortest possible update interval for send clock
The send clock indicates the time between two consecutive communication cycles. It is the shortest possible transmission interval in data exchange. The update times are calculated as multiples of the send clock cycle.
Procedure
To set the send clock, proceed as follows: 1. Select the PROFINET IO controller in the device or network view. 2. Change the value for "Shortest possible update interval for send clock" in the properties of the PROFINET interface under "PROFINET Interface > Advanced options > Realtime settings > IO communication". 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.
457
458
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: There is a greater number of IO devices There is a greater number of IO modules The update times are shorter.
459
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.
"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.
460
461
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.
462
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.
Enabling device replacement without exchangeable medium Replacing an IO device without exchangeable medium
Replacement of IO devices is frequently required in automation systems. The IO devices are generally assigned a device name by either inserting an exchangeable medium or via the programming device. The CPU identifies the IO device by using these device names. Replacing an IO device can be done without inserting an exchangeable medium (e.g. memory card) or without the programming device, under certain circumstances. For this purpose the Ethernet mechanism analyzes the relationship between the individual IO devices and the IO controller. From these relationships which are stored in the IO controller, the IO controller recognizes which IO device was replaced and assigns a device name to the new device.
Requirements
A port interconnection is already configured. The affected IO devices in the automation system must support device replacement without exchangeable medium. If the individual IO devices in the automation system do not support device replacement without exchangeable medium, a corresponding message is output for the IO device. Note Use only new IO devices as replacements or restore configured IO devices to their delivery state.
Procedure
In order to enable the replacement of an IO device without exchangeable medium, proceed as follows: 1. In the device, select the device or network view of the PROFINET interface in the corresponding IO controller. 2. In the interface properties under "Advanced settings > Interface options", select the "Allow device replacement without exchangeable medium"
463
See also
Components with the the device replacement without exchangeable medium function (http:// support.automation.siemens.com/WW/view/en/36752540)
Using GSDML 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 scheme. The language used to describe the GSD files is GSDML (Generic Station Description Markup Language). It is determined by the GSDML scheme. The following sections therefore refer to GSDML files. A GSDML scheme contains validation rules that allow it, for example, to check the syntax of a GSDML file. GSDML schemes (as scheme 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 scheme. A new version of the specification and of the scheme is created by the functional enhancement.
464
Requirements
The hardware and network editor is closed. You have access to the required GSDML files in a directory on the hard disk.
Procedure
To install a GSDML file, follow these steps: 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 GSDML files. 3. Choose one or more files from the list of displayed GSD- and GSDML 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 the GSDML files in a new folder in the hardware catalog. Note You cannot undo the installation of an GSDML file.
465
Changing the version of a GSDML 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.
Requirements
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.
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.
466
8.1.4.4
Figure 8-1
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).
467
8.1.4.5
Requirements
The call interface of the tool complies with the TCI specification. Parameters and commands are forwarded to the distributed device via this call interface.
468
See also
Example of a device tool (Page 469)
Requirements
You have configured the corresponding DP slave or the corresponding IO device.
Starting S7-PCT
For a ET 200S with 4SI IO-Link, for example, follow these steps: 1. Select the module in the device view. 2. Select "Edit > Start device tool" from the shortcut menu. The tool starts and you can configure the ports. Alternatively, you can also start from the device view (see next section). For a ET 200eco PN with 4IOL+8DI+4DO, follow these steps: 1. Select the module in the device view. 2. Arrange the areas in the work area in such a way that the device overview is visible (is located between device view and Inspector window). 3. Select the row with the IO link in the device overview. 4. Select "Edit > Start device tool" from the shortcut menu.
469
See also
Integrating S7-external tools (Page 468)
8.1.4.6
Loading a configuration
See also
Uploading project data from a device (Page 192) General information on loading (Page 189) Downloading a configuration to a device (Page 470) Downloading project data to a device (Page 190) Downloading a configuration to the PG/PC (Page 471) Special features during startup (Page 501)
470
WARNING Load only in STOP mode After loading, you may experience unexpected behaviors on the machine or in the process if the parameter settings are incorrect. The CPU must be set to STOP mode for the download operation to rule out possible damage to equipment or personal injury.
See also
General information on loading (Page 189) Downloading project data to a device (Page 190)
Requirements
The original hardware configuration must be created in TIA-Portal V11. The opened project is in offline mode.
Scope of download
The following list presents an exact overview of the parts of the configuration that are transferred: Device parameters All set parameters of the module are transferred. PROFIBUS master systems and all PROFIBUS-relevant settings A DP master system and all connected slaves are inserted into the project. The respective settings remain unchanged. If a suitable PROFIBUS subnet has already been created, the downloaded modules are connected to the PROFIBUS interface at the existing subnet.
471
See also
Uploading project data from a device (Page 192) General information on loading (Page 189)
8.1.5
8.1.5.1
Introduction
When a system error occurs, hardware components and devices of other manufacturers (slaves whose properties are set by the GSD files) can trigger organization block calls. Example: If a wire breaks, a module with diagnostics capability can call OB 82.
472
8.1.5.2
Recommended procedure
Make the settings for reporting system errors and the structure of the alarms. Specify which diagnostics blocks will be created. Configure the OBs, Status DBs, as well as the PLC in STOP. Generate the blocks and download the configuration to apply the changes. You will find detailed information in the sections below. Note If you use system diagnostics, the system response of the plant may change if an error occurs. For example, the CPU may not change to "STOP" mode as it would without system diagnostics. Make sure that all protective mechanisms of the plant are working properly.
473
8.1.5.3
Components supported
The following components are supported: S7-300 CPUs S7-400 CPUs S7-400 power supply modules PN/PN Coupler DP/DP Coupler IE/PB-Link AS-i CP ET 200S ET 200M ET 200eco ET 200R ET 200Pro ET 200L Diagnostics repeater GSD-based slaves GSDML-based slaves ET 200iSP IO-Link Software CPUs
8.1.5.4
474
See also
Properties of the blocks (Page 475)
8.1.5.5
Diagnostics blocks
The created diagnostics blocks (FB with assigned instance DB and one or more global DBs and an FC) evaluate the local data of the error OB and read any additional diagnostics information from the hardware component that triggered the error. They have the following properties: Created in RSE language (report system errors) (also applies to the blocks listed above) Know-how protected (also applies to the blocks listed above) Delay incoming interrupts during runtime
Status DBs
The status DBs act as the interface for the diagnostics blocks and allow diagnostics events to be displayed graphically on an HMI device or a Web server.
See also
Settings for system diagnostics blocks (Page 487)
8.1.5.6
475
476
See also
Settings for OB configuration (Page 488)
8.1.5.7
8.1.5.8
Diagnostics status DB
477
Name Directory D_Version D_pGlobalState D_pQuery D_pComponent D_pError D_pState D_pAlarm D_pSubComponent GlobalState G_EventCount G_StartReporting Query Q_ClientID_User
Data type WORD WORD WORD WORD WORD WORD WORD WORD
Description Version supported by system diagnostics Byte offset to the start of the "GlobalState" section Byte offset to the start of the "Query" section Byte offset to the start of the "Component" section Byte offset to the start of the "Error" section Byte offset to the start of the "State" section Byte offset to the start of the "Alarm" section Byte offset to the start of the "Subcomponent" section ID of the last event (counter) Startup evaluation active ID of the client; here, please use a value between 1 and 255. Make sure that different clients use different IDs. ID of the client (internal) With/without status of the lower-level components (slower) AS-i master returns AS-i slave interrupts Reserved Reserved Reserved Reserved Reserved Reserved Start query
Q_ClientID_Intern Q_WithSubComponent Q_SubComponentAlarm Q_Reserved2 Q_Reserved3 Q_Reserved4 Q_Reserved5 Q_Reserved6 Q_Reserved7 Q_Start
DWORD BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL
478
2.1
E_Reserved
+40 0 1 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 4 8 12 16
State S_Hierarchy S_Periphery S_SupFault S_NotAvailable S_Faulty S_MoreErrors S_Maintenance1 S_Maintenance2 S_Deactivated S_Reserved2 S_SubFault S_SubMaintenance1 S_SubMaintenance2 S_SubDeactivated S_Reserved4 S_Reserved5 S_Reserved6 S_Reserved7 S_TIAMS S_TIAMSChannelExist S_TIAMSChannelOK S_ChannelCount BYTE BYTE BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL BOOL DWORD DWORD DWORD WORD Reserved Reserved The component cannot be reached The component does not exist The component is faulty, the "Alarm" section is not empty There are more errors than system diagnostics can store A maintenance request is pending A maintenance demand is pending The component was deactivated *) Reserved A subcomponent is faulty A maintenance request is pending for a subcomponent A maintenance demand is pending for a subcomponent A subcomponent is deactivated Reserved Reserved Reserved Reserved Maintenance state of the component Maintenance state: Configured channels Maintenance state: Faulty channels Number of channels; valid only when Q_WithSubComponent is set
479
*) If the component was deactivated, the index of the requested/actual error is not changed and "E_LastError" is set to "true". The tag area of the alarm is also not filled in. **) The list of subcomponents is valid only when Q_WithSubComponent is set. The ARRAY has a status byte for each configured component. For a master, the ARRAY contains the status of the configured stations sorted in ascending order according to the station ID. For a station, the ARRAY contains the status of the configured slots sorted in ascending order according to slot number. This field can contain a maximum of 4096 entries (for an IO system): only the actual maximum size is displayed. The status byte for each lower-level component is defined as follows: Bit 0 = SubFault: the component cannot be reached Bit 1 = Fault: the component is not available or faulty Bit 2 = Maintenance1: the component has reported a need for maintenance Bit 3 = Maintenance2: the component has reported a need for maintenance Bit 4 = Deactivated: the component was deactivated Bit 5 = SubFault: a subcomponent is faulty Bit 6 = SubMaintenance1: the component has reported a need for maintenance Bit 7 = SubMaintenance2: a subcomponent has reported a need for maintenance
480
8.1.5.9
PROFINET IO DB
481
OK 00
faulty 01
failed 10
not configured 11
Status Coding
482
8.1.5.10
PROFIBUS DP DB
"Manual" mode
In this mode, all errors of the selected station are displayed one after the other.
"Automatic" mode
In this mode, the errors of all configured stations are displayed one after the other.
483
8 10 11
MODULE_NO CHANNEL_NO CHANNEL_TYPE CHANNEL_ERROR_CODE CHANNEL_ERROR_INFO_1 CHANNEL_ERROR_INFO_2 DIAG_COUNTER DIAG_OVERFLOW BUSY DIAG_DAT_NORM
BYTE BYTE BYTE BYTE DWORD DWORD BYTE BOOL BOOL BYTE [1 to 244] DWORD [1 to 4] DWORD [1 to 4] DWORD [1 to 4] DWORD [1 to 4] DWORD [1 to 4] DWORD [1 to 4] BYTE [1 to 126] DWORD DWORD DWORD WORD WORD
1176 - 1191 CONFIG_SLAVES 1192 - 1207 EXIST_SLAVES 1208 - 1223 FAILED_SLAVES 1224 - 1239 FAULTY_SLAVES 1240 - 1255 AFFECT_SLAVES 1256 - 1271 AFFECT_SLAVES_MEM 1272 - 1397 DIAG_CNT 1404 1408 1412 1416 1418 ERROR_CAT HELP_CAT ERROR_NO MAP_ERRORNO MAP_HELPNO
484
BOOL [1 to 32] True if at least one station of the PROFIBUS master system (1 to 32) has failed BOOL [1 to 32] True if at least one station of the PROFIBUS master system (1 to 32) is faulty
8.1.5.11
Requirement
You are in the "Properties" area of the Inspector window of the required PLC.
Procedure
To display and edit the settings for system diagnostics, follow these steps: 1. Click "System diagnostics" in the area navigation of the Inspector window. In the right-hand part of the Inspector window, you can display and edit the various settings.
8.1.5.12
Basic settings
General settings
Here, you can decide which options will be enabled when the diagnostic block executes.
NOTICE If you disable this option, no diagnostics data is read out in the Web server and diagnostics viewer either even if the option is enabled there. If you disable this option on a PLC on which it was previously enabled, all the diagnostic data is deleted the next time you compile the hardware configuration.
Send alarms
This option is enabled by default. The diagnostics block then sends alarms as a reaction to system errors.
485
Alarming component
Select the component (for example module or rack) for which you want to configure the alarm text.
See also
Adapting event text/info text (Page 486)
See also
Settings for configuring alarms (Page 486) Working with text lists (Page 221) Working with multi-language projects (Page 180)
Attributes
The default alarm attributes "Priority", "Group ID" and "Display class" and the options "Logging" and "With acknowledgement" can be set separately for each individual reporting component. You will find more detailed information on the alarm attributes in the description of "Configuring alarms".
486
You can, however, assign different numbers and/or names for these blocks as long as they are not already being used.
Status DBs
Enable the required status DB to read out the current system status of configured components via this data block. The following status DBs are set as defaults:
Block Diagnostics status DB PROFINET IO DB PROFIBUS DP DB Name RSE_DIAGNOSTIC_STATUS_ DB RSE_PROFINET_IO_DB RSE_PROFIBUS_DP_DB Number 127 126 125
You can, however, assign different names and/or number for these blocks as long as they are not already being used. If the "Enable Web server on this module" functionality is enabled in the properties of the CPU, the diagnostics status DB must be enabled. As default, DB 127 is generated if the CPU supports the Web server and if this is enabled in the properties of the CPU. Note The status DBs "PROFINET IO DB" and "PROFIBUS DP DB" only have limited diagnostics functionality. It is therefore preferable to use the "diagnostics status DB".
487
8.1.5.13
Advanced settings
See also
Supported error OBs (Page 475)
488
Subcomponent error
Note In "Startup" mode, the PLC does not change to STOP regardless of the settings you made.
See also
Assignment of error classes to system errors (Page 489)
489
490
Failure AS-i slave PROFIBUS/central channel error AS-i slave PROFINET module Failure
* The CPU does not change to STOP mode. Note In "startup" mode, the CPU does not change to STOP.
See also
Settings for "PLC in STOP" (Page 488)
8.1.6
8.1.6.1
Displaying alarms
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 Shows the currently active (pending) alarms. Alarms that must be acknowledged are shown in bold characters. Ignores the arrival of alarms, These alarms are neither shown in the window nor stored in the archive. Confirms the selected alarm as read. Alarms requiring acknowledgment are shown in bold characters. Deletes all alarms in the archive. Clear archive
Active alarms
Ignore
Acknowledge
491
Export archive
8.1.6.2
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 bold characters and can be acknowledged with the context menu command "Acknowledge alarm(s)". The archive is constantly updated and does not need to be saved explicitly.
8.1.6.3
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 acknowledgement 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 context-sensitive with the button in the toolbar or with the shortcut menu command "Acknowledge alarm(s)".
8.1.6.4
Receiving alarms
To allow alarms to be displayed, you must first set the receipt of alarms for each CPU.
492
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 "Settings" group in area navigation. 3. Select the option "Receive alarms". Or: 1. Select the "Online & Diagnostics" folder of the relevant CPU in project navigation. 2. Open the "Online" menu and select "Receive alarms". Or: 1. Select the relevant CPU in the device or network view. 2. Select the "Receive alarms" command in the context menu. Or: 1. Select the CPU in project navigation. 2. Select the "Receive alarms" command in the context menu.
8.1.6.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.6.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.6.7
493
8.1.6.8
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 acknowledgement 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 context-sensitive with the button in the toolbar or with the shortcut menu command "Acknowledge alarm(s)".
8.1.6.9
8.1.6.10
Acknowledging alarms
Alarms that must be acknowledged are shown in bold characters.
494
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.
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.6.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.
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.
495
8.1.6.12
Alarm display
Function Select all alarms Acknowledge all selected alarms Shortcut keys Ctrl+A Ctrl+Q
8.1.7
8.1.7.1
496
See also
STOP mode (Page 502) RUN mode (Page 502)
The following table shows the conditions under which the operating modes will change:
No. Operating mode transition STOP STOP STARTUP Conditions After you turn on the power supply, the CPU is in "STOP" mode. It then determines the required type of startup and changes to the next operating mode. If the hardware configuration and the program blocks are consistent, the CPU changes to "STARTUP" mode in the following situations: The CPU is set to "RUN" from the programming device. After automatic triggering of a STARTUP operating mode by "POWER-ON". STARTUP STOP The CPU returns to the "STOP" mode in the following situations: An error is detected during startup. The CPU is set to "STOP" from the programming device. A STOP command is executed in the STARTUP OB.
497
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.
498
See also
Editing properties and parameters (Page 297) Principles of the operating modes of S7-CPUs (Page 496) Organization blocks for startup (Page 541) Warm restart (Page 499)
See also
Retentive memory areas (Page 507)
499
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. 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.
500
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: If an invalid SD card is inserted. If no hardware configuration has been downloaded.
WinCC Basic V11.0 SP2 System Manual, 04/2012,
501
See also
Overview of the CPU properties (Page 517)
See also
Principles of the operating modes of S7-CPUs (Page 496) Events and OBs (Page 510)
502
See also
Principles of the operating modes of S7-CPUs (Page 496)
Memory areas Things you should know about 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 a S7-CPU.
503
504
See also
Replacing a hardware component (Page 297)
See also
Using memory cards (Page 225)
505
Bit memory
See also
Diagnostics buffer (Page 509) Basic principles of process images (Page 507) Access to the I/O addresses (Page 510)
506
See also
Warm restart (Page 499)
507
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.
Update QW10 in the I/O output area with the value from MW0.
See also
Start address of a module (Page 509) Access to the I/O addresses (Page 510) Startup activities (Page 500)
508
See also
Basic information on the diagnostics buffer (Page 612)
509
This could be necessary, for example, during execution of a time time-sensitive program which also has to control the outputs within the same cycle.
510
1, >= 200 >= 1 100, >= 200 >= 200 >= 200 >= 200
82 80
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 Insert/remove distributed I/O modules (PROFINET or PROFIBUS) I/O access error during process image update Programming error Event Insert/remove a module Event priority 21 21 System reaction STOP RUN
I/O access error during process image update 22 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
Ignore RUN
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). 27
RUN
Maximum cycle time exceeded Maximum cycle time exceeded twice twice
STOP
511
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 512)
512
Figure 8-2
Program sequence
513
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.
514
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.
515
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.
516
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 297) Introduction to loading a configuration (Page 470)
517
518
Protection and password for read/ Setting options for the level of protection (Page 540) write access
519
Communications load Maximum allocation of the cycle for communication (as a percentage) I/O addresses 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 386) Configuring high-speed counters (Page 527) Setting options for the level of protection (Page 540) Cycle time and maximum cycle time (Page 521) Cycle loading by communications (Page 522) Assigning parameters to hardware interrupt OBs (Page 549) Principles of the STARTUP mode (Page 498) Access to the I/O addresses (Page 510) Using clock memory (Page 538) Addressing modules (Page 385) Special features during startup (Page 501)
520
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.
521
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.
522
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 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.
523
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 the time of day "WR_SYS_T" Read local time "RD_LOC_T" Write local time "WRLT_DTL"
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".
524
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. 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.
See also
Configuring high-speed counters (Page 527) Interdependency of the counter mode and counter inputs (Page 526)
525
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.
526
HSC1 and HSC2 support the motion axis count mode for the PTO1 and PTO2 pulse generators: 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 524) Configuring high-speed counters (Page 527)
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: HSC1 to HSC6
527
528
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 524) Interdependency of the counter mode and counter inputs (Page 526)
529
See also
Configuring a communications port (Page 530)
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.
530
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. 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.
531
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 532)
532
See also
Configuring a communications port (Page 530)
533
See also
User-programmed communication with RS-232 devices (Page 534) Making the settings for sending (Page 536) Specifying the start of the message (Page 536) Specifying the end of the message (Page 537)
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.
534
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.
535
See also
Configuration of message transfer (Page 533) Making the settings for sending (Page 536) Specifying the start of the message (Page 536) Specifying the end of the message (Page 537)
See also
Specifying the start of the message (Page 536) Specifying the end of the message (Page 537) User-programmed communication with RS-232 devices (Page 534)
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:
536
See also
Making the settings for sending (Page 536) User-programmed communication with RS-232 devices (Page 534)
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:
Parameter Recognize end of message by message timeout Recognize end of message by reply timeout Definition 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. 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.
537
See also
Making the settings for sending (Page 536) User-programmed communication with RS-232 devices (Page 534)
538
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 Period (s) Frequency (Hz) 7 2.0 0.5 6 1.6 0.625 5 1.0 1 4 0.8 1.25 3 0.5 2 2 0.4 2.5 1 0.2 5 0 0.1 10
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.
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.
539
Note The selected memory byte cannot be used for intermediate storage of data.
540
Start information
A startup OB has the following start information:
Tag LostRetentive LostRTC Data type BOOL BOOL Description = 1, if retentive data storage areas have been lost = 1, if realtime clock has been lost
541
See also
Events and OBs (Page 510)
542
Start information
Cycle OBs have no start information.
See also
Events and OBs (Page 510)
Organization blocks for interrupt-driven program execution 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.
543
Start information
Time delay interrupt OBs have no start information.
See also
Events and OBs (Page 510)
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 interrupt OB is started. The cyclic interrupt that caused the error is executed later or discarded.
544
Start information
Cyclic interrupt OBs have no start information.
See also
Assigning parameters to cyclic interrupt OBs (Page 550) Events and OBs (Page 510)
545
Start information
Hardware interrupt OBs have no start information.
See also
Assigning parameters to hardware interrupt OBs (Page 549) Events and OBs (Page 510)
546
Start information
The time error interrupt OB has the following start information:
Tag fault_id Data type BYTE Description 0x01: Maximum cycle time exceeded 0x02: Called OB is still being executed 0x07: Queue overflow 0x09: Interrupt loss due to high interrupt load csg_OBnr csg_prio OB_ANY UINT Number of the OB being executed at the time of the error Priority of the OB being executed at the time of the error
See also
Events and OBs (Page 510)
Start information
The diagnostic error interrupt OB has the following start information:
Tag IO_state laddr Channel multi_error Data type WORD HW_ANY UINT BOOL Description Contains the I/O status of the diagnosticscapable module. HW-ID Channel number = 1, if there is more than one error
547
IO_state tag
The following table shows the possible I/O states that the IO_state tag can contain:
IO_state Bit 0 Description 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 510)
Overview
You can assign parameters to the properties for the following organization blocks: Hardware interrupt OBs Cyclic interrupt OBs
See also
Assigning parameters to hardware interrupt OBs (Page 549) Assigning parameters to cyclic interrupt OBs (Page 550)
548
Procedure
To assign parameters for the hardware interrupt OB, 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. 7. Enter an event name. 8. Select an existing hardware interrupt OB from the "Hardware interrupt" drop-down list. Note If you have not previously created any hardware interrupt OB, you can click "Add new block" in the drop-down list. See also: Auto-Hotspot 9. If you want to assign further hardware interrupts, repeat steps 5 to 8.
See also
Basics of block parameters (Page 548) Organization blocks for hardware interrupts (Page 545) Events and OBs (Page 510)
549
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 548) Organization blocks for cyclic interrupts (Page 544)
550
551
Functions (FCs)
Numerical name FC 2 (1) FC 4 (1) FC 11
(1)
Symbolic name CONCAT DELETE FIND INSERT LEFT LEN LIMIT MAX MID MIN REPLACE RIGHT ENCO SEL DECO LED IM_DATA DeviceStates ModuleStates USS_PORT USS_RPM USS_WPM
FC 26 (1)
(1)
FC 31 (1)
(1)
MC7+ instruction
552
Symbolic name CTU CTD CTUD TP TON TOF START_OB RDREC WRREC RALRM T_CONFIG TDIAG TRESET PORT_CFG SEND_CFG RCV_CFG SEND_PTP RCV_PTP SGN_GET SGN_SET RCV_RST CTRL_HSC CTRL_PWM DataLogCreate DataLogOpen DateLogWrite DataLogClear DataLogClose DataLogDelete DataLogNewFile
SFB 27 SFB 52 SFB 53 SFB 54 SFB 105 SFB 106 SFB 107 SFB 110 SFB 111 SFB 112 SFB 113 SFB 114 SFB 115 SFB 116 SFB 117 SFB 120 SFB 122 SFB 140 SFB 141 SFB 142 SFB 143 SFB 144 SFB 145 SFB 146
553
554
8.1.7.2
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, 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 ET 200S Properties 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
555
The following table provides an overview of I/O devices for use without a control cabinet:
I/O device ET 200pro Properties 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
556
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)
Area of application
The ET 200iSP distributed I/O station can be operated in potentially explosive atmospheres characterized by gas and dust:
Approval ATEX IECEx ET 200iSP Station* Zone 1, Zone 21 Zone 2, Zone 22 Inputs and outputs up to Zone 0, Zone 20 ** 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.
557
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)
Requirements
The HART field device must support the assigned number of IEEE tags.
558
See also
Documentation on ET 200iSP (http://support.automation.siemens.com/WW/view/de/ 28930789/0/en)
559
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-1 Compensation of the reference junction temperature Explanation 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. 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. Number of reference junctions: 2 Reference junction parameters None
Option No compensation
Use of a Pt100 Climatic Range resistance thermometer to record the reference junction temperature (best method)
The parameter assignment of the IM 152 and the 4 AI TC must be coordinated: 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.
560
IM 152
4 AI TC 4 AI TC
See also
Documentation on ET 200iSP (http://support.automation.siemens.com/WW/view/de/ 28930789/0/en)
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, ...).
561
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 Time stamping Setting disabled enabled Edge evaluation incoming event rising edge falling edge Description Activate the time staming for the channels of the electronics module 8 DI NAMUR. Determine the type of signal change that will be time-stamped.
See also
Principle of operation (Page 562) Configuring counters (Page 565) Assigning parameters to counters (Page 568)
562
563
See also
Count properties (Page 562)
564
565
566
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 562)
567
See also
Count properties (Page 562)
See also
Principle of operation (Page 569) Configuring frequency meters (Page 569) Assigning parameters for the frequency meters (Page 571)
568
See also
Frequency measurement properties (Page 568)
569
Assignment of the process image output (PIQ): The PIQ is not assigned.
See also
Frequency measurement properties (Page 568)
570
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-6 Parameter Sensor type frequency inputs Parameters for the frequency meters Setting Channel disabled 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) Description Select the sensor for the relevant frequency meter for channel 0 or 1.
See also
Frequency measurement properties (Page 568)
571
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)
572
Temperature unit
Specify the unit of the temperature measurement here.
Measuring range
With this parameter, you set the measuring range of the selected measurement type.
573
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.
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:
574
Explanation Diagnostics, wire break Measured value after leaving the underrange Diagnostic message Lower limit value undershot
Wire break
8000H
Measuring range limits for wire break detection and measuring range undershoot detection:
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.
575
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, overload
If you enable this parameter, the diagnostics event is generated in the event of an overload.
576
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.
See also
Changeover contact (Page 577) Technological parameters (Page 578)
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)
577
See also
Documentation on modules for process automation (http://support.automation.siemens.com/ WW/view/de/7215812/0/en)
See also
Documentation on modules for process automation (http://support.automation.siemens.com/ WW/view/de/7215812/0/en)
578
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.
See also
Documentation for the frequency converter (http://support.automation.siemens.com/WW/view/ en/26291825/0/en)
579
See also
Sensor type (Page 580) Switching hysteresis (Page 581) Time function,time value (Page 582)
Sensor type
This parameter is used to set the sensor type per channel: Reflex sensor or Diffuse sensor or De-activated
580
Diffuse sensor
Table 8-7 Transmitter Receiver Diffuse sensor Object Circuit state 0: no object detected, i.e. the object is not in the beam. The receiver does not see any light. Circuit state 1: object detected, i.e. the object is in the beam. The receiver does not see any light.
Diffuse sensor
Transmitter Receiver
Reflex sensor
Table 8-8 Transmitter Receiver Reflex sensor Object Circuit state 0: no object detected, i.e. the object is not in the beam. The receiver sees light. Circuit state 1: object detected, i.e. the object is in the beam. The receiver does not see any light.
Reflex sensor
Transmitter Receiver
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.
Prerequisites
You can only set the switching hysteresis parameter for diffuse sensors with background fadeout.
581
Operating principle
Figure 8-3
582
Operating principle
Figure 8-4
583
8.2
8.2.1
8.2.1.1
584
See also
Basics on task cards (Page 150) Inspector window (Page 148)
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.
585
See also
Determination of online status and display using symbols (Page 586)
Determination of online status and display using symbols 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 subordinate components will be determined. The operating mode of the device is also determined, where applicable. The following is a description of the symbols that are displayed in a specific view. Device view The associated diagnostics icon is displayed for every hardware component (except the signal board on the CPU). For hardware components with subordinate components, an "Error in subordinate component" diagnostics icon will also be displayed in the hardware component diagnostics icon if an error is present in at least one subordinate component. For hardware components with their own operating mode, the operating mode icon will also be displayed to the left of or above the diagnostics icon. Device overview The associated diagnostics icon is displayed for every hardware component. For hardware components with subordinate components, an "Error in subordinate component" diagnostics icon will also be displayed in the bottom right corner of the hardware component diagnostics icon if an error is present in at least one subordinate component. Network view The associated diagnostics icon is displayed for every device. If an error is present in at least one subordinate component, then the "Error in subordinate component" diagnostics icon will also be displayed in the bottom right corner of the diagnostics icon.
586
587
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 diagnostics interrupt when setting the module properties.
588
Note If both a comparison icon and the "Error in subordinate component" diagnostics icon are to be displayed at the bottom right in the device view, the following rule applies: The diagnostics icon for the subordinate hardware component has a higher priority than the comparison icon. This means that a comparison icon is only displayed if the subordinate hardware components have no faults.
Note If forcing is active on a CPU, a red F will be displayed on a pink background at the bottom right of the operating mode icon.
589
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.
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:
590
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.
591
See also
View in online mode (Page 1475)
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 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.
"Module" area
This area shows the following data of the module: Short designation, for example, CPU 1214C DC/DC/DC Order no.
592
593
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.
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
594
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:
595
Status
If you select a line in the port table, additional help information will be provided for the corresponding port.
8.2.1.3
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.
596
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.
597
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 "Memory" pane display area of 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 respective 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 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 a memory area is utilized to less than 1%, the available portion of this memory area is shown as "99%". The following memory utilizations are shown:
598
See also
Load memory (Page 505) Work memory (Page 505) Retentive memory areas (Page 507)
8.2.1.4
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)
"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. 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.
599
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.
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
600
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.
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.
601
For S7-1200 CPUs only: 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. Sorting is possible, but only by the sequential numbers.
602
603
"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
See also
Basic information on the diagnostics buffer (Page 612)
8.2.1.5
604
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.
605
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 503)
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.
606
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.
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.
607
Result
The IP address will be assigned to the IO device.
608
Procedure
To reset a CPU to the factory settings, follow these steps: 1. Open the Online and Diagnostics view of the CPU. 2. Select the "Reset to factory settings" group from the "Functions" folder. Note The MAC address is not displayed for S7-1200 CPUs. 3. Select the "Retain IP address" check box if you want to retain the IP address or the "Delete IP address" 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 factory settings are then reset. This means: The work memory and the internal load memory and all operand areas are deleted. All parameters are reset to their defaults. The diagnostics buffer is cleared. The time of day is reset. The IP address is retained or deleted depending on the setting you make.
609
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.
610
See also
Calling the name assignment function from the project tree or via the "Online" menu (Page 611) Calling the name assignment function from within the project context (Page 611)
Calling the name assignment function from the project tree or via the "Online" menu Requirement
You have opened the Online and Diagnostics view of the PROFINET IO device from the project tree or with the "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: Click the "Flash LED" button on the left of the graphic to run an LED flash test for 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. 4. Click "Assign name".
Result
The entered name is assigned to the PROFINET IO device.
Calling the name assignment function from within the project context Requirement
An online connection to the PROFINET IO device is not required. You have opened the Online and Diagnostics view of the PROFINET IO device from within the project context. The PROFINET IO device can be accessed using at least one PG/PC.
611
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. 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: Click the "Flash LED" button to run an LED flash test for 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. 8. Click "Assign name".
Result
The selected name is assigned to the PROFINET IO device.
8.2.1.6
612
See also
Resetting a CPU to the factory settings (Page 609) Determining the cause of a STOP of a CPU (Page 614) Determining and setting the time of day on a CPU (Page 606) Parameterizing the clock (Page 524)
613
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.
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 600)
614
8.2.1.7
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. However, if you have opened the Online and Diagnostics view using the "Show/update accessible devices" function, it will not be displayed.
Result
The status of the online connection is displayed in the "Status" area both graphically and in text form.
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. However, if you have opened the Online and Diagnostics view using the "Show/update accessible devices" function, it will not be displayed.
615
Result
The online connection to the desired device will be established.
See also
Establishing and canceling an online connection (Page 1480)
616
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. However, if you have opened the Online and Diagnostics view using the "Show/update accessible devices" function, it will not be displayed. 3. Click the "Go offline" button.
Result
The online connection to the desired device will be disconnected.
See also
Establishing and canceling an online connection (Page 1480)
Performing the flash test for a device with an online connection 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 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. However, if you have opened the Online and Diagnostics view using the "Show/update accessible devices" function, it will not be displayed. 3. Click the "LED Flash test" button.
617
Result
On an S7-1200 CPU, the RUN/STOP, ERROR and MAINT LEDs flash. On an S7-300 or S7-400 CPU, the FRCE LED flashes. Note The flash test cannot be performed when the FORCE function is active.
8.2.1.8
618
See also
Displaying the status of the segment diagnostics using icons (Page 619) Displaying the status of the segment diagnostics using graphics and text (Page 619)
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
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.
619
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.
620
8.2.2
8.2.2.1 Basics
Connection diagnostics
Overview of connection diagnostics
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.
621
8.2.2.2
622
8.2.2.3
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 diagnostics icon of the instruction (3 squares back-to-back at an angle in green, yellow, red).
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 only) If a connection has been selected (connection table), it will contain the following groups: Connection details Address details of the connection (for S7-1200 only)
623
624
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 "Address details for connection" group. This group is located in the "Diagnostics > Connection information" area of the Inspector window.
For which CPUs is the "Address details for connection" group available?
The "Address details for connection" group of the "Connection information" tab is available for S7-1200 CPUs only.
625
Creating screens
Basics
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.
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.
627
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.
9.1.1.2
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:
WinCC Basic V11.0 SP2 System Manual, 04/2012,
628
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.
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.
629
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.
Basics
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:
Icon Meaning Displays the objects as a list. Displays the objects as a graphic.
630
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: Zoom: Serves to select detail view 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.
Requirement
A screen is open. The view shows only a screen section.
631
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.
Requirement
The screen is opened.
632
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 open the "Layout" task card and change the screen view.
Result
The selected screen section is magnified.
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
Requirement
The project has been created. The Inspector window is open.
633
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.
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.
634
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.
Requirement
The project contains the screen you want to use as the start screen.
635
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.
9.1.1.5
636
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 639) Managing templates (Page 640) Global screen (Page 637) Using a template in the screen (Page 641)
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:
637
638
See also
Basics on working with templates (Page 636)
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.
639
See also
Basics on working with templates (Page 636)
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.
See also
Basics on working with templates (Page 636)
640
Requirement
A template has been created. A screen has been created.
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".
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 636)
9.1.2
9.1.2.1
Introduction
Objects are graphics elements which you use to design the screens of your project.
641
642
Basic objects
Icon Object "Line" "Ellipsis" "Circle" "Rectangle" "Text field" "Graphic view" Instructions One or more lines of text. The font and layout are adjustable. 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 "I/O field" Instructions 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, activate "Hidden input." "Button" "Symbolic I/O field" "Graphic I/O field" "Date/time field" Executes a list of functions, or a script as configured. 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. 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. 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. The bar represents a value from the PLC in the form of a scaled bar graph. Toggles between two defined states. You can label a switch with text, or a graphic.
"Bar" "Switch"
Controls
Icon Object "Alarm view" "Trend view" Description Shows currently pending alarms or alarm events from the alarm buffer or alarm log. Represents multiple curves with values from the PLC, or from a log.
643
See also
Options for Editing Objects (Page 644) Inserting an object (Page 645) Deleting an Object (Page 647) Positioning an object (Page 648) Resizing an object (Page 649) Selecting multiple objects (Page 650) Aligning objects (Page 652) Moving an object forward or backward (Page 654) Show objects outside the screen area (Page 655) Rotating objects (Page 656) Flipping objects (Page 657) Inserting multiple objects of the same type (stamping tool) (Page 658) Repositioning and resizing multiple objects (Page 660) External graphics (Page 660) Managing external graphics (Page 661) Storing an external image in the graphics library. (Page 663) Basics on groups (Page 665) Overview of keyboard access (Page 671) Example: Inserting and configuring a rectangle (Page 674)
9.1.2.2
Introduction
Objects are graphics elements which you use to design the screens of your project. You have the following options for editing objects:
644
See also
Overview of objects (Page 641)
9.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:
645
Requirement
The "Tools" task card is open.
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.
646
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 641)
9.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 641)
647
9.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.
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.
648
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 641)
9.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.
649
Procedure
1. Select the object you want to resize. The selection rectangle appears. The following figure shows a selected object:
2. Drag a resizing contact of the rectangle to a new position. The size of the object changes. The size of the object is aligned to the grid pattern, provided the "Snap to grid" function is set. Press <ALT> to disable this function while you drag the object. Note In order to scale the object proportionally, keep the <Shift> key pressed while changing the size with the mouse.
Alternative procedure
1. In the Inspector window, select "Properties > Properties > Layout". 2. Enter the size of the object under "Position & Size".
Result
The object now appears with its new size.
See also
Overview of objects (Page 641)
9.1.2.7
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.
650
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.
651
Result
Multiple objects are selected. One of those is identified as the reference object. You can now perform the following steps: Changing the object properties of all the objects Resizing all the objects by the same ratio, by dragging the selection frame to increase or reduce the size Moving all the objects in one group Aligning the objects to the reference object
See also
Overview of objects (Page 641)
9.1.2.8 Procedure
Aligning objects
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.
652
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.
653
See also
Overview of objects (Page 641)
9.1.2.9
Introduction
You can use the "Order" functions in the shortcut menu of a selected object or in the toolbar to move a selected object in front of or behind other objects within an object layer. Note ActiveX controls are always positioned in front of an object layer (.NET property).
Requirement
You have opened a screen which contains a layer with multiple objects.
Procedure
1. Select the object you want to move forward or backward. 2. Select the "Sort" command and one of the following commands from the shortcut menu:
Icon Description Moves the selected object before all the other objects of the same layer Moves the selected object to the lowest position in the same layer Moves the selected object up by one position Moves the selected object down by one position
Alternative procedure
1. Open the "Layers" palette of the "Layout" task card. 2. Navigate to the required object. 3. Hold down the mouse button, and drag the object in the tree topology to the required position in the layer. 4. Now release the mouse button.
654
Result
The object is moved up or down.
See also
Overview of objects (Page 641)
9.1.2.10
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.
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 icon. If you click this icon, the object is moved back into the screen. the
Result
The objects are moved to the configurable area.
See also
Overview of objects (Page 641)
655
9.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:
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.
656
Result
The object is shown at its new angle.
See also
Overview of objects (Page 641) Ellipse (Page 740)
9.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.
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.
657
See also
Overview of objects (Page 641) Ellipse (Page 740)
9.1.2.13
Designing an object
Introduction
You design the border and background of an object.
Requirement
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.
9.1.2.14
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.
658
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.
659
See also
Overview of objects (Page 641)
9.1.2.15
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 641)
9.1.2.16
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.
660
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 641)
9.1.2.17
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.
661
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
662
See also
Overview of objects (Page 641)
9.1.2.18
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.
663
664
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 641)
9.1.2.19
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.
665
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.
Layers
All objects of a group are located in the same layer.
See also
Overview of objects (Page 641)
Requirement
You have opened a screen which contains at least two objects.
666
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.
667
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.
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.
668
Requirement
You have opened a screen that contains a group.
669
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.
Requirement
You have opened a screen that contains a 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."
670
The properties of the object are displayed. 3. Change the object properties.
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.
9.1.2.20
671
See also
Example: Inserting and configuring a rectangle (Page 674) Overview of objects (Page 641)
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.
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.
672
See also
Example: Inserting and configuring a rectangle (Page 674)
Requirement
The active screen contains operable objects. No object is selected. The objects have been enabled for use in runtime, and have operator authorization.
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):
673
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 674)
9.1.2.21
Examples
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.
674
Overview
Carry out the following steps in order to create a rectangle: Inserting a rectangle Configuring a rectangle
See also
Basics on groups (Page 665) Overview of objects (Page 641)
Requirement
A screen is open. The Inspector window is open. The "Tools" task card is open.
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.
675
Interim result
The rectangle is red and has a black frame with a width of two pixels.
3. Set "20" for the both the X and Y coordinates under "Position & Size". 4. Set "100" for the height and for the width.
676
Result
The rectangle is positioned at the coordinates (20, 20), and has a width and height of 100 pixels.
9.1.3
9.1.3.1
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."
677
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
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.
678
Result
A text list is created.
Requirement
The "Text and graphics list" editor is open. The "Text lists" tab is open. An area text list has been created and selected.
679
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.
680
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".
681
Result
A bit text list is created. Texts that appear in Runtime are assigned to the possible values "0" and "1".
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.
682
Result
A bit number text list is created. Texts that appear in Runtime are assigned to the specified bit numbers.
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.
683
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.
9.1.3.2
684
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
685
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.
686
Requirement
The "Text and graphics list" editor is open. The "Graphics list" tab is open. An area graphics list has been created and selected.
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.
687
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.
Requirement
The "Text and graphics list" editor is open. The "Graphics list" tab is opened. A bit graphics list has been created and selected.
688
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".
689
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.
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.
690
Result
A bit number graphics list is created. Graphics that appear in Runtime are assigned to the specified bit numbers.
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.
691
9.1.4
9.1.4.1
Dynamizing screens
Basics on dynamization
Dynamizing objects
In WinCC you dynamize objects to map your system and show processes on HMI devices. 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 692) Configuring a new animation (Page 694) Basic on events (Page 703)
9.1.4.2
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:
692
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.
693
You will find further information in "Working with function lists (Page 929)".
See also
Basics on dynamization (Page 692)
9.1.4.3
Requirement
You have opened a screen which contains at least one dynamic object. The Inspector window is open. The toolbox window is displayed.
694
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 700) Basics on dynamization (Page 692)
695
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. 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. button.
696
Result
In Runtime, the flashing response, and color of the object change dynamically according to the process value returned in the tag.
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.
697
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. button. 3. Select "Horizontal movement" and click the 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.
698
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 movement in the same way as horizontal movement
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.
699
Result
In Runtime, the object moves in response to every change in value of the tag that is used to control the movement.
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.
700
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. button. 3. Select "Visibility" and click the The parameters of the animation are displayed. 4. Select a tag. 5. Activate "Single bit". 6. Select bit number "6" for example. 7. Activate "Visible".
Result
The screen object is shown or hidden in Runtime depending on the tag value. If the tag value matches the configured bit number exactly, the screen object is shown. If the tag value matches the configured bit number exactly, the screen object is hidden.
See also
Configuring a new animation (Page 694)
701
If you configure an animation for an object group, this animation will apply to all individual objects that support this animation.
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.
702
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.
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.
9.1.4.4
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. Further information can be found in Working with function lists (Page 929)
See also
Basics on dynamization (Page 692) Example: Configuring a button for language switching (Page 704) Configure system function on the "Click" event (Page 704)
703
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.
Result
The alarm window opens in the screen if the operator clicks the button in runtime.
See also
Basic on events (Page 703)
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.
704
Procedure
1. In the Inspector window, select "Properties > Events > Press". 2. Click on "Add function" in the table. 3. Select the "SetLanguage" system function.
Result
You have assigned the button the function "SetLanguage". Pressing the button during runtime will switch the runtime language. The runtime languages are switched in the order specified by the number sequence in the "Languages and fonts" editor.
See also
Basic on events (Page 703) Button (Page 758)
9.1.5
9.1.5.1
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.
705
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 9-1 Function key The following table shows which symbols display the assignment of the function keys: Description Not assigned
Global assignment
706
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, which already overwrites global assignment) Assigning buttons with screen navigation
Note Basic Panels The "Screen Navigation" editor is not available for Basic Panels.
9.1.5.2
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.
707
Requirement
You have opened the project. The Inspector window is open.
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.
708
9.1.5.3
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.
Requirement
You have opened the screen or the template in which you want to assign a function key locally. The Inspector window is open.
709
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.
9.1.5.4
Introduction
A function key can have two states: Pressed: Defined by the "Key pressed" event. Released: Defined by the "Release key" event.
710
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.
9.1.5.5
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
711
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.
712
Result
The operator authorization is configured.
9.1.5.6
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.
713
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. 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.
714
Result
The graphic is displayed next to the function key.
9.1.5.7 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.
715
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.
716
9.1.6
9.1.6.1 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 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.
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
717
9.1.6.2
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.
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.
Result
The object is assigned to the selected layer, and positioned at the top of the layer.
9.1.6.3
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 icon in the "Layout > Layers" task card. by the Layer 0 is the active layer when you start programming. You can activate a different layer during configuration, if necessary.
718
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".
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.
9.1.6.4
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.
719
Requirement
The screen is opened. The "Layout" task card is open.
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.
720
9.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.
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".
Result
The layer is displayed with the new name.
721
9.1.7
9.1.7.1
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. Libraries are managed in the "Libraries" task card. 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.
722
Global libraries
In addition to the objects from the project library, you can also incorporate objects from global libraries in your projects. A global library is saved independently of the project data in its own file with the extension *.aI11. 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 Structures
See also
Copy templates and types (Page 723)
9.1.7.2
Introduction
Both the "Project library" and the "Global library" contain the two folders "Copy templates" and "Types". You can create or use the library objects either as a copy template or a type.
Copy templates
Use copy templates to create independent copies of the library object.
723
Types
Create instances of objects of the "Types" folder and use these 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.
See also
Basics on libraries (Page 722)
9.1.7.3
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.
724
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.
725
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.
9.1.7.4
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.
726
Requirement
At least one library object has been created in a library. The "Libraries" task card is opened.
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.
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.
727
Result
The library objects are displayed in accordance with the configuration. The components of the faceplates are displayed.
728
9.1.7.5
Introduction
You can always copy or move library objects within the categories of a library. Delete the library objects you do not require. Note Copy templates and types You can only copy and move library objects within the same library. You can only copy copy templates to the "Copy templates" folder or any sub-folder of "Copy templates". You can also only insert types in the "Types" folder or any sub-folder of "Types".
Requirement
You have opened a library which contains several categories and at least one object. The library object is shown.
729
9.1.7.6
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.
730
9.1.7.7
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. If the inserted object already exists, you can use a dialog window to specify whether or not the existing object should be replaced or inserted under a new name. Enter a new name if you do not want to replace the existing object. 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 the library object that you want to insert in the library. 2. Drag-and-drop the library object to the position in the work area where you want to insert the object. The library object is inserted. 3. Select the library object in the screen and adapt it.
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.
9.1.7.8
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.
731
Requirement
You have opened the project. The "Libraries" task card is opened.
Procedure
icon in the "Libraries > Global libraries" task card. 1. Click the 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".
Result
The new library is shown in the "Global libraries" palette. The global library contains the "Types" and "Copy templates" folders. You can save objects to the library.
9.1.7.9
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 opened. A library has been changed.
WinCC Basic V11.0 SP2 System Manual, 04/2012,
732
Procedure
1. Select the global library that you want to save. 2. Click the icon in the "Libraries" task card in the "Global libraries" 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.
9.1.7.10
Introduction
In WinCC, the global libraries are stored in separate files. You can use a global library in every project.
Requirement
You have saved a global library. A project is open. The "Libraries" task card is opened.
Procedure
icon in the "Global libraries" palette. 1. Click the The "Open global library" dialog box is displayed. 2. Select the path in which the library is stored. 3. Click "Open." Note If you want to access a global library from several projects, the global library will have to be read-only when you open it. As soon as a global library is read-only, access from other projects is blocked.
Result
WinCC displays the opened global library in the "Global libraries" palette.
733
9.1.8
9.1.8.1
Objects for Basic Panels Availability of display and operating elements 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 control objects for the Basic Panels.
Overview
KP300 Basic KP400 Basic KTP400 Basic KTP600 Basic KTP1000 Basic TP1500 Basic Bar User view Date/time field I/O field Ellipse Graphic view Graphic I/O field Help indicator Circle Trend view Line Alarm view Alarm window Alarm indicator Rectangle Recipe view Button Switch Symbolic I/O field Text field Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes
734
Objects
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 "Segmented" Description 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. If a particular limit was reached, the entire bar changes color.
"Entire bar"
735
See also
Device-Specific Nature of the Objects (Page 734)
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".
WinCC Basic V11.0 SP2 System Manual, 04/2012,
736
See also
Device-Specific Nature of the Objects (Page 734) Simple user view (Page 1438) Configuring a user view (Page 910)
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.
Using tags
The time of the interconnected tag is displayed in the date/time field. 1. Click the "General" group in the inspector window. 2. In the "Format" area, select a tag with the "DateTime" data type, e.g. an internal tag. Information about data types which are available for connection to other PLCs can be found in the documentation about the respective communication drivers.
737
See also
Device-Specific Nature of the Objects (Page 734)
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".
738
Mode
The response of the I/O field is specified in the Inspector window in "Properties > Properties > General > Type".
Mode "Input" "Input/output" "Output" Description Values can only be input into the I/O field in runtime. Values can be input and output in the I/O field in runtime. 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 "Binary" "Date" "Date/time" "Decimal" "Hexadecimal" "Time" "Character string" Input and output of values in binary form Input and output of date information. The format depends on the language setting on the HMI device. Input and output of date and time information. The format depends on the language setting on the HMI device. Input and output of values in decimal form Input and output of values in hexadecimal form Input and output of times. The format depends on the language setting on the HMI device. Input and output of character strings.
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".
739
See also
Device-Specific Nature of the Objects (Page 734)
Ellipse Application
The "Ellipse" is an enclosed object that 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: 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 734) Rotating objects (Page 656) Flipping objects (Page 657)
740
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.
741
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.
See also
Device-Specific Nature of the Objects (Page 734) Storing an external image in the graphics library. (Page 663) Options for Editing Objects (Page 644) Objects for Basic Panels (Page 734)
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.
742
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.
Mode "Input" "Input/output" "Output" "Two states" Description The "Graphic I/O field" object is only used to select graphics. The "Graphic I/O field" object is used to select and display graphics. The "Graphic I/O field" object is used to display graphics only. 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.
743
See also
Device-Specific Nature of the Objects (Page 734) Symbolic I/O field (Page 759)
You configure the object "help indicator" exclusively in the global screen.
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 734)
744
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 734)
745
Layout
In the Inspector window, you customize the position, shape, style, color, and font types of the object. You can adapt the following properties in particular: Display 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.
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
Description Scrolls back to the beginning of the trend recording. The start values with which the trend recording started are displayed. Zooms into the displayed time section. Zooms out of the displayed time section. Moves the ruler back. Moves the ruler forward. Scrolls back one display width. Scrolls forward one display width. Shows or hides the ruler. The ruler displays the Xvalue associated with a Y-value. Stops trend recording or continues trend recording.
"Zoom in" "Zoom out" "Ruler backward" "Ruler forward" "Backward" "Forward" "Ruler" "Start/stop"
746
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.
See also
Device-Specific Nature of the Objects (Page 734) Configuring trend displays for values from the PLC (Page 803) Touch and key operation (Page 1432) Overview (Page 1431)
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.
747
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.
See also
Device-Specific Nature of the Objects (Page 734)
748
Layout
In the Inspector window, you customize the position, shape, style, color and font types of the object. Note The fonts available for selection depend on the "Language and fonts" you have configured in the Runtime settings. You can adapt the following properties in particular: 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.
749
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 "Info text" Function Displays info text for an alarm.
"Acknowledge"
Acknowledges an alarm.
"Loop-In-Alarm"
Switches to the screen containing information about the error that has occurred.
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".
750
See also
Device-Specific Nature of the Objects (Page 734) Alarm window (Page 751) Alarm indicator (Page 753) Configuring an alarm view (Page 829)
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.
751
Layout
In the Inspector window, you customize the position, shape, 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 windows: 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.
Control elements
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 "Tooltip" Function Displays a tooltip for an alarm.
"Acknowledge"
Acknowledges an alarm.
"Loop-In-Alarm"
Switches to the screen containing information about the error that has occurred.
752
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 Automatic display Closable Modal Function The Alarm window is automatically displayed when a system alarm occurs, for example. The window closes again after a set time has elapsed. You define the display duration in the alarm settings. 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 for a function key are carried out. You can change the size of the Alarm window in runtime.
Sizeable
See also
Device-Specific Nature of the Objects (Page 734) Alarm view (Page 748) Configuring an alarm window (Page 831)
753
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".
See also
Device-Specific Nature of the Objects (Page 734) Alarm view (Page 748) Configuring an alarm indicator (Page 832)
754
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.
See also
Device-Specific Nature of the Objects (Page 734) Rotating objects (Page 656) Flipping objects (Page 657)
755
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: Control elements: Specifies the menu commands of the recipe view.
Control elements
The menu commands with which the recipe view is operated in Runtime are configured under "Properties > Buttons" in the inspector window.
Menu command "Tooltip" "New record" "Delete record" "Saving" "Save as" "Write to PLC" "Read from PLC" Description Calls up the configured tooltip for the selected recipe. Creates a new recipe record in the recipe. Deletes the selected record. Saves the modified record with its current name. Saves the modified record with a new name. Sends the current value to the PLC. Reads the current value from the PLC.
See also
Device-Specific Nature of the Objects (Page 734) Simple recipe view (Page 873) Displaying recipes (Page 867) Configuring the simple recipe view (Page 884) Description of the simple recipe view (Page 887)
756
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.
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
The button display is defined in "Properties > Properties > General >Settings" in the Inspector window.
Type "Switch" Description 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" "Switch with graphic" 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. 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 734) Elements (Page 997) Overview of objects (Page 641)
757
Button Application
The "Button" object allows you to configure an object that the operator can use in runtime to execute any configurable function.
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 "Invisible" "Text" "Graphic" Description The button is not visible in runtime. The current state of the button is visualized with a label. The current state of the button is visualized with a graphic.
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 >Label > Text" or "Graphic" in the Inspector window.
Type "Text" Option "Text" Description "Text OFF" is used to specify a text that appears in the button when the state is "OFF". If you enable "Text ON", you can enter a text for the "ON" state. "Text list" The text in the button depends on the state. The entry from the text list corresponding to the state is displayed.
758
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 734) Example: Configuring a button for language switching (Page 704) Example: Configuring a button with logon dialog box (Page 918) Example: Configuring a button with access protection (Page 922)
759
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".
Mode
The response of the symbolic I/O field is specified in the Inspector window in "Properties > Properties > General > Type".
Mode "Output" "Input" "Input/output" "Two states" Description The symbolic I/O field is used to output values. The symbolic I/O field is used to input values. The symbolic I/O field is used for the input and output of values. 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.
760
See also
Device-Specific Nature of the Objects (Page 734) Graphic I/O field (Page 742)
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>.
761
See also
Device-Specific Nature of the Objects (Page 734)
9.1.9
9.1.9.1
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 763)
762
9.1.9.2
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.
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".
WinCC Basic V11.0 SP2 System Manual, 04/2012,
763
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 762)
9.1.9.3
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.
Result
The operator goes to the specified "Screen_2" with function key "F2" in Runtime.
764
9.2
9.2.1
9.2.1.1
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.
Internal tags do not have a process link and only convey values within the WinCC.
Tags in WinCC
For external tags, the properties of the tag are used to define the connection that the WinCC uses to communicate with the automation system and form of data exchange. Tags that are not supplied with values by the process - the internal tags - are not connected to the automation system. In the tag's "Connection" property, this is identified by the "Internal tag" entry. You can create tags in different tag tables for greater clarity. You then directly access the individual tag tables in the "HMI tags" node in the project tree. The tags from all tag tables can be displayed with the help of the table "Show all tags".
765
See also
Overview of HMI tag tables (Page 766) Internal tags (Page 770) External tags (Page 767) Addressing external tags (Page 768) Creating external tags (Page 771) Basics on arrays (Page 798) Cycle basics (Page 801)
9.2.1.2
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.
766
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.
See also
Basics of tags (Page 765)
9.2.1.3
External tags
Introduction
External tags allow communication (exchange of data) between the components of an automation system, such as between the HMI device and the PLC.
Principle
An external tag is the image of a defined memory location in the PLC. You have read and write access to this storage location from both the HMI device and from the PLC. Since external tags are the image of a storage location in the PLC, the applicable data types depend on the PLC which is connected to the HMI device. In STEP 7, if you write a PLC control program, the PLC tags created in the control program will be added to the PLC tag table. If you want to connect an external tag to a PLC tag, access the PLC tags directly via the PLC tag table and connect them to the external tag.
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.
767
See also
Addressing external tags (Page 768) Basics of communication (Page 1019) Basics of tags (Page 765)
9.2.1.4
Introduction
The options for addressing external tags depend on the type of connection between WinCC and the PLC in question. A distinction must be made between the following connection types: Integrated connection Connections of devices which are within a project and were created with "Devices & Networks" editor are referred to as integrated connections. Non-integrated connection Connections of devices which were created with the "Connections" editor are referred to as non-integrated connections. It is not necessary that all of the devices be within a single project. The connection type can also be recognized by its symbol.
Integrated connection Non-integrated connection
You can find additional details on this in the section "Basics of communication (Page 1019)".
768
769
S7 1200
Yes
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.
See also
External tags (Page 767) Basics of tags (Page 765) Basics of communication (Page 1019)
9.2.1.5
Internal tags
Introduction
Internal tags do not have any connection to the PLC.
770
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:
HMI data type Array Bool DateTime DInt Int LReal Real SInt UDInt UInt USInt WString Data format One-dimensional array Binary tag Date/time format Signed 32-bit value Signed 16-bit value Floating-point number 64-bit IEEE 754 Floating-point number 32-bit IEEE 754 Signed 8-bit value Unsigned 32-bit value Unsigned 16-bit value Unsigned 8-bit value Text tag, 16-bit character set
See also
Basics of tags (Page 765)
9.2.2
9.2.2.1
771
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 is opened. 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. 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 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.
772
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. by clicking 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.
See also
Creating internal tags (Page 774) Creating multiple tags (Page 775) Editing a Tag (Page 776) Tag limits (Page 781) Basics of tags (Page 765) Addressing external tags (Page 768)
773
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 is opened. Alternatively, create a new tag table and then open it. 2. If the Inspector window is not open, select the "Inspector window" option in the "View" menu. 3. 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. 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. 5. Select "Internal tag" as the connection in the "Connection" field. 6. Select the required data type in the "Data type" field. 7. 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. 8. 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. You can also create new tags alternatively directly at the application point, e.g. on an I/O field. button in the object list. You can then configure the new tag in by clicking the 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.
774
See also
Creating external tags (Page 771)
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.
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.
775
See also
Creating external tags (Page 771)
9.2.2.2
Editing 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.
776
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.
See also
Changing the tag configuration (Page 777) Configuring multiple tags simultaneously (Page 778) Using multiple tags simultaneously in a screen (Page 778) Reconnecting a tag (Page 780) Creating external tags (Page 771) Importing and exporting tags (Page 1325)
777
See also
Editing a Tag (Page 776)
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. 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 776)
778
Requirement
Several tags are set up. A screen is open.
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.
779
See also
Editing a Tag (Page 776)
Requirement
You have created an HMI tag. The tag table is open. A PLC tag with the absolute address from the PLC is present.
Procedure
Proceed as follows to reconnect tags: 1. Select the row with the tag in the tag table. 2. Open the shortcut menu and select the menu command "Reconnect PLC tag". The system looks for a PLC tag whose absolute address and data type match the settings for the HMI tag. If a matching PLC tag is found, the tag connection is established immediately.
Result
The PLC tag is connected to the HMI tag.
780
See also
Editing a Tag (Page 776)
Configuring tags
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.
781
See also
Applying linear scaling to a tag (Page 787) Defining the start value of a tag (Page 784) Defining the acquisition cycle for a tag (Page 791) Defining Limits for a Tag (Page 782) Start value of a tag (Page 783) Updating the tag value in Runtime (Page 784) Linear scaling of a tag (Page 785) Connecting a tag to another PLC (Page 787) Indirect addressing of tags (Page 788) Addressing tags indirectly (Page 789) Using tags to trigger functions (Page 790) Address multiplexing (Page 792) Configuring address multiplexing with absolute addressing (Page 793) Configuring address multiplexing with symbolic addressing (Page 795) Creating external tags (Page 771)
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 button. Enter a number in of the limits as a constant value, select "Constant" using the 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.
782
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.
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 781)
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.
783
See also
Defining the start value of a tag (Page 784) Tag limits (Page 781)
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 781) Start value of a tag (Page 783)
784
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: 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."
See also
Tag limits (Page 781)
785
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.
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 781)
786
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 781)
787
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 781)
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.
788
See also
Tag limits (Page 781)
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.
789
See also
Tag limits (Page 781)
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 781)
790
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 781)
791
792
See also
Tag limits (Page 781)
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".
793
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.
794
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 781)
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.
795
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.
796
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.
797
See also
Tag limits (Page 781)
9.2.3
9.2.3.1 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.
798
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 800) Examples of arrays (Page 801) Basics of tags (Page 765)
799
9.2.3.2
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 3. Click in the Data type column and select the "Array" data type. 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.
800
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 798)
9.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 798)
9.2.4
9.2.4.1
Introduction
Cycles are used to control actions that regularly occur in runtime. Common applications are the acquisition cycle and the update cycle.
801
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 765)
9.2.5
9.2.5.1
Displaying tags
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.
802
9.2.5.2
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.
803
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.
9.3
9.3.1
9.3.1.1
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 Date Alarm text Boiler pressure above high limit. Status Incoming Outgoing Alarm class Warning: Color Red
804
9.3.1.2
Alarm types
805
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.
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.
806
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".
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.
9.3.1.3
Alarm states
Introduction
An alarm assumes various alarm states in Runtime.
807
Description
Every alarm has an alarm status. The alarm states are made up of the following events: Incoming (I) The condition for triggering an alarm is satisfied. The alarm is displayed, such as "Boiler pressure too high." Outgoing (O) The condition for triggering an alarm is no longer satisfied. The alarm is no longer displayed as the boiler was vented. Acknowledge (A) The operator acknowledges the alarm.
IA IAO
Each occurrence of these states can be displayed and logged on the HMI device and a protocol printed. Note You can configure the display text for the alarm status.
808
9.3.1.4
Alarm classes
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.
See also
Creating alarm classes (Page 815)
809
See also
Creating alarm classes (Page 815)
9.3.1.5
Acknowledgment
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.
810
811
9.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.
Display in Runtime
In Runtime, the "Alarm group" column displays the number of the alarm group to which the alarm belongs.
812
9.3.1.7
Alarm number
9.3.2
9.3.2.1 Overview
You configure the components of alarms in WinCC. The following table shows the basic components of alarms:
Alarm Alarm class number Warni 1 ng Syste m 110001 Time Date of day 11:09 :14 11:25 :58 Alarm status Alarm text Alarm Tooltip group Maximum speed reached Switch to "Online" mode 2 0 This alarm is ... This alarm is ... speed_1 PLCVariable_1 Trigger tag Limit value 27
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.
813
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.
814
9.3.2.2
Configuring alarms
815
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.
816
Requirement
You have created a project. The "HMI alarms" editor is open. The Inspector window is open.
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.
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.
817
818
See also
Configuring loop-in alarm (Page 823)
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.
819
4. Configure the tag that triggers the alarm under "Properties > Properties > Trigger > Settings". Do not use trigger tags for anything else.
820
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.
See also
Configuring loop-in alarm (Page 823)
821
Requirements
The "HMI alarms" editor is open. The alarm is selected.
822
Procedure
To format an alarm text, proceed as follows: 1. Select the alarm to edit. 2. In the Inspector window, select the characters to format under "Properties > Properties > General > Alarm text". 3. Select the formatting from the shortcut menu, e.g. "Underscored" or "Uppercase".
Result
The selected characters are displayed in Runtime with the selected formatting.
Result
The selected characters are displayed in unformatted notation in Runtime.
Requirements
The screen called by the Loop-In-Alarm has been created. The "HMI alarms" editor is open.
823
Procedure
To configure a Loop-In-Alarm for an alarm, proceed as follows: 1. Click the tab that contains the alarm for which you want to configure the Loop-In-Alarm. 2. Select the alarm. 3. In the Inspector window, select "Properties > Events > Loop-In-Alarm". 4. Select the "ActivateScreen" system function. 5. Select the screen called by the Loop-In-Alarm as parameter.
Note To configure the Loop-In-Alarm for an alarm view with an "alarm line" format, use the following system functions: "EditAlarm" for HMI devices with keys "AlarmViewEditAlarm" for HMI devices without keys The system functions trigger the "Loop-In-Alarm" event. The alarm line has no buttons.
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 819) Configuring discrete alarms (Page 817)
824
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. Use the data types "Int" or "Word" to select a PLC tag. 3. Select the tag at the top of the work area. 4. Click on "<Add>" in the table on the "Discrete alarms" tab at the bottom of the work area. A new discrete alarm is created for the tag. If you have selected the incorrect data type, the tag will be marked in the discrete alarm. 5. Configure the discrete alarm in the Inspector window: Enter the alarm text under "Properties > Properties > General > Alarm text". You can also insert output fields into the alarm text. Select an alarm class. Select the trigger bit of the tag that triggers the discrete alarm under "Properties > Trigger". 6. You can create additional discrete alarms to monitor the tags. Note A tag is monitored using only one alarm type. You should therefore create either analog alarms or discrete alarms for a tag.
825
Result
The configured discrete alarms are created in the "HMI tags" editor and displayed in the "HMI alarms" and "HMI tags" editors.
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.
826
Result
The configured analog alarms are created in the "HMI tags" editor and displayed in the "HMI alarms" and "HMI tags" editors.
9.3.2.3
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.
827
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.
828
Requirement
A screen is open in the "Screen" editor. The "Tools" task card is open.
829
3. In the table, activate the alarm classes to be displayed in the alarm view.
830
Result
Alarms of various alarm classes are output in the alarm view during runtime.
See also
Alarm view (Page 748)
831
Requirement
The "Global Screen" editor is open. The "Tools" task card is displayed. The Inspector window is open.
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 751)
832
Requirement
The "Global Screen" editor is open. The "Tools" task card is open. The Inspector window is open.
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.
833
See also
Alarm indicator (Page 753)
9.3.2.4
Acknowledging alarms
Requirement
The "HMI alarms" editor is open. The required alarm class has been created. The required alarm has been created.
Result
The alarm will not disappear in Runtime until it is acknowledged by the operator.
834
Requirement
The "HMI alarms" editor is open. The required alarm class has been created. The required alarm has been created. An alarm view and a button are created in the "Screens" editor.
835
836
Result
If the operator acknowledges the alarm in Runtime, the operating step is forwarded to the PLC.
9.3.3
9.3.3.1 Alarms
Alarms indicate events and states on the HMI device which have occurred in the system, in the process or on the HMI device itself. A status is reported when it is received. An alarm could trigger one of the following alarm events: Incoming Outgoing Acknowledge Loop-in-alarm The configuration engineer defines which alarms must be acknowledged by the user. An alarm may contain the following information: Date Time Alarm text Location of fault Status Alarm class Alarm number Alarm group
Alarm classes
Alarms are assigned to various alarm classes. "Warnings" Alarms of this class usually indicate states of a plant such as "Motor switched on". Alarms in this class do not require acknowledgment. "Errors" Alarms in this class must always be acknowledged. Error alarms normally indicate critical errors within the plant such as "Motor temperature too high".
837
Alarm buffer
Alarm events are saved to an internal buffer. The size of this alarm buffer depends on the HMI device type.
Alarm view
The alarm view shows selected alarms or alarm events from the alarm buffer. Whether alarm events have to be acknowledged or not is specified in your configuration.
Alarm window
An alarm window shows all pending alarms or alarms awaiting acknowledgement of a particular alarm class. The alarm window is displayed as soon as a new alarm occurs. You can configure the order in which the alarms are displayed. You can choose to display the alarms in ascending or descending order of their occurrence. The alarm window can also be set to indicate the exact location of the fault, including the date and time of the alarm event. By means of configuration, the display can be filtered in such a way that only alarms that contain a specific character string will be shown.
Alarm indicator
The alarm indicator is a graphic icon that is displayed on the screen when an alarm of the specified alarm class is activated. The alarm indicator can have one of two states: Flashing: At least one unacknowledged alarm is pending. Static: The alarms are acknowledged but at least one of them has not gone out yet. The displayed number indicates the number of queued alarms.
838
9.3.3.2 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.
Layout
Depending on the configuration, in the alarm view different columns with information regarding an alarm or an alarm event are displayed. To differentiate between the different alarm classes, the first column in the alarm view contains an icon:
Symbol ! empty depends on the configuration $ Alarm class "Errors" "Warnings" Custom alarm classes "System"
839
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 Displaying a tooltip for an alarm Displays the full text of the selected alarm in a separate window, namely the alarm text window In the alarm text window, you can view alarm texts that exceed the space available in the Alarm view. Close the alarm text window with the the button. Scrolls one alarm up. Scrolls one page up in the alarm view. Scrolls one page down in the alarm view. Scrolls one alarm down.
9.3.3.3 Application
The alarm indicator is displayed if alarms of the specified alarm class are pending or require acknowledgment.
840
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.
9.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
WinCC Basic V11.0 SP2 System Manual, 04/2012,
button.
841
Result
The alarm status changes to "Acknowledged". If the condition for triggering an alarm no longer applies, the alarm status also changes to "Outgoing", and it is no longer displayed on the HMI device.
9.3.4
9.3.4.1
Reference
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.
System function EditAlarm ClearAlarmBuffer ClearAlarmBufferProtoolLegacy Effect Triggers the Loop-In-Alarm event for all selected alarms. Deletes alarms from the alarm buffer on the HMI device. Function such as "ClearAlarmBuffer". This system function has been retained to ensure compatibility and uses the old ProTool numbering. Triggers the event Loop-In-Alarm for all alarms selected in the specified alarm view. Acknowledges the alarms that are selected in the specified alarm view. Displays the configured tooltip for the alarm selected in the specified alarm view. Acknowledges all selected alarms. Hides or shows the alarm window on the HMI device.
9.3.4.2
System events
842
Note System events are output in an alarm view. System events are output in the language currently set on your HMI device.
30000 - Alarms errors when using system functions Meaning of the system events
All system events that can be displayed are listed below. The system events are divided into different ranges.
Table 9-2 Number 30010 30011 30000 - Alarms errors when using system functions Effect/causes The tag could not accept the function result, e.g. when it has exceeded the value range. A system function could not be executed because the function was assigned an invalid value or type in the parameter. A system function could not be executed because the function was assigned an invalid value or type in the parameter. Remedy Check the tag types of the system function parameters. Check the parameter value and tag type of the invalid parameter. If a tag is used as a parameter, check its value. Check the parameter value and tag type of the invalid parameter. If a tag is used as a parameter, check its value.
30012
843
40011
50001
--
70011
Check the time which is to be set. The system time could not be modified. 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.
844
70013
70014
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.
70025
70026
--
70027
845
70029
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 function with the parameters configured for the PLCs are faulty. The connection to the new PLC was not established. and correct them as necessary. The PLC configured in the system function is not an Compare the S7 PLC name parameter configured for the system function with the parameters configured for S7 PLC. The connection to the new PLC was not established. the PLC and correct them as necessary. The object configured with this number in the tab sequence is not available in the selected screen. The screen changes but the focus is set to the first object. Check the number of the tab sequence and correct it if necessary.
70031
70032
70033
Check the network connection to the SMTP server and An e-mail cannot be sent because a TCP/IP re-establish it if necessary. connection to the SMTP server no longer exists. This system event is generated only at the first attempt. All subsequent unsuccessful attempts to send an e-mail will no longer generate a system event. The event is regenerated when an e-mail has been successfully sent in the meantime. The central e-mail component in WinCC Runtime attempts to connect to the SMTP server at cyclic intervals (1 minute) in order to transmit the remaining e-mails. Following a disruption, the TCP/IP connection to the SMTP server could be re-established. The queued e-mails are then sent. 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. An e-mail cannot be sent for unknown reasons. The contents of the e-mail are lost. 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. The syntax of the e-mail address is incorrect or contains illegal characters. The contents of the e-mail are discarded. The syntax of the e-mail address is incorrect or contains illegal characters. --
70034
70036
Configure an SMTP server: In the WinCC Engineering System using "Device settings > Device settings" In the Windows CE operating system using "Control Panel > Internet Settings > E-mail > SMTP Server" Check the e-mail parameters (recipient etc.). 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. Check the e-mail address of the recipient.
70037 70038
70039
70040
--
846
70042
110003
The operating mode of the specified PLC was changed by the "SetConnectionMode" system function. The "offline" operating mode is now set. The operating mode of the specified PLC was changed by the "SetConnectionMode" system function. The "online" operating mode is now set. 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. The content of the "project ID" area pointer does not match the project ID configured in WinCC. The WinCC Runtime is therefore terminated.
110004
--
110005
Switch the complete system to "online" mode and repeat execution of the system function.
110006
Check: the project ID entered on the PLC. the project ID entered in WinCC.
847
140004
No tag update or write operations are executed due to an incorrect access point, or incorrect module configuration.
140005
No tag update or write operations are executed due to an incorrect HMI device address (possibly too high).
140006
No tag update or write operations are executed due to an incorrect baud rate setting.
848
140008
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 140010
To reinstall the module, open the Control Panel and select "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. Check the connection and whether the communication partner is switched on. Restart the HMI device. Or: Start WinCC Runtime and then start your other applications.
140011 140012
No tag updates or write operations because communication is down. There is an initialization problem (e.g. if WinCC Runtime was closed in Task Manager). Or: Another application (e.g.STEP7) with different bus parameters is active and the driver cannot be started with the new bus parameters (baud rate, for example). The MPI cable is disconnected and, therefore, there is no power supply. The configured bus address is in use by another application. Incorrect baud rate Or: Incorrect bus parameters (e.g. HSA) Or: OP address > HSA or: Incorrect interrupt vector (interrupt not registered by the driver)
Check the connections. Change the HMI device address in the PLC configuration. Correct the parameters.
849
850
Select system function "SetOnline" to enable communication. Check the configuration. Check the configuration. Check the configuration. Set online mode or reconnect to the PLC.
190008
190011
851
190101
--
190102
--
852
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. Coordination is not carried out at the moment because the address format of the area pointer does not match the internal storage format. Coordination can be executed again because the last error state is eliminated (return to normal operation). The coordination may not be executed. No more data is read or written. Possible causes: The cable is defective. The PLC does not respond, is defective, etc. System overload Internal error
200003
--
200004 200005
-Ensure that the cable is plugged in and the PLC is operational. Restart the system if the system alarm persists.
210001
Change the address, or set up the address in a PLC area at which read/write access is possible. Internal error
210002
210003
--
-Check the PLC program. Check the parameters of the control job. Recompile the configuration data.
853
220000 - WinCC communication driver alarms 220000 - WinCC communication driver alarms
Number 220001 Effect/causes The tag is not downloaded because write access to data type Bool/Bit is not supported by the sublevel communication driver/HMI device. The tag is not downloaded because write access to data type Byte is not supported by the sublevel communication driver/HMI device. The communication driver cannot be loaded as it is possibly not installed. Communication is down and no update data is transferred because the cable is not connected or defective etc. Communication is up. The connection between the specified PLC and the specified port is active. The connection to the specified PLC is interrupted at the specified port. Remedy Change the configuration.
220002
220003 220004
--Check the following: Is the cable plugged in? Is the PLC OK? Is the right port being used? Is your configuration OK (port parameters, protocol settings, PLC address)? Restart the system if the system event persists.
220008
The communication driver cannot access or open the specified port. This port might be in use by another application, or a port that does not exist on the target device is being used. No communication with the PLC.
Close all applications that access the port and restart the computer. Use another port that exists in the system.
854
230003
Configure the screen and check the selection function. Observe the range of values for the tag when entering a value. Navigate to another page.
230005
230100
230200
230201
--
855
230302
Check the configured server address. Check whether the DNS service is available on the network. Check the configured server address. Check whether the remote server is running on the target computer. Use a compatible remote server.
230303
230304
230305
856
230307
260001
Log on to the system as a user with sufficient authorization. --Select another user name because user names have to be unique in the user management. Enter a shorter user name. Use a shorter or longer password. Enter a logon timeout value between 0 and 60 minutes.
260008
--
260009
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.
857
260014
You can log on to the system with your correct password. Only an administrator can change the assignment to a group. Enter a password that contains at least one number. Enter a password that contains at least one special character. 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. Log in again and choose a different password. Check the password rules on the SIMATIC Logon Server.
858
Try again. If necessary, check the password data on the SIMATIC Logon Server.
270001
270002
859
270004
If the problems persist at the next restart, contact Customer Support (delete Flash). If the problems persist at the next restart, contact Customer Support (delete Flash). 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. Update the operating system and download your project again to the HMI device.
270005 270006
270007
290001
290002
290003
Check the configuration to see whether the tag addresses have been set up in the PLC.
290004
290005
860
290008
Remove the specified recipe tag in the specified recipe from the project.
290010
A recipe of the specified number does not exist. Check the source for the number (constant or tag value). 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
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. Check back to verify that the download of records from the HMI device to the PLC was completed. Check back to indicate that the download of data records from the HMI device to the PLC was canceled due to an error.
--
290021
--
290022
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. Check back to verify that the download of data records from the PLC to the HMI device was completed.
--
290024
---
861
290027
Check the connection to the PLC. Unable to connect to the PLC at present. As a result, the data record cannot be read or written. Possible causes: No hardware connection to the PLC (no cable plugged in, cable is defect), or the PLC is switched off. This alarm is output after you selected screen which contains a recipe view in which a data record is already selected. While saving, it was detected that a data record with the specified number already exists. During the export of data records, a file with the specified name was found. Confirmation prompt before deleting data records. 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. A data record or file cannot be saved because the storage location is out of sufficient space. An attempt was made to execute several recipe actions simultaneously. The last action is not executed. The database for the recipe was corrupted and will be deleted. A check back indicates that the export of data records was started. A check back indicates successful completion of the export of data records. A check back indicates that the export of data records was canceled due to an error. A check back indicates that the import of records was started. A check back indicates successful completion of the import of data records. Reload the data record from the storage location, or retain the current values. Overwrite the data record, or cancel the action. Overwrite the file, or cancel the process. -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. Delete files no longer required. Retrigger the action after a short waiting time.
290030
290041 290042
Confirmation prompt before saving data records. ----Ensure that the structure of the data records at the storage location and the current recipe structure on the HMI device are identical. ---
290053 290054
862
290056
290057
--
290058
--
290063
-----Check the source of the data record number, or the data record name (constant, or tag value). 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.
863
Overwrite the record, change the record number or cancel the action. Select a different data record name. -Download the project to the device again, including the recipes (the corresponding check box in the download dialog must be check marked).
9.4
9.4.1
9.4.1.1
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.
864
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.
865
9.4.1.2
9.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: In a soft drinks production plant, a recipe is needed for different flavors. Drink variants include fruit juice drink, juice and nectar.
866
Recipe
The recipe contains all the recipe data records for the different drink variants.
5 30 23 80
15 35 20 70
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.
9.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.
867
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.
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.
9.4.1.5
868
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.
9.4.1.6 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.
869
Coordinated transfer
In the case of coordinated transfer, both the PLC and the HMI device set the status bits in the shared data compartment. Coordinated transfer of recipe data records can be a useful solution in the following cases: The PLC is the "active partner" for the transfer of recipe data records. The PLC evaluates information about the recipe number and name, as well as the recipe data record number and name. The transfer of recipe data records is started by the following PLC jobs: "Set_data_record_in_PLC" "Get_data_record_from_PLC"
9.4.2
9.4.2.1
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.
870
You can then configure the selected recipe, the recipe element or the recipe data record in the Inspector window. You will find further notes on configuring the components of a recipe under "Configuring Recipes".
Recipe settings
The following settings are available for recipes:
Setting Name of the recipe Display name Description This is a unique identification for the recipe within the HMI device. 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". This is a unique identification for the recipe within the HMI device. Information about the recipe. The date and time of the last change to the recipe is set by default. Defines the storage location for recipes. The recipes are stored as a file. The recipe data records are limited to a predetermined number by default. Maximum number of data records in a recipe in Runtime. The number is limited by the recipe memory of the HMI device.
Recipe number Version Path Size type [fixed] Number of data records [fixed]
871
NOTICE Path The storage location depends on the storage media available on the HMI device. Basic Panels and OP77A, TP177A (Portrait) These HMI devices have no external memory. Recipes are always saved in the internal Flash memory. The "Path" setting is therefore not available.
Display name
Tooltip
872
9.4.3
9.4.3.1
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.
873
Display of values
NOTICE Processed recipe data record is changed in the background Only applies for Basic Panels: if an operator has changed a recipe data record and a PLC job wants to read or write any recipe data record of this recipe, the PLC job is stopped and a system alarm is output. On the other hand, the changed value is displayed immediately if only the PLC job and no operator has changed recipe data. Does not apply for Basic Panels: If an operator has changed a recipe data record and a PLC job has changed the values of the recipe data record concerned, the recipe view is not updated automatically. To update the recipe view, reselect the respective recipe data record.
See also
Recipe view (Page 756)
9.4.3.2
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.
874
9.4.4
9.4.4.1
Configuring recipes
General configuration procedure
Carry out the following configuration steps when you create a new recipe:
Step 1 2 3 Description Define the structure of the recipe. Create tags according to the recipe structure. Assign process names to these tags. Create the recipe.
875
NOTICE Basic Panels and OP77A, TP177A (Portrait) The selection of the storage location is not available for these devices. The recipes are always saved in the internal Flash memory. Recipe tags cannot be used outside a recipe, e.g. not in I/O fields, not in alarms as trigger tags, not in systems functions as parameters, etc. NOTICE Restrictions recipe view and recipe image Only the simple recipe view is available in Basic Panels and OP77A, TP177A. Recipe images are not available in Basic Panels and OP73, OP77A, TP177A (Portrait).
9.4.4.2
Requirement
The tags for the recipe have been created. The "Recipes" editor is open.
876
Create recipe
Create a recipe as follows: 1. Click "Add" in the first free row of the table in the "Recipes" editor. The new recipe is created and displayed on a line.
2. Enter a descriptive name for the recipe under "Name" in the "General" area. This name identifies the recipe unambiguously within the project. 3. Select "Display name" to enter the language-specific name to be displayed in runtime. 4. Select a recipe number in "Number". The number identifies the recipe unambiguously within the HMI device. The recipe is automatically assigned a version that indicates the date and time of the last change. As an alternative, you can enter specific information relating to the recipe. 5. Specify the storage location for recipe data records in "Data medium". The options offered depend on the specific HMI device used. NOTICE Basic Panels and OP77A, TP177A (Portrait) The selection of the storage location is not available for these devices. The recipes are always saved in the internal Flash memory. Recipe tags cannot be used outside a recipe, e.g. not in I/O fields, not in alarms as trigger tags, not in systems functions as parameters, etc. 6. Enter a tooltip that is shown to the operator in runtime.
877
NOTICE Basic Panels and OP77A, TP177A (Portrait) Because the recipe tags cannot be additionally used in I/O fields in screens for Basic Panels, the "Synchronize recipe view and recipe tags" is not available; you will also not be able to use the "Manual transfer of individual modified values (teach-in mode)" option. 8. Deactivate "Manual transfer of individual modified values (teach-in mode)" to specify that the recipe tags are automatically transferred to the PLC when editing the I/O fields. 9. Activate "Coordinated transfer of data records" to monitor the transfer of recipe data in Runtime using area pointers. 10.Select the appropriate connection to the PLC for coordinated transfer under "Synchronize with".
878
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.
879
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.
880
Result
The complete recipe is configured.
Requirement
You have created at least one recipe. The "Recipes" editor is open.
881
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.
882
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.
883
9.4.4.3
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".
884
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".
885
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.
886
9.4.5
9.4.5.1
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
887
888
Function The displayed values of the selected data record are transferred from the HMI device to the PLC. The recipe values from the PLC are displayed in the recipe view of the HMI device.
889
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.
890
Result
The recipe data record is stored under the new name.
Result
The modified values are applied to the recipe data record.
Result
The recipe data record is deleted.
891
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.
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.
892
9.4.6
9.4.6.1 Task
Example
Example of creating a recipe
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 Liter water Liter concentrate Kilo sugar Gram flavoring PLC connection Yes Yes Yes Yes Address DB 120, DBW 0 DB 120, DBW 4 DB 120, DBW 8 DB 120, DBW 12 Type Integer Integer Integer Integer
893
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.
894
9.5
9.5.1
Principle
The access protection controls access to data and functions in Runtime. This feature protects your applications against unauthorized operation. Safety-related operations are already limited to specific user groups when a project is being created. To this purpose you set up users and user groups that you equip with characteristic access rights, so-called authorizations. You then configure the authorizations required for operation of safety-related objects. Operators only have access, for example, to specific operator controls. Commissioners, for example, have unlimited access in Runtime.
Definition
You administer users, user groups and authorizations centrally in the user administration of WinCC. You transfer users and user groups together with the project to the HMI device. The users and passwords are managed on the HMI device in the User view.
Application example
You configure the "Service" authorization so that only service technicians have access to the configuration parameters. You assign the authorization to the "Service technician" user group. This allows all members of this group to set the protected configuration parameters. CAUTION Access protection does not protect against incorrect operations. It is your job to ensure that only authorized personnel with appropriate training will design, commission, operate and maintain plants and machines. Access protection is not suitable for defining work routines and monitoring their observance.
9.5.2
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 V11.0 SP2 System Manual, 04/2012,
895
Principle
To minimize the work required for management, authorizations are assigned via user groups and not directly to individual users. A user group assembles configured authorizations according to common jobs. For example, all permissions required for a service job are collected in a "Service technician" group. When you create a user who should be responsible for servicing, you simply assign him to the "Service technician" group. The user view enables user administration in Runtime. Use user view to create, delete and assign an authorization to users in Runtime. The user administration separates the administration of the users from the configuration of the authorizations. This ensures flexibility at the access protection. Defaults can be set for the user administration during the configuration phase in the Engineering System.
9.5.3
9.5.3.1
Basics
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.
896
Open
To open the "Users" tab, double-click "User administration" in the project window.
Work area
The users are managed in the work area: You create or delete users. You assign users to user groups. Note You can assign a user to exactly one user group.
Inspector window
When you select a user, you can change the password in the "General" group. Under "Automatic logoff" you can specify if the user is to be automatically logged off by the HMI device when there is no operator activity after the specified time.
9.5.3.2
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.
897
9.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.
9.5.3.4
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.
898
Principle
The work area consists of the "Groups" and "Authorizations" tables.
The "Groups" table shows the existing user groups. When you select a user group in this table, the "Active" column of the "Authorizations" table shows the authorizations which were assigned to the user group. The number of the user group and of the authorization is assigned by the user administration. The designations and descriptions are assigned by you. The number of predefined authorizations are fixed. Authorizations that you create can be freely edited. Ensure that the assigned numbers are unique.
9.5.3.5
Introduction
In the "Runtime settings > User administration" editor, configure the security settings for users and their passwords in runtime.
Open
Double-click the "Runtime settings" editor in the project window. Click "User administration."
Work area
You carry out the settings for the validity of passwords in runtime in the work area. You determine the complexity of the password, for example.
899
Effects in runtime
The security settings have the following effects in runtime, depending on the configuration. "Runtime services" group "Enable limit for logon attempts" check box selected The number entered in the "Number of incorrect logon attempts" box defines the number of logon attempts a user is allowed before being assigned to the "Unauthorized" group. "Enable limit for logon attempts" check box not selected The user has an unlimited number of logon attempts in runtime. "Number of incorrect logon attempts" field If you enter "4" in the field, for example, and the fourth logon attempt fails, the user is automatically assigned to the "Unauthorized" group. You can specify 1 to 9 attempts. "Logon only with password" check box When the check box is selected, the user will be authenticated by the password. The user name is not required. To match users to passwords, you cannot configure passwords more than once. "Hierarchy level" group "Group-specific rights for user administration" check box When this check box is selected, administrators only manage users whose group number is less than or equal to their own. For example, an administrator whose group number is 5 can only manage users whose group number is less than or equal to 5. This means that the administrator can assign users only to groups with a group number less than or equal to 5.
900
9.5.4
9.5.4.1 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."
901
9.5.4.2
Requirements
The "User groups" work area is open.
Procedure
1. Double-click "Add" in the "Authorizations" table. 2. Enter "Archive data" as the name of the authorization. 3. Enter a brief description as the "Comment."
902
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 903) Creating users (Page 904) Assigning a user to a user group (Page 905) Managing user groups (Page 907) User administration (Page 906)
Requirements
An "Archive data" authorization has been created. An "Operators" user group has been created. The "User groups" work area is open.
903
Procedure
1. Click on the "Operators" user group in the "Groups" table. The "Authorizations" table shows all authorizations. 2. Activate the "Archive data" authorization in the "Authorizations" table. NOTICE The "Archive data" authorization is only a designation and does not having any relation to the function "Archiving." You have to establish this relation yourself. To do so, configure the "StartArchiving" system functions at a control button and select "Archive data" as the "Authorization."
See also
Creating a user group (Page 902)
Requirements
The "Users" work area is open.
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.
904
See also
Creating a user group (Page 902)
Requirements
The user "Foreman" has been created. An "Operators" user group has been created. The "Users" work area is open.
Procedure
1. Click on the "Foreman" user in the "Users" table. The "Groups" table shows all user groups. 2. Activate the "Operators" user group in the "Groups" table.
See also
Creating a user group (Page 902)
905
Requirements
The "Users" work area is open.
906
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 902)
Requirements
The "User groups" work area is open.
907
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 902)
908
9.5.4.3
User view
When you configure a user view in the Engineering System, you administer users in this user view following download to the HMI device. CAUTION Changes in the user view are effective immediately in Runtime. Changes in runtime are not updated in the engineering system. When downloading the user administration to the HMI device, all changes in the user view are overwritten after a security prompt and based on the settings. Users who have a "User administration" authorization have unlimited access to the user view. This allows them to administer all users. Any other user has only limited access to the user view for self administration.
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.
909
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.
When no administrator is logged on, the user view shows only the logged-on user. Users can change their own passwords.
910
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.
Requirements
The user view is open. A "Group 2" user group has been created.
911
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.
Requirements
Runtime is enabled. The simple user view has been created.
WinCC Basic V11.0 SP2 System Manual, 04/2012,
912
913
Deleting a user
1. Click the name of the user to be deleted. 2. Delete the name. 3. Press the <Return> button. NOTICE The user can no longer log on in runtime.
914
Requirements
Under "Runtime settings > User administration" the "Enable limit for logon attempts" check box has been selected. The number 3 is entered in the field "Number of invalid login attempts". The "ShowLogonDialog" system function is configured on a button called "Logon".
Procedure
1. Click the "Logon" button. The logon dialog box is displayed.
2. Enter your user name as it was specified in the user administration, for example "Foreman". If someone has logged on before you, the name of the user will be displayed. 3. Enter the corresponding password. The input is concealed. 4. Click "OK" to close the dialog box.
915
9.5.4.4
Requirements
The "Operators" user group has been created. The "Archive data" authorization has been created. A screen has been created and opened. The screen contains a button.
Procedure
1. Click the button in the screen. 2. Click "Properties > Properties > Security" in the Inspector window. 3. Select "Archive data" as the "Authorization".
916
9.5.5
9.5.5.1
Reference
Objects with access protection
Introduction
The following objects can be configured with an authorization: Date/time field I/O field Graphic I/O field Recipe view Switch Button Symbolic I/O field
9.5.5.2 Principle
The predefined user groups and authorizations have the following numbers:
User group "Administrator group" "Users" Number 1 2
917
9.5.6
9.5.6.1 Task
Examples
Example: Configuring a button with logon dialog box
In the following example, you configure the function "ShowLogonDialog" for a button. A different user can then log on in runtime when the shift changes, for example. In the process the user previously logged on is logged off. Note In runtime the logon dialog box is not displayed by default until you access a protected object. Either no user is logged on or the logged-on user does not have the required authorization.
Requirements
A screen has been created. A button has been created in the screen.
Procedure
1. Click the button in the screen. 2. Click "Properties > Events > Release" in the Inspector window.
918
Result
If the user clicks on the button in runtime, the function "ShowLogonDialog" is called up. When the function "ShowLogonDialog" is called up, the logon dialog box is displayed. The user logs on with his user name and password.
9.5.6.2 Task
In the following example, you configure the function "TraceUserChange" to the event "User change".
Principle
The "TraceUserChange" function is called when a user logs on or off. When a function is called up, a system message with information about the corresponding user is output. This system message can be archived. When archiving, the system message is provided with a date stamp and time stamp. This ensures that you can track which user was logged on at the HMI device at which time and for how long.
Requirements
You have created an HMI device with Runtime Advanced. The Inspector window is open.
919
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.
9.5.6.3
Principle
Completely different groups of persons are involved in a plant or project. Each group of persons protects its respective data and functions against access by others. For this purpose, users are created and assigned to a user group. You can reproduce different views through user groups. Example: Organizational view: Commissioners, Operators, Shift I, Shift II Technological view: Axis control, Tool changers, Plant North, Plant South The following example orientates itself to the organizational view. Every user group has characteristic requirements regarding access protection: A user group has operating authorizations for specific application cases. A programmer changes, for example, recipe data records. In the example the users Miller, Group Smith and Foreman are created and assigned to different user groups. Ms. Miller works as a programmer in the engineering system. The Group Smith are commissioners. Mr. Foreman is an operator.
920
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 Roles Authorizations Changing recipe records X X x X X Changing system parameters Changing process parameters Managing
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.
921
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
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.
WinCC Basic V11.0 SP2 System Manual, 04/2012,
922
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. button to close the dialog box. 7. Select the "Recipes" screen and use the
8. Click "Properties > Properties > Security" in the Inspector window. 9. Select "Change recipe data records" as the "Authorization."
Result
Access to the "To Recipe view" button is protected. If, for example, the user "Smith" clicks the button in Runtime, the function "Recipe view" screen is called up. Prerequisite is that the user "Smith" has logged on correctly and has the required authorization. The "Recipes" screen contains a recipe view and other screen objects.
923
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
924
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
Procedure
1. Open the "Users" work area. 2. Double-click "Add" in the "Users" table.
925
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.
926
Result
9.6
9.6.1
9.6.1.1
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.
927
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.
928
9.6.1.2
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".
9.6.2
9.6.2.1
Introduction
When the configured event occurs, several system functions can be performed with the function list.
929
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.
9.6.2.2
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.
930
9.6.2.3
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.
931
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.
932
9.6.2.4
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.
933
9.6.2.5 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.
9.6.3
9.6.3.1
Example
Changing the operating mode on the HMI device with the current display
Scheduled task
In this example, you use the "SetDeviceMode" system function to switch between the "online" and "offline" modes on the HMI device. You also display the current set operating mode on the HMI device.
Requirements
A screen has been created.
Settings
For this example you require a HMI-tag and a text list with the following settings: HMI tag:
934
Text list:
Name ShowOperatingMode Contains Bit (0/1) Values 1: Operating mode: "Online" 0: Operating mode: "Offline"
Procedure
1. Create the "OperatingMode" HMI-tag 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".
935
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".
936
Result
When you change the operating mode with the buttons, the currently set operating mode on the HMI device is always shown.
9.6.4
9.6.4.1
Reference
Function list
Overview
KP300 Basic PN User-defined functions Logoff (Page 940) AdjustContrast (Page 940) ActivateScreen (Page 941) ActivateCleanScreen (Page 943) ActivatePreviousScreen (Page 944) UpdateTag (Page 945) Logon (Page 945) EditAlarm (Page 946) ScreenObjectCursorUp (Page 946) ScreenObjectPageDown (Page 948) ScreenObjectPageUp (Page 947) IncreaseFocusedValue (Page 948) IncreaseTag (Page 949) GoToHome (Page 950) GoToEnd (Page 950) InvertBit (Page 951) No Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes KTP400 Basic PN No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes KTP 600 Basic DP No Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes KTP 600 Basic PN No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
1)
KTP KTP TP 1500 1000 1000 Basic Basic DP Basic PN PN No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes No Yes No No Yes
937
RecipeViewGetDataRecordFromPLC Yes (Page 968) RecipeViewClearDataRecord (Page 969) RecipeViewMenu (Page 969) RecipeViewOpen (Page 970) RecipeViewSetDataRecordToPLC (Page 970) RecipeViewSaveDataRecord (Page 971) RecipeViewSaveAsDataRecord (Page 971) RecipeViewRenameDataRecord (Page 972) Yes Yes Yes Yes Yes Yes Yes
938
KTP400 Basic PN Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
KTP 600 Basic DP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
KTP 600 Basic PN Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
KTP KTP TP 1500 1000 1000 Basic Basic DP Basic PN PN Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No Yes No No Yes Yes Yes Yes No Yes Yes Yes No Yes Yes Yes No Yes Yes Yes Yes Yes
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
939
Parameters
--
See also
Device-based dependency of system functions (Page 937)
AdjustContrast Description
Changes the contrast of the display one level on the HMI device.
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.
940
See also
Device-based dependency of system functions (Page 937)
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.
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:
941
See also
Device-based dependency of system functions (Page 937) ActivateScreenByNumber (Page 942)
ActivateScreenByNumber Description
Performs a screen change to a screen depending on a tag value. The screen is identified by its screen number.
Parameters
Screen number Tag which contains the screen number of the destination screen. When a change from the root screen to the permanent window is desired, "0" or "-1" is specified: 0 = Change from root screen to permanent window -1 = Change from permanent window to root screen
942
See also
Device-based dependency of system functions (Page 937) ActivateScreen (Page 941)
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.
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.
943
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.
Parameters
--
See also
Device-based dependency of system functions (Page 937)
UpdateTag Description
Reads the current value of the tag with the specified Update ID from the PLC.
944
Parameters
Update ID Update ID assigned to the tag that will be updated.
Logon Description
Logs on the current user on the HMI device.
Parameters
Password The tag from which the password for the user logging on is read. If the user is logged on, the password in the tag is deleted. User name The tag from which the user name for the user logging on is read.
See also
Device-based dependency of system functions (Page 937)
EditAlarm Description
Triggers the "Edit" event for all selected alarms.
945
Parameters
--
See also
Device-based dependency of system functions (Page 937)
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
946
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
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
947
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: User view Alarm view Recipe view
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.
948
Parameters
Value The value which is added to the tag value.
IncreaseTag Description
Adds the given value to the value of the tags. X=X+a Note The system function uses the same tag as input and output values. When this system function is used to convert a value, help tags must be used. The auxiliary tags can be assigned to the tag value with the "SetTag" system function. If you configure the system function on the events of an alarm and the tag is not being used in the current screen, it is not ensured that the actual value of the tags is being used in the PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode.
Parameters
Tag The tag to which the given value is added. Value The value which is added.
949
See also
Device-based dependency of system functions (Page 937) SetTag (Page 984)
GoToHome Description
Executes the key function <Home> on the HMI device. This system function is used when the HMI device does not have this functionality by default. The system function can only be used for the following function keys.
Parameters
--
See also
Device-based dependency of system functions (Page 937)
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.
950
Parameters
--
See also
Device-based dependency of system functions (Page 937)
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).
Parameters
Tag The tag whose bit is set.
See also
Device-based dependency of system functions (Page 937) InvertBitInTag (Page 952)
951
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.
Parameters
Tag The tag in which the given bit is set. Bit The number of the bit that is set. When this system function is used in a user-defined function, the bits in a tag are counted from right to left. The counting begins with 0.
See also
Device-based dependency of system functions (Page 937) InvertBit (Page 951)
952
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.
Parameters
X The tag which is assigned the value calculated from the linear equation. Y The tag whose value is used for the calculation. b The value which is subtracted. a The value through which is divided.
See also
Device-based dependency of system functions (Page 937) LinearScaling (Page 962)
953
CalibrateTouchScreen Description
Calls a program for calibrating the touch screen. During the calibration process, there is a prompt to touch five positions on the screen display. Touch the screen display within 30 seconds, to confirm the calibration process. If the calibration is not completed within this time span, the calibration settings are discarded. The user prompt is in English. Use this system function the first time you start the HMI device.
Parameters
-Note The CalibrateTouchScreen system function cannot be simulated.
See also
Device-based dependency of system functions (Page 937)
TrendViewScrollForward Description
Scrolls forward one display width in the Trend view.
954
Parameters
Screen object Name of the trend view in which is scrolled forward. Note The HMI device TP 177A does not support this system function for the "screen" object.
TrendViewScrollBack Description
Scrolls back one display width to the left in the trend view.
Parameters
Screen object Name of the trend view in which is scrolled back. Note The HMI device TP 177A does not support this system function for the "screen" object.
TrendViewExtend Description
Reduces the time period which is displayed in the trend view.
955
Parameters
Screen object Name of the trend view in which the displayed time period is reduced. Note The HMI device TP 177A does not support this system function for the "screen" object.
TrendViewCompress Description
Increases the time period which is displayed in the trend view.
Parameters
Screen object Name of the trend view in which the displayed time period is increased. Note The HMI device TP 177A does not support this system function for the "screen" object.
956
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.
Parameters
Screen object Name of the trend view in which the read-line is moved forward. Note The HMI device TP 177A does not support this system function for the "screen" object.
See also
TrendViewSetRulerMode (Page 958)
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.
957
Parameters
Screen object Name of the trend view in which the read-line is moved backwards. Note The HMI device TP 177A does not support this system function for the "screen" object.
See also
TrendViewSetRulerMode (Page 958)
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.
958
Parameters
Screen object Name of the trend view in which the read-line is hidden or shown. Note The HMI device TP 177A does not support this system function for the "screen" object.
TrendViewStartStop Description
Stops the trend recording or continues the trend recording in the trend view.
Parameters
Screen object Name of the trend view in which the recording of the trend is started or stopped. Note The HMI device TP 177A does not support this system function for the "screen" object.
TrendViewBackToBeginning Description
Scrolls back to the beginning of the display range in the trend view.
959
Parameters
Screen object Name of the trend view in which you scroll to the beginning of the display range. Note The HMI device TP 177A does not support this system function for the "screen" object.
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.
Parameters
Tag The tag to which the user name is written.
See also
Device-based dependency of system functions (Page 937)
960
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.
Parameters
Tag The tag to which the number of the group is written.
See also
Device-based dependency of system functions (Page 937)
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.
961
Parameters
Tag The tag to which the password is written.
See also
Device-based dependency of system functions (Page 937)
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.
Parameters
Y The tag which is assigned the value calculated from the linear equation.
962
See also
Device-based dependency of system functions (Page 937) InvertLinearScaling (Page 953)
ClearAlarmBuffer Description
Deletes alarms from the alarm buffer on the HMI device. Note Alarms which have not yet been acknowledged are also deleted.
Parameters
Alarm class number Determines which alarms are to be deleted from the alarm buffer: 0 (hmiAll) = All alarms/events 1 (hmiAlarms) = Alarms of alarm class "Errors" 2 (hmiEvents) = Alarms of alarm class "Warnings" 3 (hmiSystem) = Alarms of alarm class "System"
963
See also
Device-based dependency of system functions (Page 937)
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.
Parameters
Alarm class number Alarm class number whose messages are to be deleted: -1 (hmiAllProtoolLegacy) = All alarms/events 0 (hmiAlarmsProtoolLegacy) = Alarms of alarm class "Errors" 1 (hmiEventsProtoolLegacy) = Alarms of alarm class "Warnings" 2 (hmiSystemProtoolLegacy) = Alarms of alarm class "System"
964
See also
Device-based dependency of system functions (Page 937) ClearAlarmBuffer (Page 963)
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.
965
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.
AlarmViewUpdate Description
Updates the enhanced alarm view.
Parameters
Screen object Name of the alarm view which is updated.
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.
966
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.
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.
967
Parameters
--
RecipeViewNewDataRecord Description
Creates a new data record in the given recipe view.
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.
968
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.
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.
969
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: 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.
Parameters
Screen object Name of the recipe view in which the command is triggered.
See also
RecipeViewBack (Page 973)
RecipeViewSetDataRecordToPLC Description
Transfers the recipe data record which is currently displayed in the recipe view to the PLC.
970
Parameters
Screen object Name of the recipe view from which the recipe data record is transferred to the connected PLC.
RecipeViewSaveDataRecord Description
Saves the recipe data record which is currently displayed in the recipe view.
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.
971
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. Only use this system function at a simple recipe view.
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.
Parameters
Screen object Name of the recipe view whose configured tooltip is displayed.
972
RecipeViewBack Description
Returns to the previous selection list in the given recipe view. The system function has no effect if the selection field for the recipe is displayed on the HMI device. Operation sequence of the selection lists in runtime: Recipe name Data record name RecipeDataRecordValues This system function is used when a simple recipe view has been configured. In the simple recipe view, only one selection list is displayed at a time on the HMI device. Use the "RecipeViewOpen" system function to display the recipe data record values or the next selection field.
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).
973
Parameters
Tag The BOOL type tag which is set to 0 (FALSE).
See also
Device-based dependency of system functions (Page 937) ResetBitInTag (Page 974)
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.
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.
974
See also
Device-based dependency of system functions (Page 937) ResetBit (Page 973)
PressButton Description
The system function can only be configured on the function keys of an HMI device and triggers the "Press key" event at the specified screen object. Use this system function when you want to operate a button in a screen with a function key of the HMI device, for example. Note The "PressButton" and "ReleaseButton" system functions must always be configured together. If you configure the "PressButton" system function on the "Press key" event for a function key, the "ReleaseButton" system function is configured on the "Release" event for the same function key.
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.
975
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.
976
Parameters
Source tag The tag includes the input bit pattern. Integer-type tags, e.g. "Byte", "Char", "Int", "UInt", "Long" and "ULong" are permitted. Example: The actual value 72 is set at the 16-bit integer source tag: 0000000001001000. Target tag The output bit pattern is saved in the tag. Integer type tags, e.g. "Byte", "Char", "Int", "UInt", "Long" and "ULong" are permitted. Example: The shifted input bit pattern is multiplied by the bit mask, with bit-by-bit logical AND operation: 0000000000001001. The resultant decimal value "8" is saved to the target tag. Please note the following: The source and target tags have the same number of bits. The number of bits to shift is less than the number of bits in the source tag and target tag. Bits to mask does not have more bits than the source tag and the target tag. Bits to shift Number of bits by which the input bit pattern is shifted right. A negative value shifts the input bit pattern to the left. Example: "Bits to shift" has the value "+3". The input bit pattern is shifted right by three bits when the system function is called: 0000000000001001. 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.
977
See also
Device-based dependency of system functions (Page 937)
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.
Parameters
-
See also
Device-based dependency of system functions (Page 937)
PageDown Description
Executes the key function <Pagedown> on the HMI device. This system function can only be used for function keys.
978
Parameters
-
See also
Device-based dependency of system functions (Page 937)
SetDeviceMode Description
Toggles the operating mode on the HMI device. The following types of operation are possible: "Online", "Offline" and "Load".
Parameters
Operating mode Determines the operating mode of the HMI device: 0 (hmiOnline) = Online: The connection to the PLC is established. 1 (hmiOffline) = Offline: The connection to the PLC is disconnected. 2 (hmiTransfer) = load: A project can be transferred from the configuration computer to the HMI device. Note If you use a PC as an HMI device, the runtime software will be exited when you change operating mode after "Load".
See also
Device-based dependency of system functions (Page 937) SetConnectionMode (Page 985)
979
SetBit Description
Sets the value of a "Bool" type tag to 1 (TRUE).
Parameters
Tag The BOOL type tag which is set to 1 (TRUE).
See also
Device-based dependency of system functions (Page 937)
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.
980
Parameters
Tag The tag in which a bit is set to 1 (TRUE). Bit The number of the bit that is set to 1 (TRUE). When this system function is used in a user-defined function, the bits in the specified tag will be counted from right to left independent of the PLC used. The counting begins with 0. Note The guaranteed update of the tags used with actual process values is absolutely conditional in terms of reliable functionality. You should therefore configure the tag in an I/O field or assign the system function to a screen object, such as a button. If you have configured a short event such as the activation of an alarm for the system function you can only access the actual process values by setting the tag for continuous reading.
See also
Device-based dependency of system functions (Page 937) SetBit (Page 980)
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
981
Parameters
Tag The tag in which a bit is temporarily set to 1 (TRUE). Use only tags of the type BOOL, as far as allowed by the PLC. Bit The number of the bit that is temporarily set to 1 (TRUE). Note The guaranteed update of the tags used with actual process values is absolutely conditional in terms of reliable functionality. You should therefore configure the tag in an IO field, or assign the function to a screen element such as a button. If you configured a short event such as the activation of an alarm for the function you can only access the actual process values by setting the tag for continuous reading.
See also
SetBit (Page 980)
982
SetColorBackgroundLighting Description
Defines the background lighting of the button. Note The configuration that was set at Switch off is reestablished when restarting the HMI device.
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
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.
983
Parameters
Language Determines which language is set on the HMI device. The following specifications are possible: -1 (hmiToggle) = Toggle: Changes to the next language. The sequence is determined during configuration in the "Project languages" editor. Number you have defined under "Languages and fonts" in the "Runtime Settings" editor. Changes to the language with the given number. Language you have defined under "Languages and fonts" in the "Runtime Settings" editor. Language abbreviation in accordance with the VBScript5 reference: This changes to the language corresponding to the specified language code, e.g. "de-DE" for German (Germany) or "en-US" for English (United States). An overview of the language abbreviations is available in the basic information of VBScript under the topic "Area diagram-ID (LCID) Diagram".
See also
Device-based dependency of system functions (Page 937)
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.
Parameters
Tag The tag to which the given value is assigned.
984
See also
Device-based dependency of system functions (Page 937) IncreaseTag (Page 949)
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.
Parameters
Mode Determines whether a connection to the PLC is established or disconnected: 0 (hmiOnline) = Online: Connection is established. 1 (hmiOffline) = Offline: Connection is disconnected. Connection The PLC to which the HMI device is connected. You specify the name of the PLC in the connection editor.
985
Application example
Two typical application examples for this system function are as follows: Test As long as no PLC is connected to the HMI device, no error messages will be output during the test on the HMI device. If the HMI device is connected to a PLC, the connection to the PLC can be established by pressing a key. Start up Several PLCs are to be configured for a system. At first, all PLCs except one are configured "Offline". After start up of the first PLC, the connection to each of the other PLCs is established by pressing a key. In this way, the other PLCs are started up one after another.
See also
Device-based dependency of system functions (Page 937) SetDeviceMode (Page 979)
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.
986
Parameters
System Key System Key, the behavior for which is to be simulated.
SimulateTag Description
Simulates the behavior of tags and dynamic objects such as text lists, without having the HMI device connected to a PLC. This system function is used, for example, to demonstrate the functionality of a project. NOTICE Only tags of the data type Integer can be used for simulation. Tags of the data types Integer and Double Integer, however, can be used with OP 73, OP 77A, TP 177A.
987
Parameters
Tag The tag whose value is changed. Cycle The factor by which the basic cycle of 200 milliseconds is multiplied. The cycle defines when the tag value is changed by the specified value. Possible cycles between 1 and 32767. Maximum value The maximum value that the tag can assume during simulation. The maximum value must be greater than the minimum value but less than / equal to 32767. Minimum value The minimum value that the tag can assume during simulation. The minimum value must be greater than the maximum value but less than / equal to -32768. Value The value by which the tag value is changed during each cycle. Possible values between -32768 and 32767. A positive value increases the tag value. When the maximum value is reached, the tag value is set to the minimum value after the next update cycle. A negative value reduces the tag value. When the minimum value is reached, the tag value is set to the maximum value after the next update cycle.
StopRuntime Description
Exits the runtime software and thereby the project running on the HMI device.
Parameters
Mode Determines whether the operating system is shut down after exiting runtime.
988
See also
Device-based dependency of system functions (Page 937)
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.
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. The system function can be configured: Input field Symbolic selection list Graphic selection list Slider bar
989
Parameters
Value The value which is subtracted from the tag value.
DecreaseTag Description
Subtracts the given value from the tag values. X=X-a Note The system function uses the same tag as input and output values. When this system function is used to convert a value, help tags must be used. The auxiliary tags are assigned to the tag value with the "SetTag" system function. If you configure the system function on the events of an alarm and the tag is not being used in the current screen, it is not ensured that the actual value of the tags is being used in the PLC. You can improve the situation by setting the "Cyclic continuous" acquisition mode.
Parameters
Tag The tag from which the given value is subtracted. Value The value which is subtracted.
990
See also
Device-based dependency of system functions (Page 937)
ChangeConnection Description
Disconnects the connection to the currently used PLC in use and establishes a connection to a PLC with another address. The newly connected PLC must belong to the same device class (S7-1200, S7-300, ...etc). With S7-1200, the use of the function is also only permitted for absolute addressing.
Note When changing to another address, ensure that the address is not already being used by another HMI device. The follows address types are supported: IP address MPI address The follows PLC types are supported: SIMATIC S7 1200 SIMATIC S7 300/400 SIMATIC S7-NC SIMOTION
Parameters
Connection Name of the connection that is disconnected. The name is set during configuration, for example, in the "Connections" editor.
991
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 937)
ShowLogonDialog Description
Opens a dialog on the HMI device with which the user can log on to the HMI device.
992
Parameters
--
ShowOperatorNotes Application
Displays the configured tooltip of the selected object. If the system function is configured on a function key, the tooltip for the screen object that currently has the focus is displayed. If a tooltip is configured for the screen itself, you can switch to this text by pressing <Enter> or by double-clicking on the help window. If the system function is configured on a button, only the tooltip for the current screen is displayed. If a tooltip is configured on the button itself, initially only the tooltip for the button is displayed. You can press <Enter> or double-click on the help window to switch to the tooltip for the current screen. Note No other screen object can be used while the help window is open. To use the screen object, close the help window.
993
Parameters
Display mode Determines whether the configured tooltip is hidden or shown: 0 (hmiOff) = Off: Configured tooltip is hidden 1 (hmiOn) = On: Configured tooltip is shown -1 (hmiToggle) = Toggle: Toggles between the two modes
See also
Device-based dependency of system functions (Page 937)
ShowAlarmWindow Description
Hides or shows the alarm window on the HMI device.
Parameters
Object name Name of the alarm view which is hidden or shown. Display mode Determines whether the alarm window is hidden or shown: 0 (hmiOff) = Off: Alarm view is hidden 1 (hmiOn) = On: Alarm view is shown -1 (hmiToggle) = Toggle: Toggles between the two modes
See also
Device-based dependency of system functions (Page 937)
994
Events
Introduction
The following table shows which events occur in which editor. Technical data subject to change.
Icon Editor Screens HMI alarms HMI tags Scheduler
Cleared (Page 1000) Enable (Page 1000) Adjust (Page 1001) Loaded (Page 1001) Execute (Page 1001) Selection changed (Page 1001) When dialog is opened (Page 1002) When dialog is closed (Page 1002) User change (Page 1002) Screen change (Page 1002) Disabling (Page 1003) Double-click (Page 1003) Pressing (Page 1004) On Finish Input (Page 1004) Press ESC twice (Page 1004) Outgoing (Page 1005) Incoming (Page 1005) Click (Page 1005) Loop-in alarm (Page 1005) Releasing (Page 1006) In the event of high limit violation (Page 1006) Alarm buffer overflow (Page 1006) In the event of low limit violation (Page 1007) Acknowledging (Page 1007)
-- ---------------------
--------------- - ----
-------------------- - --
995
Reach margin (Page 1007) Runtime stop (Page 1008) Press key (Page 1008) Release key (Page 1008) Overflow (Page 1009) Switch OFF (Page 1009) Switch ON (Page 1009) Low free storage space (Page 1009) Free space critically low (Page 1010) Value change (Page 1010) Time expired (Page 1010)
------------
------------
--------- --
- ----------
Cleared (Page 1000) Enable (Page 1000) Adjust (Page 1001) Loaded (Page 1001) Execute (Page 1001) Selection changed (Page 1001) When dialog is opened (Page 1002) When dialog is closed (Page 1002) User change (Page 1002) Screen change (Page 1002) Disabling (Page 1003)
------------
------------
------------
------------
------------
------------
996
Double-click (Page 1003) Pressing (Page 1004) On Finish Input (Page 1004) Press ESC twice (Page 1004) Outgoing (Page 1005) Incoming (Page 1005) Click (Page 1005) Loop-in alarm (Page 1005) Releasing (Page 1006) In the event of high limit violation (Page 1006) Alarm buffer overflow (Page 1006) In the event of low limit violation (Page 1007) Acknowledging (Page 1007) Reach margin (Page 1007) Runtime stop (Page 1008) Press key (Page 1008) Release key (Page 1008) Overflow (Page 1009) Switch OFF (Page 1009) Switch ON (Page 1009) Low free storage space (Page 1009) Free space critically low (Page 1010) Value change (Page 1010) Time expired (Page 1010)
-------------------------
-------------------------
-------------------------
-------------------------
-------------------------
-------------------------
Elements Introduction
The following table shows which events occur on which objects. Technical data subject to change.
Icon Object IO field Button Symbolic IO field Graphic IO field Date/time field Bar Switch
997
Cleared (Page 1000) Enable (Page 1000) Adjust (Page 1001) Loaded (Page 1001) Execute (Page 1001) Selection changed (Page 1001) When dialog is opened (Page 1002) When dialog is closed (Page 1002) User change (Page 1002) Screen change (Page 1002) Disabling (Page 1003) Double-click (Page 1003) Pressing (Page 1004) On Finish Input (Page 1004) Press ESC twice (Page 1004) Outgoing (Page 1005) Incoming (Page 1005) Click (Page 1005) Loop-in alarm (Page 1005) Releasing (Page 1006) Auto-Hotspot Alarm buffer overflow (Page 1006) In the event of low limit violation (Page 1007) Acknowledging (Page 1007) Reach margin (Page 1007) Runtime stop (Page 1008) Press key (Page 1008) Release key (Page 1008) Overflow (Page 1009) Switch OFF (Page 1009) Switch ON (Page 1009) Low free storage space (Page 1009) Free space critically low (Page 1010) Value change (Page 1010) Time expired (Page 1010)
- -------- -------------------------
- ------- -------------------------
- -------- -------------------------
------------------------------------
------------------------------------
See also
In the event of high limit violation (Page 1006)
998
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
Cleared (Page 1000) Enable (Page 1000) Adjust (Page 1001) Loaded (Page 1001) Execute (Page 1001) Selection changed (Page 1001) When dialog is opened (Page 1002) When dialog is closed (Page 1002) User change (Page 1002) Screen change (Page 1002) Disabling (Page 1003) Double-click (Page 1003) Pressing (Page 1004) On Finish Input (Page 1004) Press ESC twice (Page 1004) Outgoing (Page 1005) Incoming (Page 1005) Click (Page 1005) Loop-in alarm (Page 1005) Releasing (Page 1006) In the event of high limit violation (Page 1006) Alarm buffer overflow (Page 1006) In the event of low limit violation (Page 1007) Acknowledging (Page 1007) Reach margin (Page 1007) Runtime stop (Page 1008)
- -------- ----------------
----------------- --------
- -------- ----------------
- -------- ----------------
---------------------------
---------------------------
999
Press key (Page 1008) Release key (Page 1008) Overflow (Page 1009) Switch OFF (Page 1009) Switch ON (Page 1009) Low free storage space (Page 1009) Free space critically low (Page 1010) Value change (Page 1010) Time expired (Page 1010)
----------
----------
----------
----------
----------
----------
Enable Description
Occurs when the user selects a display or operating object using the configured tab sequence. Note Please note that the availability of the event is dependent upon the HMI device and object type. Note If the user e.g. clicks a button with the mouse, the "Click" event is triggered. Users wishing to trigger the "Enable" event must select the button using the tab key. The "Activate" event is only used to detect whether an object was selected. The event does not trigger a password prompt. For this reason, do not use the "Activate" event if you want to configure access protection on the function call of the object.
1000
Adjust Description
Occurs if the status of a display and operator control object changes. The status of an object changes if, for example, the user presses the key. Note Please note that the availability of the event depends on the HMI device and object type.
Loaded Description
Occurs 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.
1001
1002
Disabling Description
Occurs when the user takes the focus from a display and operating object. 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.
1003
Pressing 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.
1004
Outgoing Description
Occurs when an alarm is deactivated. Note Please note that the availability of the event depends on the HMI device and object type.
Incoming Description
Occurs when an alarm is triggered and displayed in the alarm view. Note Please note that the availability of the event depends on the HMI device and object type.
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.
1005
Releasing 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.
1006
Acknowledging 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.
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.
1007
1008
Overflow Description
Occurs when the configured size of the log is reached. You use the log type "Trigger event". Note Please note that the availability of the event is dependent upon the HMI device and object type.
Switch ON Description
Occurs when the user moves the display and operating object "Switch" to the ON position. Note Please note that the availability of the event is dependent upon the HMI device and object type.
1009
9.7
9.7.1
Definition
Planning tasks
Field of application of the Scheduler
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.
1010
Example of an application
The Scheduler is used to execute event-controlled tasks automatically. For example, you use a task to automate the following: Regular swap out of log data Printout of an alarm report when an alarm buffer overflow occurs Printout of a report at shift end Monitoring a tag Monitoring of a user change Note The availability of the listed examples is determined by the HMI device.
See also
Working with tasks and triggers (Page 1012) Example: Update user following change of user (Page 1017) Work area of the "Scheduler" editor (Page 1013)
1011
9.7.2
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 1010)
1012
9.7.3
9.7.3.1
Basics
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.
1013
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 1010) Planning tasks with event triggers (Page 1015) Triggers (Page 1014) Function list (Page 1014)
9.7.3.2
Function list
Function list
A trigger starts the function list. The function list is executed line-for-line. Each line contains a system function. You can configure exactly one function list for each task. Note The choice of configurable system functions in a function list depends on the selected trigger and the HMI device.
See also
Work area of the "Scheduler" editor (Page 1013)
9.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.
1014
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 1013)
9.7.3.4
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".
1015
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 1013)
1016
9.7.4
9.7.4.1 Task
Examples
Example: Update user following change of user
Configure an I/O field which displays the logged on user. Configure a task which updates the I/O field when the logged on user changes.
Requirements
A "CurrentUser" tag of the "String" type is created. A screen has been created and opened. An I/O field is created in the screen.
Procedure
1. Click on the "I/O field" object. 2. In the Inspector window, select "Properties > Events > General": Select "Character string" as the "Display format." Select "CurrentUser" as the "Variable." Select "Output" as the mode. 3. Change to the work area of the Scheduler. 4. Click "Add..." in the table of the task area. 5. Enter "CurrentUser" as the "Name". 6. Select "User change" as the "Trigger." 7. In the Inspector window, select "Properties > Events".
1017
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 1010)
1018
9.8
9.8.1
9.8.1.1
Communication
The data exchange between two devices is known as communication. The devices can be interconnected directly or via a network. The interconnected devices in communication are referred to as communication partners.
Data transferred between the communication partners may serve different purposes: Display processes Operate processes Output alarms Archive process values and alarms Document process values and alarms Administer process parameters and machine parameters
Communication partners
Communication between the following devices is described in more detail in this section: PLC The PLC controls a process by means of a user program. HMI device You use the HMI device to operate and monitor the process.
1019
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
9.8.1.2
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.
1020
Inserting devices
If you have created a project, you can add a device in the portal view or project view.
1021
Project view
1022
1023
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.
1024
Connecting devices
After you network the devices together, you configure the connection. You configure the "HMI connection" connection type for communication with the HMI device.
9.8.1.3
1025
9.8.1.4
9.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.
1026
9.8.2
9.8.2.1
1027
PROFIBUS
Ethernet network
An Ethernet network allows you to interconnect all devices that are connected to the network via an integrated Ethernet interface or a communication module. You can thereby connect multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI device. The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device.
PROFINET
PROFINET is an open standard for industrial automation defined by IEEE 61158 and based on Industrial Ethernet. PROFINET makes use of IT standards all the way to the field level and enables plant-wide engineering. With PROFINET, you can realize high-performance automation solutions for applications with stringent real-time requirements.
1028
PROFIBUS PROFIBUS DP
PROFIBUS DP (distributed I/O) is used to connect the following devices: PLCs, PCs, HMI devices Distributed I/O devices, e.g., SIMATIC ET 200 Valves Drives PROFIBUS DP's fast response times make it ideally suited for the manufacturing industry. Its basic functionality includes cyclic exchange of process data between the master and PROFIBUS DP slaves, as well as diagnostics.
PROFIBUS network
You can connect an HMI device within the PROFIBUS network to any SIMATIC S7 module that has an integrated PROFIBUS or PROFIBUS DP interface. You can thereby connect multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI device. The maximum number of communication partners that you can connect to an HMI device is dependent on the HMI device used. Additional information is available in the documentation for the respective HMI device. You configure the SIMATIC S7-200 PLC as a passive device in the network. You connect the SIMATIC S7-200 using the DP connector or a PROFIBUS communication module.
MPI MPI
MPI (Multi-Point Interface) is the integrated interface for SIMATIC products: PLCs HMI devices Programming device/PC Small subnets with the following characteristics are set up with MPI: Short distances Few devices Small data quantities
MPI network
You connect the HMI device to the MPI interface of the SIMATIC S7 PLC. You can connect multiple HMI devices to one SIMATIC S7 PLC and multiple SIMATIC S7 PLCs to one HMI
1029
Network architectures
MPI is based on the PROFIBUS standard (IEC 61158 and EN 50170) and supports the following bus topologies: Line Star Tree An MPI subnet contains a maximum of 127 devices and consists of multiple segments. Each segment contains a maximum of 32 devices and is limited by terminating resistors. Repeaters are used to connect segments. The maximum cable length without a repeater is 50 m.
PPI Introduction
PPI (point-to-point interface) is an integrated interface that was developed specially for the SIMATIC S7-200. A PPI network typically connects S7-200 PLCs. However, other SIMATIC PLCs (e.g., S7-300 and S7-400) or HMI devices can communicate with a SIMATIC S7-200 in the PPI network.
PPI network
A PPI connection is a point-to-point connection. The HMI device is the master. The SIMATIC S7-200 is the slave. You can connect a maximum of one SIMATIC S7-200 to an HMI device. You use the serial connector of the CPU to connect the HMI device. You can connect multiple HMI devices to one SIMATIC S7-200. From the perspective of the SIMATIC S7-200, only one connection at a time is possible. Note The PPI network can contain a maximum of four masters in addition to the HMI device. For performance reasons, do not configure more than four devices at a time as a master in the PPI network.
Network architectures
PPI is based on the PROFIBUS standard (IEC 61158 and EN 50170) and supports the following bus topologies: Line Star
1030
9.8.2.2
Networking devices
The network view of the "Devices & Networks" editor includes a graphical area and a tabular area. You can use the graphical area to network the devices in the project with drag-and-drop. The tabular area provides an overview of the devices and their components. You can network the following PLCs together with HMI devices in the "Devices & Networks" area. SIMATIC S7 1200 SIMATIC S7 300 SIMATIC S7 400 All other PLCs are available in the TIA-Portal and are configured "not integrated". You configure "not integrated" connections in the "Connections" editor of the HMI device.
1031
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.
1032
Integrated connections
Connections of devices within a project are referred to as integrated connections. In the case of integrated connections, you can directly configure addresses of PLC tags. Note An HMI connection can be configured in the "Devices & Networks" editor for the following PLCs only: SIMATIC S7 1200 SIMATIC S7 300 SIMATIC S7 400 You configure the HMI connections to all other PLCs in the "Connections" editor of the HMI device.
1033
5. Change the IP address and subnet mask address parameters according to the requirements of your project.
1034
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.
1035
Then you can configure the parameters of the selected HMI connection and the communication partners in the inspector window.
Requirements
A project is open. An HMI device has been created.
1036
1037
1038
9.8.3
9.8.3.1
Data exchange
Data exchange using tags
Internal tags do not have a process link and only convey values within the WinCC.
Tags in WinCC
For external tags, the properties of the tag are used to define the connection that the WinCC uses to communicate with the automation system and form of data exchange. Tags that are not supplied with values by the process - the internal tags - are not connected to the automation system. In the tag's "Connection" property, this is identified by the "Internal tag" entry. You can create tags in different tag tables for greater clarity. You then directly access the individual tag tables in the "HMI tags" node in the project tree. The tags from all tag tables can be displayed with the help of the table "Show all tags". With structures you bundle a number of different tags that form one logical unit. Structures are project-associated data and are available for all HMI devices of the project. You use the "Types" editor in the project library to create and edit a structure.
1039
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.
1040
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.
Principle
An external tag is the image of a defined memory location in the PLC. You have read and write access to this storage location from both the HMI device and from the PLC. Since external tags are the image of a storage location in the PLC, the applicable data types depend on the PLC which is connected to the HMI device. In STEP 7, if you write a PLC control program, the PLC tags created in the control program will be added to the PLC tag table. If you want to connect an external tag to a PLC tag, access the PLC tags directly via the PLC tag table and connect them to the external tag.
1041
Data types
All the data types which are available at the connected PLC are available at an external tag in WinCC. Information about data types which are available for connection to other PLCs can be found in the documentation about the respective communication drivers. See "Communication between devices (Page 1019)" 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.
See also
Communication between devices (Page 1019)
You can find additional details on this in the section "Basics of communication (Page 1019)".
1042
1043
S7 1200
Yes
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.
See also
Basics of communication (Page 1019)
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.
1044
9.8.3.2
Area pointers
The following area pointers are supported:
Area pointer
Area pointers can be configured for connections. Data record Date/time
1045
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.
1046
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.
1047
1048
Alternative procedure
Alternatively, you can also use the absolute access mode to access area pointers.
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.
1049
Procedure
1. Open "PLC > Program blocks" in the project tree. 2. Double-click the global data block you created previously. The data block opens.
3. Enter a tag name in the "Name" column. 4. Select "Array[lo .. hi] of type" as the data type in the "Data type" column. 5. Replace the "lo" entry by the low value for the dimension of the array. 6. Replace the "hi" entry by the high value for the dimension of the array. Example: If you configure an area pointer with the length "4", enter the value "0" for "lo" and the value "3" for "hi" inside the brackets. 7. Replace the "type" designation with the "word" data type. The full data type for an array of 4 tags appears as follows: "Array[0 .. 3] of word". The tag array is created after the entry is confirmed. 8. Click "Compile". The project is compiled.
1050
Requirements
The global data block has been parameterized in the PLC program.
Procedure
1. Open "HMI >Connections" in the project tree. 2. Click the "Area pointer" tab. 3. Enable the required area pointer. You enable a global area pointer by selecting the connection in the "Connection" field. 4. Click the navigation button in the "PLC tag" field. The object list opens. 5. Navigate to the data block in the object list, and select the tag in the right window. You do not need an array tag to configure an area pointer with the length of "1".
6. Select the "Word" data type when creating the tag in the data block. If required, set additional parameters, such as the acquisition cycle, during configuration.
Result
The area pointer is enabled and connected to the PLC tag in the global data block.
9.8.4
9.8.4.1
Device dependency
Basic Panel
Communication drivers for Basic Panels Device dependency of the Basic Panels
The following table shows which communication drivers you can configure with the various Basic Panels.
1051
Communication drivers
HMI SIMATI SIMATI SIMATI SIMATI OPC devices C S7 C S7 C S7 C 1200 300/40 200 HTTP 0 protoco l KP300 Basic Yes Yes Yes Yes Yes No No No No AllenAllenMitsubi Mitsubi Bradley Bradley shi MC shi FX DF1 TCP/IP EtherN et/IP Yes Yes No No Yes Yes No No Modico n Modbu s TCP/ IP Yes Yes Modico Omron n Host Modbu Link s RTU No No No No
KTP40 Yes 0 Basic mono PN KTP40 Yes 0 Basic mono PN Portrait KTP60 Yes 0 Basic DP KTP60 Yes 0 Basic DP Portrait KTP60 Yes 0 Basic PN KTP60 Yes 0 Basic PN Portrait KTP60 Yes 0 Basic mono PN KTP60 Yes 0 Basic mono PN Portrait KTP10 00 Basic DP KTP10 00 Basic PN Yes
Yes
Yes
No
No
Yes
No
Yes
No
Yes
No
No
Yes
Yes
No
No
No
Yes 2)
No
Yes
No
yes 1)
Yes
Yes
Yes
No
No
No
Yes 2)
No
Yes
No
yes 1)
Yes
Yes
Yes
No
No
Yes
No
Yes
No
Yes
No
No
Yes
Yes
No
No
Yes
No
Yes
No
Yes
No
No
Yes
Yes
No
No
Yes
No
Yes
No
Yes
No
No
Yes
Yes
No
No
Yes
No
Yes
No
Yes
No
No
Yes
Yes
No
No
No
Yes 2)
No
Yes
No
yes 1)
Yes
Yes
Yes
Yes
No
No
Yes
No
Yes
No
Yes
No
No
Yes
Yes
No
No
Yes
No
Yes
No
Yes
No
No
1052
1)
2)
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
KTP1000 Basic PN PROFINET (X1) PROFINET (X1) PROFINET (X1) PROFINET (X1)
TP1500 Basic PN PROFINET (X1) PROFINET (X1) PROFINET (X1) PROFINET (X1)
2)
2)
Mitsubishi TCP/ PROFINET IP (X1) Mitsubishi FX Modicon Modbus TCP Modicon Modbus RTU Omron Host Link PROFINET (X1)
3)
1053
3)
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
Area pointer
KP300 Basic KTP400 Basic PN Screen number Data record Date/time Date/time PLC Coordination Project ID Job mailbox Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes KTP600 Basic PN Yes Yes Yes Yes Yes Yes Yes KTP600 Basic DP Yes Yes Yes Yes Yes Yes Yes KTP1000 Basic PN Yes Yes Yes Yes Yes Yes Yes KTP1000 Basic DP Yes Yes Yes Yes Yes Yes Yes TP1500 Basic PN Yes Yes Yes Yes Yes Yes Yes
1054
9.8.5
9.8.5.1
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
1055
9.8.5.2
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.
1056
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.
1057
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 1058)" 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.
1058
"Connection"
Displays whether the devices are networked together. - displayed if the devices are networked together. - displayed if the devices are not networked together.
"Connection path"
The communication partners of the selected HMI connection and the associated PROFINET parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area is not editable. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device.
1059
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.
1060
"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.
1061
"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.
1062
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.
1063
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.
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.
1064
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.
"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.
1065
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.
1066
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.
1067
Restrictions
The following restrictions must be observed: The individual check boxes can only be used if the port supports the function in question. If a partner port has been determined for the port, the following check boxes cannot be used: "End of discovery of accessible devices" "End of topology discovery" If autonegotiation is disabled, none of the check boxes can be used.
9.8.5.3
1068
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".
1069
7. Click the name of the connection. The connection is displayed graphically in the Inspector window. 8. Click "Highlight HMI connection" and select the HMI connection. 9. Click the communication partners in the "Network view" and change the PROFINET parameters in the Inspector window according to the requirements of your project. See the chapter "PROFIBUS parameters (Page 1070)" 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.
1070
"Connection"
Displays whether the devices are networked together. - displayed if the devices are networked together. - displayed if the devices are not networked together.
1071
"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.
1072
"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.
1073
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.
1074
"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.
1075
Meaning of profiles
Profile DP Meaning 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. 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.
Universal
9.8.5.4
Data exchange
Data exchange using area pointers General information on area pointers Introduction
You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations. The PLC and the HMI device trigger defined interactions based on the evaluation of stored data.
1076
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29 result in the years 2000 through 2029.
1077
n+4 1) n+5
1)
Reserved Reserved
Reserved Reserved
1078
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29 result in the years 2000 through 2029.
The HMI devices do not support the use of nanoseconds. Values in the nanosecond range will be ignored during processing in Runtime.
1079
Application
Note Each time the area pointer is updated by the HMI device, the entire coordination area is always written. For this reason, the PLC program must not make any changes in the coordination area.
Startup bit
The startup bit is set briefly to "0" by the HMI device during startup. After startup, the bit is set permanently to "1".
Operating mode
As soon as the HMI device is switched offline by the user, the operating mode bit is set to 1. In normal operation of the HMI device, the state of the operating mode bit is "0". You can find out the current operating mode of the HMI device by querying this bit.
Life bit
The life bit is inverted by the HMI device at intervals of approximately one second. By querying this bit in the PLC program, you can check whether or not the connection to the HMI device still exists.
1080
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 1. Word 2. Word 3. Word 4th word 5. Word 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Current screen type Current screen number Reserved Current field number Reserved
1081
Use
In order to use this area pointer you must set up the following during the configuration: Define the version of configuration. Possible values between 1 and 255. You enter the version in the editor "Runtime settings > General" in the "Identification" area. This is where you select the PLC tag or the tag array that you have configured as the data area for the area pointer.
Connection failure
A connection failure to a device on which the "project ID" area pointer is configured results in all the other connections in the project being switched to "offline". This behavior has the following prerequisites:
1082
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 n+0 n+1 n+2 n+3 Most significant byte 0 Parameter 1 Parameter 2 Parameter 3 Least significant byte Job number
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.
1083
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 Parameter 2 Parameter 3 15 Set date (BCD-coded) Parameter 1 Left byte: Right byte: weekday (1-7: Sunday-Saturday) Left byte: day (1-31) Right byte: month (1-12) Left byte: year Left byte: Right byte: hours (0-23) Left byte: minutes (0-59) Right byte: seconds (0-59) -
Logs the user on with the name "PLC user" at the HMI device with the group number transferred in parameter 1. The logon is possible only when the transferred group number exists in the project. Parameter 1 Parameter 2, 3 24 User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 Transferring date/time to PLC An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 Transfer date/time to the PLC An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 46 Updating tags Causes the HMI device to read the current value of the tags from the PLC whose update ID matches the value transferred in parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 Clear event buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. Parameter 1, 2, 3 50 Clear error alarm buffer 1 - 100 Group number 1 to 255 -
1084
14 Set time (BCD-coded) Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 Display selection Parameter 1 Parameter 2 Parameter 3 69 Reading data record from PLC Parameter 1 Parameter 2 Parameter 3 70 Screen number Field number
1)
Recipe number (1-999) Data record number (1-65535) 0: Do not overwrite existing data record 1: Overwrite existing data record
Writing data record from PLC 1) Parameter 1 Parameter 2 Parameter 3 Recipe number (1-999) Data record number (1-65535) -
1) 2)
Only devices supporting recipes OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. The weekday is ignored on HMI device KTP 600 BASIC PN.
3)
1085
1086
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.
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 1 2 Yes 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. 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 5 The HMI device sets the status "Transfer completed." The control program must reset the status word to zero in order to enable further transfers. Action Check: Status word = 0? No Abort with system alarm.
1087
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".
1088
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step 1 2 3 4 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. The HMI device reads the values and stores the values in the data record specified in the job mailbox. 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. Action Check: Status word = 0? No Abort without return message.
Sequence writing to the PLC with job mailbox "DAT PLC" (no. 70)
Step 1 2 3 4 5 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. 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. The HMI device sets the status "Transfer completed." The PLC program can now evaluate the transferred data. To allow further transfers, the PLC program must set the status word to 0 again. Action Check: Status word = 0? No Abort without return message.
1089
Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function
Step 1 2 Yes The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. The HMI device reads the values from the PLC and stores them in the data record specified in the function. 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. Action Check: Status word = 0? No Abort with system alarm.
3 4
4 5
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 V11.0 SP2 System Manual, 04/2012,
1090
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 803)
Time-triggered trends
The HMI device reads in the trend values cyclically at an interval specified in the configuration.
1091
Data types
For connections with a SIMATIC communication driver, the following data types are supported:
PLC Discrete alarms SIMATIC S7 PLCs WORD, INT Permitted data types Analog alarms BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, TIMER
1092
1093
9.8.5.5
Permitted data types for SIMATIC S7 1200 - V1 Permitted data types for connections with SIMATIC S7 1200 (V1)
V1: Firmware Version V1.0 The table lists the data types that can be used when configuring tags and area pointers.
1094
Permitted data types for SIMATIC S7 1200 - V2 Permitted data types for connections with SIMATIC S7 1200 (V2)
V2: Firmware Version V2.0 The table lists the data types that can be used when configuring tags and area pointers.
Data type BOOL SINT INT DINT USINT UINT UDINT REAL LREAL TIME DATE DTL Length 1 bit 1 byte 2 bytes 4 bytes 1 byte 2 bytes 4 bytes 4 bytes 8 bytes 4 bytes 2 bytes 12 bytes
1095
9.8.5.6
1096
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.
1097
6. Set the IP addresses of the communication partners in the Inspector window: HMI device: "Parameters > HMI device > Address" PLC: "Parameters > PLC > Address"
1098
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".
1099
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.
1100
1101
1102
1103
9.8.6
9.8.6.1
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.
1104
9.8.6.2
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.
1105
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.
1106
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 1108)" 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.
1107
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.
1108
"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.
1109
1110
"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.
1111
"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.
1112
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.
1113
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.
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.
1114
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.
"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.
1115
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.
1116
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.
1117
Restrictions
The following restrictions must be observed: The individual check boxes can only be used if the port supports the function in question. If a partner port has been determined for the port, the following check boxes cannot be used: "End of discovery of accessible devices" "End of topology discovery" If autonegotiation is disabled, none of the check boxes can be used.
9.8.6.3
1118
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".
1119
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 1120)" 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.
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.
1120
"Connection"
Displays whether the devices are networked together. - displayed if the devices are networked together. - displayed if the devices are not networked together.
"Connection path"
The communication partners of the selected HMI connection and the associated PROFIBUS parameters are displayed in the "Connection path" area. Some of the areas displayed cannot be edited in this dialog. "End point" Displays the device name. This area is not editable. "Interface" Displays the selected interface of the device. You can choose between several interfaces, depending on the device.
1121
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.
1122
"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.
1123
"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.
1124
Meaning of profiles
Profile DP Meaning 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. 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.
Universal
1125
9.8.6.4
1126
Requirements
The following communication partners are created in the "Devices & Networks" editor: HMI device with MPI/DP interface SIMATIC S7 300/400 with MPI/DP interface
Procedure
1. Double-click the "Devices & Networks" item in the project tree. The available communication partners in the project are displayed graphically in the network view.
2. Click the "Connections" button. The devices available for connection are highlighted in color. 3. Click the interface of the PLC and use a drag-and-drop operation to draw a connection to the HMI device.
1127
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.
1128
"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.
1129
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.
1130
"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.
1131
"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.
1132
9.8.6.5
Data exchange
Data exchange using area pointers General information on area pointers Introduction
You use an area pointer to access a data area in the PLC. During communication, the PLC and the HMI device alternately access these data areas for read and write operations.
1133
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 1st word 2nd word 3rd word 4th word 5th word 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Current screen type Current screen number Reserved Current field number Reserved
1134
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29result in the years 2000 through 2029.
1135
n+4 1) n+5 1)
Reserved Reserved
Reserved Reserved
1)
The two data words must exist in the data area to ensure that the data format corresponds to WinCC flexible and to avoid false information being read.
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29 result in the years 2000 through 2029.
1136
Use
Note The HMI device always writes the entire coordination area when updating the area pointer. The control program can for this reason not make changes to the coordination area.
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.
1137
Use
To use this area pointer, set up the following during the configuration: Define the version of configuration. Possible values between 1 and 255. You enter the version in the editor "Runtime settings > General" in the "Identification" area. Data address of the value for the version that is stored in the PLC: Enter the data address in the "Communication > Connections" editor in "Address".
Connection failure
A connection failure to a device on which the "project ID" area pointer is configured results in all the other connections in the project being switched to "offline". This behavior has the following prerequisites: You have configured several connections in a project. You are using the "project ID" area pointer in at least one connection. The following causes which may set connections to "offline": The PLC is not available. The connection has been switched offline in the engineering system.
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 n+0 n+1 n+2 n+3 Most significant byte 0 Parameter 1 Parameter 2 Parameter 3 Least significant byte Job number
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.
1138
Job mailboxes
All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online.
No . Function
14 Setting the time (BCD coded) Parameter 1 Parameter 2 Parameter 3 15 Setting the date (BCD code) Parameter 1 Left byte: Right byte: hours (0-23) Left byte: minutes (0-59) Right byte: seconds (0-59) 3) 4)
Left byte: Right byte: weekday (1-7: Sunday-Saturday) Left byte: day (1-31) Right byte: month (1-12) Left byte: year
Logs the user on with the name "PLC user" at the HMI device with the group number transferred in parameter 1. The logon is possible only when the transferred group number exists in the project. Parameter 1 Parameter 2, 3 24 User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 Transfer date/time to PLC (in the S7 format DATE_AND_TIME) An interval of at least 5 seconds must be maintained between two successive jobs in order to prevent overload of the HMI device. Parameter 1, 2, 3 41 Transfer date/time to PLC (In OP/MP format) An interval of at least 5 seconds must be maintained between two successive jobs in order to prevent overload of the HMI device. Parameter 1, 2, 3 46 Update tags Causes the HMI device to read the current value of the tagsfrom the PLC whose update ID matches the value transferred in parameter 1. (Function corresponds to the "UpdateTag" system function.) Group number 1 to 255 -
1139
14 Setting the time (BCD coded) Parameter 1 49 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. Parameter 1, 2, 3 50 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 Screen selection Parameter 1 Parameter 2 Parameter 3 69 Reading data record from PLC Parameter 1 Parameter 2 Parameter 3 70 Writing data record from PLC Parameter 1 Parameter 2 Parameter 3
1) 2) 2)
1 - 100
Recipe number (1-999) Data record number (1-65535) 0: Do not overwrite existing data record 1: Overwrite existing data record
1)
Only for devices supporting recipes. OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. The weekday is ignored on HMI device KTP 600 BASIC PN. The weekday is ignored when you configure the "Date/Time PLC" area pointer.
3) 4)
1140
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.
1141
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.
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"
1142
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 1 2 Yes 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. 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 5 The HMI device sets the status "Transfer completed." The control program must reset the status word to zero in order to enable further transfers. Action Check: Status word = 0? No Abort with system event.
1143
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".
1144
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step 1 2 3 4 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data record. The HMI device reads the values from the PLC and saves these to the data record defined in the job mailbox. 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. Action Check: Status word = 0? No Abort without return message.
Sequence of writing to the PLC with job mailbox "DAT PLC" (no. 70)
Step 1 2 3 4 5 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. 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. The HMI device sets the status "Transfer completed." 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. Action Check: Status word = 0? No Abort without return message.
Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function
Step 1 2 Yes The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. The HMI device reads the values from the PLC and stores them in the data record specified in the function. Action Check: Status word = 0? No Abort with system event.
1145
4 5
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
1146
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 803)
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.
1147
Data types
For connections with a SIMATIC communication driver, the following data types are supported:
PLC Discrete alarms SIMATIC S7 300/400 WORD, INT Permitted data types Analog alarms BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, COUNTER, TIME
1148
1149
9.8.6.6
Permitted data types for SIMATIC S7 300/400 Permitted data types for connections with SIMATIC S7 300/400
The table lists the data types that can be used when configuring tags and area pointers.
Data type BOOL BYTE WORD DWORD CHAR INT DINT REAL TIME DATE TIME_OF_DAY, TOD S5TIME Length 1-bit 1 byte 2 bytes 4 bytes 1 byte 2 byte 4 bytes 4 bytes 4 bytes 2 bytes 4 bytes 2 bytes
1150
9.8.6.7
Procedure
1. Open the "Connections" editor of the HMI device. 2. Double-click "<Add>".
1151
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"
1152
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".
1153
7. Set the addresses of the communication partners in the inspector window: HMI device: "Parameters > HMI device > Address" PLC: "Parameters > PLC > Address"
1154
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".
1155
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.
1156
1157
1158
1159
1160
1161
1162
9.8.7
9.8.7.1
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
9.8.7.2
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.
1163
1164
See the chapter "Parameters for the connection (Page 1165)" for additional details.
9.8.7.3
1165
1166
1167
1168
1169
1170
1171
9.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.
1172
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 1st word 2nd word 3rd word 4th word 5th word 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Current screen type Current screen number Reserved Current field number Reserved
Current screen type "1" for root screen or "4" for permanent window Current screen number 1 to 32767 Current field number 1 to 32767
1173
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29result in the years 2000 through 2029.
1174
n+4 1) n+5
1)
Reserved Reserved
Reserved Reserved
1)
The two data words must exist in the data area to ensure that the data format matches WinCC flexible and to avoid reading false information.
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29 result in the years 2000 through 2029.
Use
Note Each time the area pointer is updated by the HMI device, the entire coordination area is always written. For this reason, the PLC program must not make any changes in the coordination area.
1175
Startup bit
The startup bit is set briefly to "0" by the HMI device during startup. After startup, the bit is set permanently to "1".
Operating mode
As soon as the HMI device is switched offline by the user, the operating mode bit is set to 1. In normal operation of the HMI device, the state of the operating mode bit is "0". You can find out the current operating mode of the HMI device by querying this bit.
Life bit
The life bit is inverted by the HMI device at intervals of approximately one second. By querying this bit in the PLC program, you can check whether or not the connection to the HMI device still exists.
Use
To use this area pointer, set up the following during the configuration: Define the version of configuration. Possible value between 1 and 255. You enter the version in the editor "Runtime settings > General" in the "Identification" area. Data address of the value for the version that is stored in the PLC: You enter the data address in the editor "Communication > Connections" under "Address".
1176
Connection failure
A connection failure to a device on which the "project ID" area pointer is configured results in all the other connections in the project being switched to "offline". This behavior has the following requirements: You have configured several connections in a project. You are using the "project ID" area pointer in at least one connection. Causes which may set connections "offline": The PLC is not available. The connection has been switched offline in the engineering system.
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 n+0 n+1 n+2 n+3 Most significant byte 0 Parameter 1 Parameter 2 Parameter 3 Least significant byte Job number
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.
1177
Job mailboxes
All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online. Note Please note that not all HMI devices support job mailboxes. TP 170A and Micro Panel do not support job mailboxes, for example.
No .
Function
14 Setting the time (BCD coded) Parameter 1 Parameter 2 Parameter 3 15 Set date (BCD code) Parameter 1
3)
Left byte: Right byte: hours (0-23) Left byte: minutes (0-59) Right byte: seconds (0-59) Left byte: Right byte: weekday (1-7: Sunday-Saturday) Left byte: day (1-31) Right byte: month (1-12) Left byte: year
Logs the user on with the name "PLC user" at the HMI device with the group number transferred in parameter 1. The logon is possible only when the transferred group number exists in the project. Parameter 1 Parameter 2, 3 24 User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 Transfer date/time to PLC (in the S7 format DATE_AND_TIME) An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 Transfer date/time to PLC (In OP/MP format) An interval of at least 5 seconds must be maintained between successive jobs in order to prevent overload of the HMI device. Parameter 1, 2, 3 46 Update tags Group number 1 to 255 -
1178
14 Setting the time (BCD coded) Causes the HMI device to read the current value of the tagsfrom the PLC whose update ID matches the value transferred in parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. Parameter 1, 2, 3 50 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 Screen selection Parameter 1 Parameter 2 Parameter 3 69 Reading data record from PLC Parameter 1 Parameter 2 Parameter 3 70
2)
1 - 100
Recipe number (1-999) Data record number (1-65535) 0: Do not overwrite existing data record 1: Overwrite existing data record
Writing data record from PLC 1) Parameter 1 Parameter 2 Parameter 3 Recipe number (1-999) Data record number (1-65535) -
1) 2)
Only devices supporting recipes OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active. The weekday is ignored on HMI device KTP 600 BASIC PN.
3)
1179
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 1 2 Yes 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. 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 5 The HMI device sets the status "Transfer completed." The control program must reset the status word to zero in order to enable further transfers. Action Check: Status word = 0? No Abort with system event.
1180
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".
1181
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step 1 2 3 4 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. The HMI device reads the values from the PLC and saves these to the data record defined in the job mailbox. 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. Action Check: Status word = 0? No Abort without return message.
Sequence of writing to the PLC using job mailbox "DAT PLC" (no. 70)
Step 1 2 3 4 5 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data mailbox. 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. The HMI device sets the status "Transfer completed." 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. Action Check: Status word = 0? No Abort without return message.
1182
Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function
Step 1 2 Yes The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data mailbox. The HMI device reads the values from the PLC and stores them in the data record specified in the function. 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. Action Check: Status word = 0? No Abort with system event.
3 4
4 5
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
WinCC Basic V11.0 SP2 System Manual, 04/2012,
1183
1184
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.
Application
Synchronous data record transfer can be a useful solution, for example, when: The PLC is the "active partner" in the transfer of data records. The PLC evaluates the information about the recipe number and data record number. The transfer of data records is triggered by means of a Job mailbox.
Requirements
In order to synchronize transfer of data records between the HMI device and the PLC, the following requirements must be met during configuration: An area pointer has been set up: "Communication > Connections" editor in "Area pointer". The PLC with which the HMI device synchronizes transfer of data records is specified in the recipe: "Recipes" editor in the Inspector window the "Coordinated transfer of data records" option under "General > Synchronization > Settings".
1185
Status The status word (word 4) can adopt the following values:
Value Decimal 0 2 4 12 Binary 0000 0000 0000 0010 0000 0100 0000 1100 Transfer permitted, data record free Transferring Transfer completed without error Transfer completed with error Meaning
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 803)
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.
1186
Data types
For connections with a SIMATIC communication driver, the following data types are supported:
PLC Discrete alarms SIMATIC S7 PLCs WORD, INT Permitted data types Analog alarms BYTE, CHAR, WORD, INT, DWORD, DINT, REAL, TIMER
1187
1188
9.8.7.5
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 Bool Byte Char Word Int DWord DInt Real StringChar Timer Array Length 1 bit 1 byte 1 byte 2 bytes 2 bytes 4 bytes 4 bytes 4 bytes -2 bytes --
1189
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.
9.8.8
9.8.8.1
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
1190
9.8.8.2
9.8.8.3
Communication drivers
1191
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.
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.
1192
1193
5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters".
1194
1195
1196
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.
1197
* 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.
Note Strings in RSLogix 5000 have a default length of 82 characters. A maximum of 80 characters can be displayed in WinCC. Always use strings which do not exceed the maximum length of 80 characters. Permitted data types - arrays
Address Array Permitted data types Int, UInt, DInt, UDInt, Real
1198
1199
1200
Note Bit addressing with the data types Bool, Real and String is not permitted and will cause an addressing fault.
1201
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.
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
1202
1203
Access to an element of a 2- Arraytag[Dim1,Dim2] dimensional array Element of structure array (1- Arraytag[Dim1].structureelement dimensional) Bit in element basic type array (2-dimensional) Arraytag[Dim1,Dim2]/Bit Structuretag.arraytag Structuretag.structure2.arraytag [element]/ bit
Structure
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]
1204
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 1 2 2 190.130.3.101 1 5 Meaning Backplane connection Stands for the CPU slot number of the second Ethernet module. Stands for an Ethernet connection. IP address of a remote AB rack on the network in particular the third Ethernet module Backplane connection Slot number of the CPU
1205
Operand type
You have the following options under operand type: I O S B C T R F N ST A
File number
Select the number between two limits under file number: Low limit High limit The limit values depend on the selected operand type.
Child element
You can select a child element when you have selected one of the following operand types: R C T
1206
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.
1207
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.
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.
1208
1209
5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters".
1210
1211
1212
RS-232 X X X X X
1) Processors released for PLC-5: PLC-5/11, PLC-5/20, PLC-5/30, PLC-5/40, PLC-5/60, and PLC-5/80.
1213
Connectable PLCs
The Allen Bradley DF1 communication driver is available for the following Allen-Bradley PLCs:
DF1 (point-to-point) PLC SLC500 SLC501 SLC502 SLC503 SLC504 SLC505 MicroLogix PLC-5
1)
RS 232 X X X
2) 2) 2)
X 2) X
1)
2)
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
1214
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.
1) 2) 3)
Only RS 232 is possible for Panel PC and PC. A point-to-point connection to the SLC500, SLC501, and SLC502 PLCs via DF1 is not possible. 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 Allen-Bradley cable 1747-CP3 For connection to MicroLogix Allen-Bradley cable 1761-CBL-PM02
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".
1215
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).
Connecting cable
HMI panel interface used RS 232 9-pin RS 422 9-pin For connection to KF2 interface module Allen-Bradley cable 1784-CP10 and 25-pin socket/socket adapter 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".
1216
DF1 protocol with multi-point connection via KF3 module DF1 protocol with multi-point connection via KF3 module to DH485 LAN
1)
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.
1217
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
1218
Screen connected with housing over large area on both sides max. length 15 m
1219
Screen connected with housing over large area on both sides max. length 3 m
1220
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 ASCII Bool Int DInt UInt UDInt Real Operand type A
1)
N, R, C, T, B, S, I, O N, R, C, T, S N, D
2)
N, R, C, T, B, I, O, D N, D 2) N, F 1)
1221
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
1222
Addressing Addressing
The addressing is entered in the following order in the Allen-Bradley DF1 communication driver: Operand type File number Element number
1223
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
1224
Child element
You can select a child element when you have selected one of the following data types: R C T
1225
Screens
The refresh rate of screens is determined by the type and volume of data to be visualized. Only configure short acquisition cycles for objects which actually require shorter refresh cycles. This procedure reduces update times.
Trends
The HMI device always updates all bit-triggered trends whose group bit is set in the "Trend transfer area". It resets the bits in the next cycle. The group bit in the PLC program can only be set again after the HMI device has reset all bits.
Job mailboxes
A high rate and volume of job mailboxes transferred may lead to overload in communication between the HMI device and the PLC. The HMI device confirms acceptance of the job mailbox by entering the value zero in the first data word of the job mailbox. The HMI device now processes the job for which it requires a certain time slice. It may take the HMI device some time to process a new job mailbox which is transferred in immediate succession to the job mailbox. The next job mailbox is only accepted if sufficient computing resources are available.
Data exchange Area pointers for Allen-Bradley Area pointers for connections using an Allen-Bradley communication driver
You use an area pointer to access a data area in the PLC. For more detailed information on area pointers and their configuration, refer to Section "Data exchange using area pointers".
1226
See also
Data exchange using area pointers (Page 1297)
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 803)
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.
1227
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 Allen-Bradley DF1 PLC SLC500, SLC501, SLC502, SLC503, SLC504, SLC505, PLC5, MicroLogix ControlLogix, CompactLogix, SLC, Micrologix Int, UInt Permitted data types Discrete alarms Analog alarms Int, UInt, Long, ULong, Real
Allen-Bradley EtherNet/IP
Int, UInt
1228
See also
Alarm system in WinCC (Page 804)
1229
1230
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.
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.
1231
1232
5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters".
1233
1234
1235
1236
Connectable PLCs
Connections can be implemented for the following Mitsubishi PLCs:
Mitsubishi FX (PG protocol) PLC MELSEC FX1n, FX2n MELSEC FX3U, FX3UC, FX3G with communication module FX3U-ENET MELSEC System Q Q-series with the communication module QJ71E71-100 QnUDEH CPU with Ethernet interface onboard Yes No No No Yes Yes Mitsubishi MC TCP/IP
1237
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
1238
1239
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 4-bit block 8-bit block 12-bit block 16-bit block 20-bit block 24-bit block 28-bit block 32-bit block Bool Operand type M, X, Y, B, F M, X, Y B, F M, X, Y B, F M, X, Y B, F M, X, Y B, F M, X, Y B, F M, X, Y B, F M, X, Y B, F M, D, X, Y B, F Length 1 byte 1 byte 2 bytes 2 bytes 4 bytes 4 bytes 4 bytes 4 bytes 1-bit
1240
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.
1241
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 Output/Input Bit memory Data register Operand type Y/X M D Max. address FX3 Octal X/Y 0 - 267 M0 - M3071 and M8000 - M8255 D0 - 7999 D8000 - D8255 C0 - 255 T0 - 255 ---Max. address Q-Series HEX X/Y 0 - 7FF M/L/S 0 - 8191 D0 - 8191 D9000 - D9255 becomes SD1000 SD1255 C0 - 1023 T0 - 2047 Hex: W0 - FFF Hex: B0 - FFF F0 - 2047
C T W B F
1242
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.
1243
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.
1244
5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters".
1245
1246
1247
Connectable PLCs
Connections can be implemented for the following Mitsubishi PLCs:
Mitsubishi FX (PG protocol) PLC MELSEC FX1n, FX2n MELSEC FX3U, FX3UC, FX3G with communication module FX3U-ENET MELSEC System Q Q-series with the communication module QJ71E71-100 QnUDEH CPU with Ethernet interface onboard Yes No No No Yes Yes Mitsubishi MC TCP/IP
Connecting cable
The following connecting cables are available to connect the HMI device to the PLC.
Interface to HMI device or adapter RS 232, 9-pin RS 422, 9-pin
1)
Mitsubishi Electric PLC via FX protocol FX1n, Fx2n, Mini DIN, 8pin Mitsubishi SC-09 1) Connecting cable RS422-2P
Since the Mitsubishi PLCs communicate via RS 422 as a standard, the Mitsubishi programming cable SC09 with integrated RS 422/RS 232 adaptor is necessary for connecting a HMI device via RS 232.
Note Applies only to RS 232: Cable length is restricted to 0.32 m. Refer to the relevant device manual to determine which HMI device interface is to be used.
1248
Connecting cables for Mitsubishi FX Connecting cable RS 422 2P, for Mitsubishi 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
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 4-bit block 8-bit block 12-bit block 16-bit block 20-bit block 24-bit block 28-bit block 32-bit block Bool DWord Real String Word Operand type M, X, Y M, X, Y M, X, Y M, X, Y M, X, Y M, X, Y M, X, Y M, X, Y D, M, X, Y D, C-32 bit D D D, T, C-16 bit Length 1 byte 1 byte 2 bytes 2 bytes 4 bytes 4 bytes 4 bytes 4 bytes 1-bit 4 bytes 4 bytes 1 to 50 characters 2 bytes
1249
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.
1250
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.
1251
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".
Mitsubishi FX restrictions
You cannot use the D operand type for configuring area pointers.
See also
Data exchange using area pointers (Page 1297)
1252
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 803)
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.
1253
Data types
For connections with a Mitsubishi communication driver, the following data types are supported:
PLC Discrete alarms FX1n, FX2n, FX3 series, QSeries, iQ-Series Word, Int 1) Permitted data types 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,
1)
Left byte 8 8 7 7
Right byte 0 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."
1254
1255
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.
1256
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.
1257
5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters".
1258
1259
1260
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.
1261
Restrictions
The coupling of the HMI device to PLCs of other manufacturers who offer a Modbus TCP/IP interface is not system-tested and thus, not enabled. However, if another PLC is to be used, observe the following instructions: Use the following CPU types, because these operate without address offset and in the usual bit count manner. Unity, PL7: Premium, Micro, Quantum, M340 The following function codes are used for the respective data areas:
Reading function codes 01 02 03 ReadCoilStatus ReadInputStatus ReadHoldingRegisters Address range 0x / %M 1x / %I 4x / %MW DIGITAL_OUT DIGITAL_IN USERDATA
1262
Address range 4x / %MW 4x / %MW 0x / %M 0x / %M 6x / USERDATA Single USERDATA Multiple DIGITAL_OUT with BIT DIGITAL_OUT with 16 BIT GROUP EXTENDEDMEMORY (not for all CPUs)
16 (10Hex)
1)
15 (0FHex) 21 (15Hex)
1)
Connectable PLCs
Connections can be implemented for the following Modicon Modbus PLCs:
Modicon Modbus PLC Modicon Modbus RTU 2) TSX Compact TSX Quantum Momentum Premium Micro M340 20X0 (without 2010)
1) 2)
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.
1263
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 +/- Double +/- Int 16-bit group ASCII Bit Double Float Int Operand type %MW %MW, %IW %MW, %I %MW %MW, %IW, %M, %I %MW %MW %MW, %IW Length 4 bytes 2 bytes 2 bytes 0 to 80 characters 1-bit 4 bytes 4 bytes 2 bytes
Note The ranges "%I" and "%IW" are not supported for the following CPU types: Premium Micro M340
Permitted data types for CPU type "Concept, ProWORX: Compact, Quantum, Momentum"
Data type +/- Double +/- Int 16-bit group ASCII Bit Operand type 4x, 6x 3x, 4x, 6x 0x, 1x 4x, 6x 0x, 1x, 3x, 4x, 6x Length 4 bytes 2 bytes 2 bytes 0 to 80 characters 1-bit
1264
1265
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.
1266
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.
1267
1268
5. Select all necessary connection parameters for the interface in the Inspector window under "Parameters".
1269
1270
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 directly via Modbus interface (RS232) 9-pin Sub D male connector PP1 Via MB Bridge (RS 232) PP1 directly via Modbus interface (RS232) 8-pin RJ45 connector PP2
The cable pin assignments can be found in Section "Connecting cables for Modicon Modbus RTU".
1271
Restrictions
The connection of the HMI device to PLCs of other manufacturers which offer a Modicon Modbus interface is not system-tested and therefore not approved. If you use another PLC nevertheless, observe the following information: These drivers only work for tags with the bit counting method typical for Modicon PLCs from left (bit1 = most significant bit) to right (bit16 = least significant bit in data type INT). The address offset displayed in the configuring is subtracted at protocol level in the message frame. E.g. in Holding Register 4x the offset "40001". The configured address "40006" therefore becomes address "5" in the message frame. The address (e.g. "5") transferred in the message frame is transformed to the PLC-specific address range in the different Non-Modicon PLCs. A reply message frame without "ExceptionCode" is expected within 500 ms. The following function codes are used for the respective data areas:
Reading function codes 01 02 03 04 20 (14Hex) ReadCoilStatus ReadInputStatus ReadHoldingRegisters ReadInputRegisters ReadGeneralReference Address range 0x 1x 4x 3x 6x DIGITAL_OUT DIGITAL_IN USERDATA ANALOG_IN EXTENDEDMEMORY (not for all CPUs)
1272
Connectable PLCs
Connections can be implemented for the following Modicon Modbus PLCs:
Modicon Modbus PLC Modicon Modbus RTU TSX Compact TSX Quantum Momentum Premium Micro M340 20x0 (without 2010)
1) 2)
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.
1273
Connecting cables for Modicon Modbus RTU Connecting cable PP1, RS-232, for Modicon Point-to-point cable 1: PLC > PC ...
1274
Connecting cable PP2, RS-232, for Modicon Point-to-point cable 2: PLC (TSX Compact) > PC...
1275
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 +/- Double +/- Int 16-bit group ASCII Bit 1) Double Float Int
1)
Operand type 4x, 6x 3x, 4x, 6x 0x, 1x 4x, 6x 0x, 1x, 3x, 4x, 6x 4x, 6x 4x, 6x 3x, 4x, 6x
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 6 7 8 9 Right byte 10 11 12 13 14 15 16
1276
1277
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 1297)".
1278
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 803)
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.
1279
Data types
For connections with a Modicon Modbus communication driver, the following data types are supported:
PLC All Modicon series Int, +/-Int Permitted data types Discrete alarms Analog alarms 16 Bit Group, Int, +/-Int, Double, +/-Double, Float
1280
1281
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.
1282
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.
1283
1284
5. Select all necessary connection parameters for the interface in the inspector window under "Parameters".
1285
1286
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 RS232, 9-pin Omron PLC RS232, 9-pin PP1 RS232 I/O port Programming cable (standard cable of Omron) RS422, 9-pin RS422, terminals/ pins
PP2
Refer to the relevant device manual to determine which HMI device interface is to be used.
1287
Multipoint connection
A multipoint connection to the up to 4 approved OMRON PLCs in a RS422-four-wire connection can be implemented with communication modules on the PLCs and is system-tested and approved by Siemens AG. Note The HMI device can only be operated as a master. Exactly one master is possible in the RS422-four-wire-Multidrop connection.
Connecting cable Connecting cable MP1, RS-232, over converter, for Omron Multipoint cable 1: MP/TP/PC > PLC
1)
Connecting cable MP2, RS-422, for Omron Multipoint cable 2: RS422, MP/TP/PC > SPS_
1288
Connecting cable PP1, RS-232, for Omron Point-to-point cable PP1, PC/TP/OP - PLC
Connecting cable PP2, RS-422, for Omron Point-to-point cable PP2, RS-422
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 Bool Byte DInt Int Real String UDInt UInt Operand type I/O, HR, AR, LR, DM, T/ C bit, CPU status CPU type HR, AR, LR, DM I/O, HR, AR, LR, DM, T/ C Val HR, DM HR, AR, LR, DM HR, AR, LR, DM I/O, HR, AR, LR, DM, T/ C Val Length 1-bit 1 byte 4 bytes 2 bytes 4 bytes 0 to 80 characters 4 bytes 2 bytes
1289
Note Read and write operations of all data areas in the OMRON PLC can only be reliably carried out in "STOP" or "MONITOR" mode. "I/O" refers either to the IR/SR area or the CIO area depending on the PLC series. The operand types "LR", "HR" and "AR" are not available in all PLC series. Note Note the following for write accesses: For the "Bool" data type with the operand types "I/O", "HR", "AR", "LR" and "DM", the entire word is written back into the PLC when the specified bit is changed. There is no check to determine whether any other bits in the word have changed. As a result, the PLC only has read access to the specified word.
Operand type old PLC CPU Status I/O HR AR LR DM T/C CPU type
Operand type CS and CJ PLC CPU Status CIO H Range 0-511 A n/a 1) D T/C 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
1290
1291
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.
1292
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".
See also
Data exchange using area pointers (Page 1297)
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 803)
1293
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.
Data types
For connections with an Omron communication driver, the following data types are supported:
PLC CP1, CJ1, CJ2, CS1, CPM Uint, int Permitted data types Discrete alarms Analog alarms UInt, Int, UDInt, DInt
1294
Left byte 8 8 7 7
Right byte 0 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.
1295
1296
9.8.8.4
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.
1297
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.
1298
Structure
The area pointer is a data area in the memory of the PLC with a fixed length of 5 words.
15 1. word 2. word 3. word 4th word 5. word 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Current screen type Current screen number Reserved Current field number Reserved
Current screen type "1" for root screen or "4" for permanent window Current screen number 1 to 32767 Current field number 1 to 32767
1299
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29result in the years 2000 through 2029.
n+4 1) n+5
1)
Reserved Reserved
Reserved Reserved
1)
The two data words must exist in the data area to ensure that the data format matches WinCC and to avoid reading false information.
Note Note that when you enter the year, values 80 to 99 result in years 1980 through 1999 and the values 0 to 29result in the years 2000 through 2029.
1300
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.
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.
1301
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.
1302
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 n+0 n+1 n+2 n+3 Left byte 0 Parameter 1 Parameter 2 Parameter 3 Right byte Job number
The HMI device evaluates the job mailbox if the first word of this job is not equal to zero. This means that the parameters must be entered in the job mailbox first, followed by the job number. When the HMI device accepts the job mailbox, the first word is set to 0 again. The execution of the job mailbox is generally not completed at this point in time.
Job mailboxes
All job mailboxes and their parameters are listed below. The "No." column contains the job number of the job mailbox. Job mailboxes can only be triggered by the PLC when the HMI device is online. Note Please note that not all HMI devices support job mailboxes.
No .
Function
14 Setting the time (BCD coded) Parameter 1 Parameter 2 Parameter 3 15 Parameter 1 Left byte: Right byte: hours (0-23) Left byte: minutes (0-59) Right byte: seconds (0-59) Left byte: Right byte: weekday (1-7: Sunday-Saturday) Left byte: day (1-31) Right byte: month (1-12) Left byte: year
Logs the user on with the name "PLC user" at the HMI device with the group number transferred in Parameter 1. The logon is possible only when the transferred group number exists in the project. Parameter 1 Parameter 2, 3 Group number 1 to 255 -
1303
14 Setting the time (BCD coded) User logoff Logs off the current user. (The function corresponds to the "logoff" system function) Parameter 1, 2, 3 40 Transfer date/time to PLC (in the S7 format DATE_AND_TIME) An interval of at least 5 seconds must be maintained between two successive jobs to prevent overload of the HMI device. Parameter 1, 2, 3 41 Transfer date/time to PLC (In OP/MP format) An interval of at least 5 seconds must be maintained between successive jobs in order to prevent overload of the HMI device. Parameter 1, 2, 3 46 Update tags Causes the HMI device to read the current value of the tagsfrom the PLC whose update ID matches the value transferred in parameter 1. (Function corresponds to the "UpdateTag" system function.) Parameter 1 49 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Warnings" class from the alarm buffer. Parameter 1, 2, 3 50 Delete alarm buffer Deletes all analog alarms and discrete alarms of the "Errors" class from the alarm buffer. Parameter 1, 2, 3 51 Screen selection Parameter 1 Parameter 2 Parameter 3 69 Read data record from PLC Parameter 1 Parameter 2 Parameter 3 70 Write data record to PLC Parameter 1 Parameter 2 Parameter 3
1)
1)
1 - 100
Screen number Field number Recipe number (1-999) Data record number (1-65535) 0: Do not overwrite existing data record 1: Overwrite existing data record Recipe number (1-999) Data record number (1-65535) -
OP 73, OP 77A and TP 177A HMI devices also execute the "Screen selection" job mailbox if the on-screen keyboard is active.
1304
1305
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.
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"
1306
Status The status word (word 4) can adopt the following values:
Value Decimal 0 2 4 12 Binary 0000 0000 0000 0010 0000 0100 0000 1100 Transfer permitted, data record free Transferring. Transfer completed without error Transfer completed with error Meaning
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 1 2 Yes 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. 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 5 The HMI device sets the status "Transfer completed." The control program must reset the status word to zero in order to enable further transfers. Action Check: Status word = 0? No Abort with system event.
1307
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".
1308
Sequence when reading from the PLC with job mailbox "PLC DAT" (no. 69)
Step 1 2 3 4 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data record. The HMI device reads the values from the PLC and saves these to the data record defined in the job mailbox. 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. Action Check: Status word = 0? No Abort without return message.
Sequence of writing to the PLC with job mailbox "DAT PLC" (no. 70)
Step 1 2 3 4 5 Yes The HMI device enters the recipe and data record number specified in the job and the status "Transferring" in the data record. 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. The HMI device sets the status "Transfer completed." 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. Action Check: Status word = 0? No Abort without return message.
1309
Sequence of the transfer when triggered by a configured function Reading from the PLC using a configured function
Step 1 2 Yes The HMI device enters the recipe and data record number specified in the function and the status "Transferring" in the data record. The HMI device reads the values from the PLC and stores them in the data record specified in the function. 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. Action Check: Status word = 0? No Abort with system event.
3 4
4 5
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 V11.0 SP2 System Manual, 04/2012,
1310
9.9
9.9.1
Introduction
The HMI device wizard will automatically start when you create a new HMI device in your project.
1311
9.9.2
9.9.2.1
Introduction
WinCC enables you to export data from a project and import it into another project. You export or import the following project data:
1312
See also
Exporting alarms (Page 1317) Exporting tags (Page 1325) Exporting text lists (Page 1330)
1313
9.9.2.2
Requirements
The WinCC project for the export is open. Recipes have been created in a project. The "Recipes" editor is open.
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.
WinCC Basic V11.0 SP2 System Manual, 04/2012,
1314
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 1317) Importing and exporting project data (Page 1312) Exporting tags (Page 1325) Exporting text lists (Page 1330)
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.
1315
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. 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.
1316
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 1314)
9.9.2.3
1317
Requirements
The WinCC project for the export is open. Alarms have been created in the project. The "HMI alarms" editor is open.
Exporting alarms
button in "Discrete alarms" or "Analog alarms". 1. Click the 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 1319) Format of the analog alarm data (Page 1320) Format of the discrete alarm data (Page 1323) Exporting recipes (Page 1314) Exporting tags (Page 1325) Importing and exporting project data (Page 1312)
1318
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. 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.
1319
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 1317)
1320
Meaning of the entries Meaning 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 of the analog alarm 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. 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. Specifies the tag monitored for limit value violation. Specifies the delay time. The alarm is not triggered until the duration of the limit value violation equals the specified delay time.
Group
1321
Meaning of the entries Meaning 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.
Trigger mode Indicates the method used for monitoring the limit value. Specifies the limit that will be monitored. Both a tag and a constant can be used as limit value. Limit value Indicates the tag or constant monitored for limit violation.
1322
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 1317)
1323
Meaning of the entries Meaning 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 of the analog alarm 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. 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. Specifies the tag containing the bit that triggers the alarm. Specifies the number of the bit that triggers the alarm. Specifies the tag containing the bit that is set by the operator upon acknowledgment. Only available if the selected alarm class requires alarm acknowledgment. Specifies the number of the bit that is set when the operator acknowledges the alarm.
Group
Acknowledgment bit
1324
PLC acknowledgment bit Delay time value Delay time unit Report
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 1317)
9.9.2.4
Requirements
The WinCC project for the export is open. Tags have been created in the project. The "HMI tags" editor is open.
1325
Exporting tags
button in the "HMI Tags" tab. 1. Click on the 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 1326) Exporting alarms (Page 1317) Importing and exporting project data (Page 1312) Exporting text lists (Page 1330) Exporting recipes (Page 1314) Format of the tag data (Page 1327)
Requirements
An xlsx file with tags has been created. The structure of the xlsx file meets the requirements. The WinCC project for the import is open. The "HMI tags" editor is open.
1326
Importing tags
1. Click on the button. The "Import" dialog box opens.
2. Click the "..." button and select the file that you want to import. 3. Click on the "Import" button. The import will start.
Result
The relevant tags have been created in WinCC. Alarms relating to the import operation are displayed in the output window. A log file is saved in the source directory of the import files. The log file has the same name as the respective import file but with the "*.xml" extension. Check when importing the data whether there are any links to objects, for example, dynamic parameters such as tags. If an object with the same name already exists, the existing object is used. If no object of the same name yet exists, create an object with the relevant name or create a new link. Note The syntax of the import file is checked during xlsx file import. The meaning of the properties or dependencies between the properties is not checked. It is possible to assign a tag a trigger tag of the wrong type, for example, string. An error will be reported during compilation.
See also
Exporting tags (Page 1325)
1327
Table 9-16 List entry Name Path PLC Tag Connection Data type
Meaning of the entries Meaning Indicates the configured name of an HMI tag. Specifies which folders in the project tree contain the tag. The folder structure is represented by "\" : "FolderName1\FolderName2\TagName". Indicates whether the tag is linked to a PLC tag. Indicates the name of the connection to the PLC. 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. 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.
Length
1328
1329
Meaning of the entries Meaning Indicates the configured name of an HMI tag which uses indirect addressing. The HMI tag must be available in the "HMI Tags" worksheet. Shows the value which governs which tag is selected. Displays the tag from the tag list corresponding to the index value.
Multiplex Tag
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 1325)
9.9.2.5
1330
Requirements
The WinCC project for the export is open. Text lists have been created in the project. The "Text & graphics lists" editor is open.
2. Click the "..." button and specify in which file the data are saved. 3. Click "Export". The export will start.
Result
The exported data has been written to an xlsx file. The xlsx file will be stored in the specified folder.
See also
Importing text lists (Page 1331) Importing and exporting project data (Page 1312) Exporting tags (Page 1325) Exporting recipes (Page 1314) Format of text list data (Page 1332)
Requirements
An xlsx file with text lists has been created. The structure of the xlsx file meets the requirements.
1331
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 1330)
1332
Meaning of the entries Meaning Shows the name of the text list. Shows the text list range: Number = Bit number (0-31) Range = value/range (...-...) Bit = Bit (0;1) Any comments on the text list. You can use up to 500 characters
Comment
1333
Meaning of the entries Meaning Shows the name of the text list entry. Specifies the name of the corresponding text list. Indicates whether the text list entry is a default entry. The default entry is always displayed when the tag has an undefined value. Specifies the tag integer values or value ranges which are assigned to the text entries in the text list. 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;>
1334
See also
Exporting text lists (Page 1330)
9.9.2.6
Requirements
At least two languages have been enabled in the "Project languages" editor, for example, Italian and French.
1335
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.
1336
See also
Importing project texts (Page 1337)
Requirements
At least two languages have been enabled in the "Project languages" editor, for example, Italian and French.
Result
You have imported the project texts.
See also
Exporting project texts (Page 1335)
1337
9.9.3
9.9.3.1
Using cross-references
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.
9.9.3.2
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.
1338
Result
The cross-reference list for the selected object is displayed in the work area.
9.9.3.3
Depending on the installed products, additional columns or different columns are displayed for the cross-references.
1339
9.9.3.4
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.
1340
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 Object Meaning Name of the object that uses the lower-level objects or that is being used by the lower-level objects. Number of uses Each location of use, for example an object or event Function of the referenced objects, for example tag for data record or process value PLC tag with which the object is connected. Type of object Path of object
Depending on the installed products, additional columns or different columns are displayed for the cross-references.
1341
9.9.4
9.9.4.1
Managing languages
Languages in WinCC
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.
1342
See also
Language settings in the operating system (Page 1343) Operating system settings for Asian languages (Page 1344) Selecting the user interface language (Page 1345) "Graphics" editor (Page 1356) Languages in Runtime (Page 1360) Example: Configuring a button for language switching (Page 1367)
9.9.4.2
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
See also
Languages in WinCC (Page 1342) Operating system settings for Asian languages (Page 1344)
1343
9.9.4.3
See also
Languages in WinCC (Page 1342) Language settings in the operating system (Page 1343)
1344
9.9.4.4
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 1345) Selecting the reference language and editing language (Page 1346) Languages in WinCC (Page 1342)
1345
See also
Selecting the user interface language (Page 1345) Selecting the reference language and editing language (Page 1346)
Requirements
The "Project languages" editor is open. Several project languages have been activated.
1346
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 1345) Enable project languages (Page 1345)
1347
9.9.4.5
See also
Project text basics (Page 1349) Translating texts directly (Page 1350) Translating texts using reference texts (Page 1352) Exporting project texts (Page 1353) Importing project texts (Page 1355)
1348
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.
1349
See also
Working with multiple languages (Page 1348) Translating texts directly (Page 1350) Translating texts using reference texts (Page 1352) Exporting project texts (Page 1353) Importing project texts (Page 1355)
Requirements
You are in the project view. A project is open. You have selected at least two further project languages.
1350
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 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.
1351
See also
Working with multiple languages (Page 1348) Exporting project texts (Page 1353) Project text basics (Page 1349) Importing project texts (Page 1355)
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 1348) Exporting project texts (Page 1353) Project text basics (Page 1349) Importing project texts (Page 1355)
1352
Requirements
At least two languages have been enabled in the "Project languages" editor, for example, Italian and French.
1353
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.
1354
See also
Working with multiple languages (Page 1348) Translating texts using reference texts (Page 1352) Translating texts directly (Page 1350) Project text basics (Page 1349) Importing project texts (Page 1355)
Requirements
At least two languages have been enabled in the "Project languages" editor, for example, Italian and French.
Result
You have imported the project texts.
1355
See also
Exporting project texts (Page 1353) Working with multiple languages (Page 1348) Project text basics (Page 1349) Translating texts directly (Page 1350) Translating texts using reference texts (Page 1352)
9.9.4.6
Work area
The work area displays all configured graphic objects in a table. There is a separate column in the table for each project language. Each column in the table contains the versions of the graphics for one particular language. In addition, you can specify a default graphic for each graphic to be displayed whenever a language-specific graphic for a project language does not exist.
Preview
The preview shows you how the graphics will look on various devices.
See also
Storing external graphics in the graphics library (Basic, Advanced, Professional) (Page 1358) Storing graphics in the graphics library (Basic, Advanced, Professional) (Page 1357) Languages in WinCC (Page 1342)
1356
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.
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.
1357
See also
"Graphics" editor (Page 1356)
Storing external graphics in the graphics library (Basic, Advanced, Professional) Introduction
To display graphics that have been created in an external graphics program in your screens, you will first have to store these graphics in the graphics browser of the WinCC project.
Requirement
Multiple languages have been enabled in the "Project languages" editor. The "Graphics" editor is open. There is a graphic in the "Graphics" editor.
1358
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 1356)
1359
9.9.4.7
Languages in runtime
See also
Methods for language switching (Page 1360) Enabling the runtime language (Page 1361) Setting the runtime language order for language switching (Page 1363) Setting the default font for a runtime language (Page 1365) Selecting the log language (Page 1366) Languages in WinCC (Page 1342)
1360
See also
Languages in Runtime (Page 1360) Selecting the log language (Page 1366) Enabling the runtime language (Page 1361) Setting the runtime language order for language switching (Page 1363) Setting the default font for a runtime language (Page 1365)
Requirements
Multiple languages have been enabled in the "Project languages" editor.
1361
Procedure
1. Double-click on "Runtime settings" in the project tree. 2. Click on "Language & Font". 3. Select the following languages: German Chinese French
Result
You have now set three runtime languages. A number is automatically assigned to each language in the "Order" column. The enabled runtime languages are transferred with the compiled project to the HMI device. If the number of languages selected exceeds the number that can be transferred to the HMI device, the table background changes color.
1362
See also
Languages in Runtime (Page 1360) Selecting the log language (Page 1366) Setting the runtime language order for language switching (Page 1363) Methods for language switching (Page 1360)
Requirements
Multiple languages have been enabled in the "Project languages" editor. "Language & Font" is open in the editor and three runtime languages have been set in the following order: 1. German 2. Chinese 3. French
1363
Procedure
1. Select the runtime language "German". button. The runtime language "German" will move down a place. The number 2. Click the 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 1360) Selecting the log language (Page 1366) Enabling the runtime language (Page 1361) Setting the default font for a runtime language (Page 1365) Methods for language switching (Page 1360)
1364
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 1360) Selecting the log language (Page 1366) Setting the runtime language order for language switching (Page 1363) Methods for language switching (Page 1360)
1365
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 1360) Setting the default font for a runtime language (Page 1365) Setting the runtime language order for language switching (Page 1363) Methods for language switching (Page 1360) Enabling the runtime language (Page 1361)
1366
9.9.4.8
Requirements
You have completed the "Configuring a button in multiple languages" example. The "Screen_1" screen is open. The button on the screen has been selected.
Procedure
1. In the Inspector window, select "Properties > Events > Press". 2. Click on "Add function" in the table. 3. Select the "SetLanguage" system function.
Result
You have assigned the button the function "SetLanguage". Pressing the button during runtime will switch the runtime language. The runtime languages are switched in the order specified by the number sequence in the "Languages and fonts" editor.
See also
Example: Configuring a button in multiple languages (Page 1367) Example: Configuring a button for language switching for each runtime language (Page 1368) Languages in WinCC (Page 1342)
1367
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 1367) Example: Configuring a button for language switching for each runtime language (Page 1368)
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.
1368
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 1367) Example: Configuring a button in multiple languages (Page 1367)
1369
9.9.5
9.9.5.1
Replacing devices
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 1371) Screen adjustment options (Page 1374) Key assignment when replacing devices (Page 1372) Engineering system (Page 1461) Basic Panel (Page 1463)
1370
9.9.5.2
Device-specific functions
See also
Basics (Page 1370)
1371
1372
1373
See also
Basics (Page 1370) Screen adjustment options (Page 1374)
9.9.5.3
None
The screens are not scaled. The objects in the screen retain their position and size. This option may result in objects being outside the configurable area if the display of the new device is smaller than the old one.
1374
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.
1375
See also
Specifying the position of screen objects (Page 1377) Fit objects to contents (Page 1376) Basics (Page 1370) Key assignment when replacing devices (Page 1372)
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:
1376
See also
Specifying the position of screen objects (Page 1377) Screen adjustment options (Page 1374)
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.
1377
See also
Fit objects to contents (Page 1376) Screen adjustment options (Page 1374)
9.9.6
9.9.6.1 Basics
1378
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.
See also
Unsupported objects and functionalities (Page 1379)
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.
1379
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.
See also
Basics (Page 1378)
9.9.6.2
1380
See also
Copying recipes within an HMI device (Page 1381) Copying objects with linked objects (Page 1382) Linked objects copied automatically (Page 1382)
"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 1380) Copying objects with linked objects (Page 1382) Linked objects copied automatically (Page 1382)
1381
Simple pasting
The linked object is not copied. The linked object is transferred and handled as follows in the target HMI device: If an object with the same name exists, the existing object with its settings is used. If no object with the same name exists, the name of the object will be displayed. The object becomes invalid. For some objects, linked objects are pasted automatically during simple pasting.
Extended pasting
Select the "Extended paste" command in the shortcut menu to paste the linked objects as well. If objects of the same name exist in the target HMI device, you need to decide whether or not to overwrite each of these objects.
See also
Copying screens (Page 1380) Copying recipes within an HMI device (Page 1381)
1382
See also
Copying screens (Page 1380) Copying recipes within an HMI device (Page 1381)
1383
9.10
9.10.1
9.10.1.1 Overview
The project is compiled in the background even as you are configuring it in WinCC. This reduces the time for final compilation. When you start compilation, you create a file that can be run on the corresponding HMI device. If an error occurs during compilation, WinCC provides support in locating and correcting it. Once you have corrected any problems, you download the compiled project to the HMI devices on which the project is to run. If 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:
1384
9.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.
1385
Requirement
A project is open.
Procedure
Proceed as follows to compile a project: 1. If you want to compile several HMI devices at the same time, select all the relevant HMI devices with multiple selection in the project tree. 2. Compile the project: For delta compilation of the project, select the "Compile > Software" command from the shortcut menu of the HMI device. To compile all project data, select the "Compile > Software (compile all)" command from the shortcut menu.
Result
The configuration data of all selected HMI devices is compiled. Any errors that occur during compilation are shown in the Inspector window.
9.10.1.3
Loading projects
1386
1387
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.
1388
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. If errors or warnings occur during the download, corresponding alarms are displayed under "Info > Load" in the Inspector window. On completion of the successful download of the project, you can execute it on the HMI device.
See also
Backing up and restoring data of the HMI device (Page 1397) Updating the HMI device operating system (Page 1399) Error messages during loading of projects (Page 1401) Adapting the project for another HMI device (Page 1402) Establishing a connection to the HMI device (Page 1404)
9.10.1.4
Runtime start
1389
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".
9.10.2
9.10.2.1
Simulating projects
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:
1390
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 1392)
1391
9.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.
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".
1392
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:
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.
1393
See also
Simulation basics (Page 1390) Working with the tag simulator (Page 1394)
9.10.2.3
Simulation modes
The simulator has six different simulation modes. The configured tags are supplied with nearly realistic values during the simulation.
Simulation mode Sinusoidal Random Increment Description Changes the tag value to form a sinusoidal curve. The value is visualized as a periodic, non-linear function. Provides randomly generated values. The tag value is changed by means of a random function. 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. 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.
Decrement
1394
Result
The simulator tests the selected tag bit-by-bit as follows:
Simulation values Set start value 1. Simulation value 2. Simulation value 3. Simulation value .... Byte for alarms 00000001 00000010 00000100 00001000 ...
See also
Simulating a project (Page 1392)
1395
9.10.3
9.10.3.1
Introduction
The "ProSave" service tool is installed by default when WinCC is installed. The ProSave functions are called in WinCC with the menu "Online > HMI device maintenance".
Functional scope
ProSave provides all of the functions 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 1396) Updating the operating system (Page 1398)
9.10.3.2
Introduction
Regular backups of the data of an HMI device reduces downtimes to a minimum, e.g. when you replace a device. You simply transfer the backup data to the HMI device and therefore restore the original state.
1396
See also
Backing up and restoring data of the HMI device (Page 1397) ProSave (Page 1396)
9.10.3.3
Requirements
The HMI device is connected to the configuration PC The HMI device is selected in the project navigation. If a server is used for data backup: The configuration PC has access to the server
1397
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 1396)
9.10.3.4
Introduction
If the operating system version on an HMI device is incompatible with the configuration, the operating system on the HMI device will be updated automatically (following a prompt) when the project is loaded. Loading will then continue. Loading will otherwise be aborted.
1398
See also
Updating the HMI device operating system (Page 1399) ProSave (Page 1396)
9.10.3.5
Requirements
The HMI device is connected to the configuration PC or the PC with ProSave. The HMI device is selected in the project navigation.
1399
Result
The operating system of the HMI device is updated to the latest version.
See also
Updating the operating system (Page 1398)
1400
9.10.4
9.10.4.1
Reference
Error messages during loading of projects
1401
9.10.4.2
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.
1402
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.
1403
9.10.4.3
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.
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.
1404
9.11
9.11.1
9.11.1.1
Operating in Runtime
Basics
Overview
Figure 9-1
1405
9.11.1.2 Definition
Tags in Runtime
Tags correspond to defined memory areas on the HMI device, to which values are written and/ or from which values are read. This action can be initiated by the PLC, or by the operator at the HMI device.
9.11.1.3 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.
1406
9.11.2
9.11.2.1
Commissioning projects
Settings in the Runtime software
Open the WinCC configuration software and make the following settings for the runtime software:
Dialog fonts
The dialog text will be shown in the standard font. Define the default font under "Language & Font" in the "Device Settings" editor.
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.
1407
9.11.2.2 Overview
Loading projects
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.
1408
9.11.2.3
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.
1409
9.11.2.4
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" All other HMI devices: "*.fwc" The project settings defined in the "Runtime settings" of the HMI device are activated when the project is started in Runtime. The programs that you can use to start projects on the HMI device are available in the Runtime installation folder.
Requirements
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".
9.11.2.5
Testing a project
Introduction
You have the following options for testing a WinCC project:
1410
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".
9.11.2.6
Closing a project
Introduction
You define the steps in closing Runtime in the user program:
1411
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.
9.11.2.7
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.
1412
9.11.3
9.11.3.1
Languages in runtime
Languages in runtime
9.11.3.2
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.
1413
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.
9.11.3.3
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.
1414
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.
9.11.3.4
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.
1415
9.11.3.5
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.
1416
9.11.4
9.11.4.1
Operating projects
Basics
1417
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.
1418
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
1419
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.
1420
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.
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.
1421
1422
Procedure
Proceed as follows to open the tooltip for operator controls: 1. Touch the required operating element. The screen keyboard opens. The representation of the key indicates whether a tooltip was configured for the operating element or for the current screen. 2. Touch the key of the on-screen keyboard. The tooltip for the operating element is displayed. If there is no tooltip for the selected screen object, the tooltip for the current screen is displayed if it has been configured. You can scroll through the contents of long tooltips using the and buttons. Note Switching between displayed tooltips The configuration engineer can configure 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.
1423
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.
Operating objects
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.
1424
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
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.
1425
Key operation
according to the configured Activate the date/time field, for example, with one or several 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. . The object changes to the special editing mode. Only one character at any time 2. Press 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
1426
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.
1427
Key operation
according to the tab sequence Activate the IO field,for example, with one or several 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. . The object will change to special editing mode. Only one character at any time 3. Press is marked in the field. Use the cursor keys Use the cursor keys 4. Confirm your entry 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 . / / to scroll a character table. to move the cursor to the next or previous input position. .
, or discard it with
1428
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.
1429
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.
1430
Key operation
How to use a graphic IO field on the keyboard device:
Step 1 2 3 4 Select the graphic IO field Enable the selection mode Select an entry Accept selection or Cancel selection
ESC
ENTER
Procedure e.g.
ENTER
The graphic IO field is marked. The selection mode is now enabled. Moves the cursor by lines. The entry selected is now valid. The selection mode is closed. The original value is restored.
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.
1431
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
Procedure
Select the trend view with the
TAB
1432
Function Scrolls back to the start of trend recording. The start values of the trend recording are displayed there. Enlarges the time section displayed. Reduces the time section displayed.
ALT ALT
+ + + + + +
+ +
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).
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.
1433
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.
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.
1434
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.
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.
1435
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.
Key operation
How to operate a symbolic IO field on the keyboard device:
Step 1 2 3 4 Select the symbolic IO field Open selection list Select an entry Accept the selection Or Canceling the selection
ESC
ENTER
Procedure e.g.
ENTER
The symbolic IO field is marked. The drop down list box opens. Moves the cursor by lines. The entry selected is now valid. The selection list is closed. The original value is restored. The selection list is closed.
1436
9.11.4.3 Overview
Project security
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.
1437
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.
1438
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.
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.
1439
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.
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.
1440
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.
1441
1442
Result
User data have been changed.
Result
The user has been deleted and may no longer log onto the project.
1443
Operating 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.
1444
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.
1445
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.
1446
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 ! (empty) (depends on the configuration) $ Alarm class "Errors" "Warnings" 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
1447
Alarm indicator
The alarm indicator is a graphic symbol indicating pending alarms or alarms requiring acknowledgment, depending on the configuration.
Figure 9-2
1448
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.
1449
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.
Requirement
The alarm to be edited is displayed in the alarm window or the alarm view.
1450
. keys.
END
or
3. Continue to press the key TAB until the button in the extended alarm view. 4. Confirm your entry by pressing the key
ENTER
Result
The system executes the additional functions of the alarm. Additional information on this topic may be available in your plant documentation.
9.11.4.5
Operating recipes
1451
Recipe data records
Recipes for a fruit juice plant Orange flavored drinks Grape flavored drinks Apple flavored drinks Cherry flavored drinks
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
folder Suspension folder Suspension folder
Recipe Product variants of apple flavored drinks Recipe data record Apple drink Recipe data record Apple nectar Recipe data record Apple juice
1452
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.
1453
Data flow
The following figure shows the data flow in a project with recipes:
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
1454
Figure 9-3
In the simple recipe view, each area is shown separately on the HMI device. You can use the shortcut menu to operate each of these display areas. The simple recipe view always begins with the recipe list.
Operation
You 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
1455
Element list
Menu command Save To PLC From PLC Save as Displaying infotext Rename Previous Keys Function The selected record is renamed. The displayed values of the selected data record are transferred from the HMI device to the PLC. The recipe values from the PLC are displayed in the recipe view of the HMI device. The data record is saved under a new name. A dialog box opens where you can enter the name. Displays the infotext configured for the simple recipe view. Renames the selected data record. A dialog box opens where you can enter the name. The data record list opens.
1456
6. Alternatively, press the number of the desired menu command. The menu command is executed.
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.
1457
Result
The new recipe data record is saved to the selected recipe.
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".
1458
Result
The edited recipe data record is saved to the selected recipe.
Requirement
A screen with a simple recipe view is displayed.
Result
The data record is deleted.
1459
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.
1460
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.
9.12
9.12.1
Performance features
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.
1461
35 80.000 8.000
3)
Number of logging tags Number of blocks (faceplates, user data types) Number of screens Number of screen objects per screen Number of screen objects Number of alarms Number of texts
3) 2) 3)
Number of text lists and graphic lists 3) Number of entries per text list Number of languages Number of global libraries
3)
1) 2) 3)
Including logging tags. With an average of 5 texts and a dynamic parameter Including the objects configured in the "Program PLC" area
80.000 8.000 500 1000 3.000 320.000 30.000 50.000 1.000 500 20.000 1.000 10.000 100.000 1.000 3.000
Number of recipes Number of recipe elements Number of texts Number of text lists and graphic lists Number of entries per text list
1462
1) 2)
9.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 Number of tags in the project Number of PowerTags Number of elements per array Number of local tags 250 -100 -KP400 Basic 500 -100 -KTP400 Basic 250 -100 -KTP600 Basic 500 -100 -KTP1000 Basic 500 -100 -TP1500 Basic 500 -100 --
Alarms
KP300 Basic Number of alarm classes Number of discrete alarms Number of analog alarms 32 200 15 KP400 Basic 32 200 15 KTP400 Basic 32 200 15 KTP600 Basic 32 200 15 KTP1000 Basic 32 200 15 TP1500 Basic 32 200 15
1463
Screens
KP300 Basic Number of screens Number of fields per screen Number of tags per screen Number of complex objects per screen 1) Number of array elements per screen 2) 50 30 30 5 100 KP400 Basic 50 30 30 5 100 KTP400 Basic 50 30 30 5 100 KTP600 Basic 50 30 30 5 100 KTP1000 Basic 50 30 30 5 100 TP1500 Basic 50 30 30 5 100
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 Number of recipes Number of elements per recipe1) User data length in bytes per data record Number of data records per recipe Reserved memory for data records in the internal Flash 5 20 -20 40 KB KP400 Basic 5 20 -20 40 KB KTP400 Basic 5 20 -20 40 KB KTP600 Basic 5 20 -20 40 KB KTP1000 Basic 5 20 -20 40 KB TP1500 Basic 5 20 -20 40 KB
1)
If arrays are used, each array element counts as one recipe element
Logs
KP300 Basic Number of logs Number of entries per log (including all log segments) 1) --KP400 Basic --KTP400 Basic --KTP600 Basic --KTP1000 Basic --TP1500 Basic ---
1464
1)
The number of entries for the "segmented circular log" logging method is the maximum number for all segmental circular logs. The product of the number of segmental circular logs and the number of data records per segmental circular log may not exceed the system limit.
Trends
KP300 Basic Number of trends 25 KP400 Basic 25 KTP400 Basic 25 KTP600 Basic 25 KTP1000 Basic 25 TP1500 Basic 25
Scripts
KP300 Basic Number of scripts -KP400 Basic -KTP400 Basic -KTP600 Basic -KTP1000 Basic -TP1500 Basic --
Communication
KP300 Basic Number of connections 4 Number of connections based on "SIMATIC -HMI HTTP" KP400 Basic 4 -KTP400 Basic 4 -KTP600 Basic 4 -KTP1000 Basic 4 -TP1500 Basic 4 --
1465
Help system
KP300 Basic Number of characters in a help text 320 KP400 Basic 320 KTP400 Basic 320 KTP600 Basic 320 KTP1000 Basic 320 TP1500 Basic 320
Languages
KP300 Basic Number of runtime languages 5 KP400 Basic 5 KTP400 Basic 5 KTP600 Basic 5 KTP1000 Basic 5 TP1500 Basic 5
Scheduler
KP300 Basic Time-triggered tasks 1) -KP400 Basic -KTP400 Basic -KTP600 Basic -KTP1000 Basic -TP1500 Basic --
1)
User administration
KP300 Basic Number of user groups Number of authorizations Number of users 50 32 50 KP400 Basic 50 32 50 KTP400 Basic 50 32 50 KTP600 Basic 50 32 50 KTP1000 Basic 50 32 50 TP1500 Basic 50 32 50
Project
KP300 Basic Size of the project file "*.srt" 512 kB KP400 Basic 512 kB KTP400 Basic 512 kB KTP600 Basic 512 kB KTP1000 Basic 1024 kB TP1500 Basic 1024 kB
1466
9.12.3
9.12.3.1
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)
9.12.3.2
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.
1467
9.13
9.13.1
1468
9.13.2
Libraries
WinCC flexible enables you to create two library types: Project library Global library A library can contain all the WinCC flexible objects, such as screens, tags, graphic objects, or alarms.
1469
Both the "Project library" and the "Global library" contain the two folders, "Copy templates" and "Types". You can create or use the library objects as a copy template, or as a type. Copy templates Use copy templates to create independent copies of the library object. Types Create instances of objects of the "Types" folder and use the instances in your project. The instances are bound to their respective type. Changes to an instance also change all other instances. Types are marked by a green triangle in the "Libraries" task card. Managing the library objects You can only copy and move library objects within the same library. For more detailed information, see: Libraries in WinCC (Page 724)
1470
9.13.3
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.
1471
Excluding the controls, the screens are displayed in runtime in the following order:
1472
10
Online mode
In online mode, there is an online connection between your programming device / PC and one or more devices. An online connection between the programming device/PC and the device is required, for example, for the following tasks: Testing user programs Displaying and changing the operating mode of the CPU Displaying and setting the date and time of day of the CPU Displaying module information Comparing blocks Hardware diagnostics Before you can establish an online connection, the programming device/PC and the device must be physically or remotely connected. As an alternative, some devices support a simulation mode. In this case, a connection to the device is simulated via the PLCSIM virtual interface. After establishing a connection, you can use the Online and Diagnostics view or the "Online tools" task card to access the data on the device. The current online status of a device is indicated by an icon to the right of the device in the project tree. You will find the meaning of the individual status icons in the relevant tooltip. Note Some online functions depend on the range of the installed software or whether a project is open.
1473
Using online and diagnostics functions 10.1 General information about online mode
See also
View in online mode (Page 1475)
1474
10.2
Online displays
After the online connection has been established successfully, the user interface changes. The following figure shows a device connected online and the corresponding user interface:
The title bar of the active window now has an orange background. The title bars of inactive windows for the relevant station now have an orange line below
them. An orange, pulsing bar appears at the right-hand edge of the status bar. If the connection has been established but is functioning incorrectly, an icon for an interrupted connection is displayed instead of the bar. You will find more information on the error in "Diagnostics" in the Inspector window.
1475
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.
See also
General information about online mode (Page 1473) Basics of project data comparison (Page 194)
10.3
Online access
1476
"Online access" folder in the project tree All interfaces installed in the programming device/PC are displayed in the "Online access" folder. 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.
1477
See also
Opening the properties of an interface (Page 1480)
10.4
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.
1478
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.
1479
Using online and diagnostics functions 10.6 Establishing and canceling an online connection
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.
10.5
Introduction
For each interface, you can display and, in some cases, modify properties, for example the network type, address, and status.
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.
10.6
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.
1480
Using online and diagnostics functions 10.6 Establishing and canceling an online connection
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. 5. In the "Connection to subnet" drop-down list, select the subnet via which the device is connected to the PG/PC interface. If the device is connected directly to the PG/PC interface, select the "(local) TCP/IP" setting. In this case, a direct connection is established to the device, without a network node, for example, an interposed switch. 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 a list. 7. Optional: Click the "Update" button to redisplay the list of accessible devices. 8. Optional: Click the "Flash LED" button on 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 "Accessible devices in the 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.
1481
Using online and diagnostics functions 10.7 Connecting online with several devices
See also
Connecting online with several devices (Page 1482) View in online mode (Page 1475) Assigning a temporary IP address (Page 1487) Influence of user rights (Page 163)
10.7
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 "Go online" command in the "Online" menu. The "Select devices" dialog opens with a table of all available devices. 2. Select the devices to which you want to establish an online connection in the "Go online" column. 3. 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 disconnect online connection (Page 1480)".
See also
Establishing and canceling an online connection (Page 1480) Assigning a temporary IP address (Page 1487)
1482
10.8
See also
Setting parameters for the Industrial Ethernet interface (Page 1484) Setting parameters for the MPI and PROFIBUS interfaces (Page 1489)
10.9
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.
1483
Using online and diagnostics functions 10.10 Setting parameters for the Ethernet interface
Result
The newly installed interface is now displayed in the project tree under the "Online access" folder.
10.10
10.10.1
1484
Using online and diagnostics functions 10.10 Setting parameters for the Ethernet interface
See also
Basics of assigning parameters for the PG/PC interface (Page 1483) Displaying operating system parameters (Page 1485) Connecting the PG/PC interface to a subnet (Page 1486) Setting parameters for the Ethernet interface (Page 1486) Assigning a temporary IP address (Page 1487) Managing temporary IP addresses (Page 1487) Influence of user rights (Page 163)
10.10.2
See also
Setting parameters for the Ethernet interface (Page 1486)
1485
Using online and diagnostics functions 10.10 Setting parameters for the Ethernet interface
10.10.3
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. 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".
10.10.4
Requirement
You must have adequate user rights. See also: Influence of user rights (Page 163).
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.
1486
Using online and diagnostics functions 10.10 Setting parameters for the Ethernet interface
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 163) Displaying operating system parameters (Page 1485)
10.10.5
See also
Managing temporary IP addresses (Page 1487)
10.10.6
1487
Using online and diagnostics functions 10.10 Setting parameters for the Ethernet interface
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. 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 163)
10.10.7
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.
1488
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
10.11
10.11.1
See also
Basics of assigning parameters for the PG/PC interface (Page 1483)
1489
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
10.11.2
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.
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 1490) Setting parameters for the PROFIBUS interface (Page 1492)
10.11.3
1490
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
1491
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
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. 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 1490)
10.11.4
1492
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
1493
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
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. 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.
1494
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
See also
Overview of the bus parameters for PROFIBUS (Page 1495) Setting MPI or PROFIBUS interface parameters automatically (Page 1490)
10.11.5
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.
1495
Using online and diagnostics functions 10.11 Setting parameters for the MPI and PROFIBUS interfaces
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.
See also
Setting parameters for the PROFIBUS interface (Page 1492)
10.11.6
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.
1496
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
10.12
10.12.1
Scope of functions
TeleService allows you to use the range of TIA portal functions via a telephone network by establishing a remote connection to a remote system. The online connection allows you to edit a remote system in the usual way 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 1498)
1497
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
See also
Basics of using a TS adapter (Page 1502) Supported telephone networks and modems (Page 1499)
1498
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
You can enter any number of plants 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. The respective TS adapters used are distinguished by color, depending on if a TS Adapter MPI or a TS Adapter IE is used for establishing the connection.
See also
Working with the phone book (Page 1523)
10.12.2
10.12.2.1 Supported telephone networks and modems Telephone networks which can be used
TeleService can be used with digital networks (ISDN), analog networks and radio networks (with GSM technology). The table below shows the transmission duration scaled to the transmission duration of the MPI card (CP 5611 = 1x) and as a function of the TS Adapter MPI used:
Connection: Direct connection (COM, 19.2 Kbps) Direct connection (USB) ISDN network (64 Kbps) Analog network (28.8 Kbps) Radio network (9.6 Kbps) with TS Adapter I V5.0: 8x 16 x 32 x 150 x with TS Adapter I V5.1/V5.2: 8x 11 x 14 x 40 x with TS Adapter II V1.0: 2.5 x 8x 11 x 30 x
Restrictions
Communication with the TS Adapter via the CAPI interface is not possible with internal ISDN cards or with PCMCIA cards unless you have a virtual COM interface from the modem manufacturer.
Modem support
TeleService has been implemented to be independent of the modem. This means that all standard modems (Hayes-compatible/AT commands) which can be installed in the Windows Control Panel can also be used by TeleService. The basic requirement is for a physical/virtual COM interface. The choice of modem type is determined primarily by the existing hardware of the programming device/PC and the telephone network to be used.
1499
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
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.
1500
Using online and diagnostics functions 10.12 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.
1501
Using online and diagnostics functions 10.12 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.
10.12.3
1502
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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". The figure below shows how a remote connection can be established with variousTS Adapter:
Figure 10-1
You can choose between a number of different TS Adapters, each of which offers a different functionality and different connection options.
See also
Short description of the TS adapter MPI (Page 1504) Short description of the TS adapter IE (Page 1511) Exporting adapter parameters (Page 1510) Importing adapter parameters (Page 1510)
1503
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
10.12.3.3 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 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 I Direct connection via the serial port. The firmware cannot be replaced. Version: V3.0 V5.0 V5.1 V5.2 TS Adapter II: Direct connection via the Universal Serial Bus (USB). Replaceable firmware. Modem integrated or external. 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. Main expansions: Access protection Access protection, network type AUTO Access protection, network type AUTO, sending SMS messages
1504
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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 The serial port to the modem Access protection
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 assigned 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.
1505
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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 the TS adapter MPI in the TIA portal As soon as you have connected a TS adapter MPI with the PG/PC via the UBS interface, the folder "TS adapter" is displayed in the project navigation. When you open the folder, you can assign the parameters of the connected TS adapter MPI via the following dialog.
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. You can then work with the selected system as usual, with the TIA portal, over the established modem connection.
1506
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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 1508) Restoring default parameter assignment (Page 1509) Importing adapter parameters (Page 1510) Exporting adapter parameters (Page 1510) Setting up access protection (Page 1518)
1507
Using online and diagnostics functions 10.12 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.
Requirement
A TS Adapter MPI is connected to your computer and the folder "TS adapter" is displayed in the project tree under "Online access".
1508
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Procedure
To assign the parameters for the TS Adapter MPI im Direktanschluss please proceed as follows: 1. In the project tree, double-click on the "TS adapter" folder under "Online access". 2. Select the command "Assign TS Adapter MPI parameters". The "Assign TS Adapter MPI parameters" dialog opens. 3. Set the desired parameters in the individual tabs of the dialog. 4. 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.
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".
Result
The TS Adapter MPI default parameters set on delivery are restored.
See also
TS adapter MPI configuration options (Page 1507)
1509
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
1510
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
1511
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
TS Adapter IE Basic: Direct connection over Industrial Ethernet (IE). Replaceable firmware. 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.
1512
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
Figure 10-2
Direct connection
Figure 10-3
1513
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
More information about the TS modules can be found in the TS Adapter modular manual.
Figure 10-4
More information about the TS modules can be found in the TS Adapter modular manual.
Figure 10-5
More information about the TS modules can be found in the TS Adapter modular manual.
1514
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
Requirement
There is a LAN connection to your TS Adapter IE Basic. The TS Adapter IE Basic is connected to the power supply.
Procedure
To assign the parameters for the TS Adapter IE please 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.
1515
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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 node list. 7. Double-click the command "Assign TS adapter IE parameters". The allocated web-interface opens for assigning the TS adapters IE parameter. 8. Complete the "logon" for the web interface. 9. Set the desired 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.
10.12.4
1516
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
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.
1517
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Level of access protection 1 2 Administrator/User password enter enter Callback number do not enter enter
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 1 2 Administrator/User password enter enter Callback number do not enter or enter any callback number 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.
10.12.4.4 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.
1518
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
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).
1519
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
5. Select the telephone network under "Network" 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. 10.Click the "Dial" button to establish the desired remote connection. This button only becomes active when you have entered all the parameters needed establishing 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.
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.
1520
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
10.12.5
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.
Proceed as follows:
1. In the project tree of the TIA Portal, open the "Online access" folder. 2. Then click the "TeleService" folder contained within. 3. Double-click the "Set up/close remote connection" entry. The "Set up remote connection to the remote system" dialog opens. 4. Select the adapter type used in the "TS Adapter" drop down list. 5. Select the telephone network under "Network". 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 the your user name and associated password. 9. If you want a "Connection setup with callback", select the appropriate option button. 10.Click the "Dial" button to establish the desired remote connection. This button only becomes active when you have entered all the parameters needed establishing a remote connection. Any remote connection is displayed under "Status".
Result
The remote connection to the desired plant is established. In "Status" the progress of establishing the connection is displayed: First "Select", then "Authenticate". The dialog closes once the remote connection is established. The message appears in the TIA portal status line: "Remote connection is established". You can now use the remote connection with TIA portal and communicate with the automation system.
1521
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
10.12.5.2 Terminating a remote connection To disconnect an active remote connection, proceed as follows:
1. Double-click the "Set up/close remote connection" entry.
Result
The connection will be terminated immediately. "Offline" status will be displayed in the status row again once the remote connection has been terminated. Note You should go offline in the TIA Portal before you terminate the remote connection.
1522
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
10.12.6
10.12.6.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 using the buttons in the toolbar. Note Access to phone books The phonebook is user specific in TeleService. However, it is not possible to access the global telephone book with more than one instance of the TIA portal at the same time.
1523
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
See also
Open phone book (Page 1525) Saving phone book (Page 1525) Importing phone book data (Page 1525) Exporting phone book data (Page 1526) Printing the phone book (Page 1527)
1524
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
10.12.6.4 Manage phone book Open phone book Opening phone books
To open the phone book, proceed as follows: 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 desired plant data.
1525
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Requirement
You have already created an import-capable phone book file under TeleService.
Procedure
Proceed as follows to import the phone book data: 1. Open the "TeleService" folder in 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" when applicable, and specify the location for storing the phone book in the dialog that follows. 5. If you do not want save the current state of the phone book, answer the prompt with "No". In the subsequent dialog, select the phone book file to which in 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.
Requirement
You have already created a phone book under TeleService with the corresponding plant 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, select where the current phone book is to be exported. 5. Close the dialog box with "OK".
1526
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Result
The exported phone book data are saved in the specified export file.
Proceed as follows:
1. Open the telephone 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.
10.12.7
1527
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Communications instruction "AS_DIAL": Establish remote connection to AS Communications instruction "AS_MAIL": Transfer email
10.12.7.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.
1528
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Figure 10-6
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. 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.
1529
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
10.12.7.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.
1530
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Figure 10-7
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.
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
1531
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
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.
Figure 10-8
10.12.7.4 Send SMS from a system Requirements for sending an SMS Introduction
Certain hardware and software requirements must be fulfilled before a plant can send an SMS. These requirements are detailed below.
Hardware requirements
To send an SMS from a plant, you will require a GSM radio modem and a TS Adapter MPI. A TS Adapter I, version V5.2 or later, or a TS Adapter II must be used.
1532
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
communication instructions folder of the Task Card under TeleService. If a plant is to send an SMS, the user program of the plant must call the communication instruction "SMS_SEND".
Figure 10-9
10.12.7.5 Send an email from a system Requirements for sending e-mails Introduction
The following hardware and software requirements must be fulfilled if a plant is to send an email:
Hardware requirements
To send e-mail from a plant, you will need a TS Adapter IE and a CPU 31x2 PN/DP, firmware version V2.5 or higher, or a CPU 41x-3 PN/DP.
1533
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
The "Use gateway/router" property must also be set for the Ethernet interface in the configuration of the CPU on which the communication instruction "AS_MAIL" runs. (See: Hardware configuration > PROFINET IO (PN-IO) > General > Properties > Parameters). The IP address of the Ethernet interface of the TS Adapter IE should be specified as the "Address".
1534
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
10.12.8
Troubleshooting
See also
Remote connection to the TS adapter is not established (Page 1536) Remote connection from the TS adapter is not established (Page 1537) Modem connection is interrupted (Page 1538) Modem alarms (Page 1539) Recording a log file for the modem (Page 1535)
1535
Using online and diagnostics functions 10.12 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.
10.12.8.3 Remote connection to the TS adapter is not established Remote 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 Cabling faulty Dial parameters for main telephone line and extension incorrectly set Check/Remedy Are all the connecting cables connected correctly? Are the connectors loose? Are the modem properties and dial parameters set for your modem correct for the phone connection (main telephone 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.
1536
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Possible cause Dial disable active Check/Remedy 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 1535) (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? Familiarize yourself with the modem initialization string requirements and set the string accordingly. Procedure for configuring the TS Adapter IE (Page 1512) Adapt the modem settings. Useful information on configuring the TS Adapter MPI (Page 1507) Restoring the default parameter assignment of a TS Adapter MPI (Page 1509) Procedure for configuring the TS Adapter IE (Page 1508)
Initialization string of the TS Adapter is not suitable for the modem. Settings for error correction between the modem at the TS Adapter and the modem at the PC/programming device are not compatible.
10.12.8.4 Remote 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 Errors in the location or call settings in the TS Adapter Check/Remedy 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: 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 Callback number is incorrect Check the configuration of the callback number you assigned.
1537
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
Set the modem initialization string in accordance with the following requirements: For further details, see: Requirements of the modem initialization string for TS Adapter MPI Options for the process of assigning parameters for the TS Adapter IE
1538
Using online and diagnostics functions 10.12 Establishing a remote connection with TeleService
See also
Initialization string requirements (Page 1502) TS adapter MPI configuration options (Page 1507) TS Adapter IE parameter assignment options (Page 1515)
Try again later. Refer to the modem documentation for information on how the dial disable function is implemented for your modem and if necessary remove it.
1539
Index
Absolute Addressing of a tag, 768, 1042 Access protection, 918 Access protection level 1, 1517 Access protection level 2, 1517 Advantages, 1517 Configuring, 922 Factory state, 1516 User administration, 917 Validity, 1516 Access to phone books, 1523 Accessible devices, 462, 1067, 1117 ACK, 1448 Acknowledge, 808, 1004, 1007 Alarm, 1450 Error alarm, 1450 AcknowledgeAlarm, 967 Acknowledgment, 810 Configuring, 834, 835, 836 Acknowledgment concept Alarm with simple acknowledgment, 812 Alarm without acknowledgment, 812 Acknowledgment model, 812 Acquisition cycle Area pointer, 1047 Tag, 784, 791, 801 Acquisition mode Tag, 784 Actions Basics of redoing actions, 215 Basics of undoing, 215 Redoing, 218 Undoing, 217 Activate Project language, 1346 ActivateCleanScreen, 943 ActivatePreviousScreen, 944 ActivateScreen, 941 ActivateScreenByNumber, 942 Active Area pointer, 1047 Adapting a project For a different HMI device, 1403 Add Objects to the group, 668 Additional field devices (PROFIBUS and PROFINET), 438, 465
add external graphic , 1358 add graphic to graphics library, 1357 Compiling Project, 1385 Connection parameter assignment General, 341 Module Inserting, 292 SetColorBackgroundLighting, 983 SIMATIC PC station Load, 52 STARTUP Warm restart, 499 Zoom in/out, (See Zoom)
"
"WWW" instruction, 408
*
*.bmp, 662 *.emf, 662 *.gif, 662 *.ico, 662 *.jpeg, 662 *.jpg, 662 *.tif, 662 *.wmf, 662
:
:P, 510
3
32-bit down counter, 564
A
Ability to read back connection parameters, 356
1541
Index
Address Area pointer, 1047 Mitsubishi, 1242 Omron Host Link, 1291 Address multiplexing with absolute addresses, 792 with symbolic addresses, 792 Address packing, 432 Address range Changing, 386 Addresses Assigning, 387 Interrupt with packed, 436 Pack, 432 Unpack, 432 Addressing, 510 Addressing tags indirectly, 788, 789 Allen-Bradley Ethernet IP, 1199 Changing, 386 General, 385 MPI, 1133 Multiplexing, 788 Adjust, 1001 AdjustContrast, 940 Admin, 1443 Alarm Acknowledge, 1450 Components, 813 Configuring, 819, 825 Displaying, 748 Editing, 1450 Exporting, 1317 Importing, 1319 in Runtime, 1444 In runtime, 837 Inspector window, 42 System function, 842 Alarm buffer in Runtime, 1445 In runtime, 838 Alarm buffer overflow, 1006 Alarm class, 813 in Runtime, 1444 In runtime, 837 Layout, 839, 1447 Alarm classes, 809 Custom, 809 Name change through migration, 99 Predefined, 809 Use, 809
Alarm display, 491 "Active alarms" view, 493 Acknowledging an alarm, 495 Archive view, 492 Clear archive, 493 Export archive, 493 Ignoring alarms, 495 Layout of the alarms in the "Active alarms" view, 494 Layout of the alarms in the archive view, 492 Receiving alarms, 493 Using the keyboard, 496 Alarm event Acknowledge, 808 Incoming, 808 Outgoing, 808 Alarm group, 812, 814 Configuring, 817 Creating, 817 Migration, 98 Alarm indicator, 42, 753, 828, 840, 1448 Alarm classes, 754 Application, 840 Configuring, 832 Events, 754 in Runtime, 1446 In runtime, 838 Layout, 754, 841 Operation, 841 Alarm log in Runtime, 1445 Alarm message Acknowledgment by the PLC, 1093, 1149, 1188, 1229, 1255, 1281, 1295 Acknowledgment on the HMI device, 1094, 1149, 1188, 1230, 1255, 1281, 1296 Configure acknowledgment, 1093, 1149, 1188, 1229, 1254, 1281, 1295 Alarm number, 813 Alarm status, 814 Acknowledged, 808 Incoming, 808 Outgoing, 808 Alarm system, 805 Alarm text, 814 Formatting, 823 Output fields, 46 Removing format settings, 823 Special characters, 46 Alarm types, 806
1542
Index
Alarm view, 42, 748, 751, 828, 840, 1448 Alarm text window, 840, 1448 Column, 750 Configuring, 830 Configuring the layout, 831 Control element, 750 Layout, 749, 839, 1447 Operation, 840, 1448 Alarm window, 42, 828 Configuring, 832 in Runtime, 1446 In runtime, 838 Alarm with simple acknowledgment, 812 Alarm without acknowledgment, 812 Alarms Output of a tag value, 822 AlarmViewAcknowledgeAlarm, 966 AlarmViewEditAlarm, 965 AlarmViewShowOperatorNotes, 967 AlarmViewUpdate, 966 Align Object flush, 652 Allen-Bradley, 1190, 1213, 1214 Allen-Bradley DF1 communication driver, 1213, 1214 Analog alarm, 1228 Basic Panel, 1051 Communication drivers, 1191 Data type, 1228 DF1, 1191 EtherNet/IP, 1191 Mitsubishi, 1254 Allen-Bradley Area pointer, 1226 Allen-Bradley DF1 Configuring a connection, 1208 Connection, 1208, 1212 Connection parameters, 1210 CPU type, 1223 KF2 module, 1213, 1214 KF3 module, 1213, 1214 Migrating data types, 111 Valid data type, 1221 Allen-Bradley Ethernet IP Address multiplexing, 1203 Addressing, 1199 Addressing type, 1201 Migrating data types, 111 Allen-Bradley EtherNet/IP Configuring a connection, 1192 Connection, 1192, 1196 Connection parameters, 1194
Analog alarm, 806 Allen-Bradley, 1228 Configuring, 819, 826 Limit value exceeded, 782 Mitsubishi, 1254 Omron, 1294 Analog alarm types, 806 Analog alarms Configuring, 815 Animation Configuring, 694 Diagonal movement, 699 Direct movement, 699 Green arrow in Overview, 695 Horizontal movement, 697 Multiple selection, 702 Object group, 702 Overview, 695 Vertical movement, 699 Appearance Dynamization of an object, 695 Application, 467 Alarm indicator, 840 Button, 1433 Date/time field, 1425 Graphic IO field, 1429 Graphic view, 1429 IO field, 1426 Recipe view, 756 Simple alarm view, 839 simple alarm window, 839 Switch, 1434 Symbolic IO field, 1435 Trend view, 1431 User view, 736 Area of unplugged modules, 286
1543
Index
Area pointer, 1076, 1133, 1172, 1297 Acquisition cycle, 1047 Active, 1047 Address, 1047 Allen-Bradley, 1226 Basic Panel, 1054 Comment, 1047 Configuring, 1048 Connection, 1046, 1050 Connections editor, 1046 Coordination, 1080, 1136, 1175, 1301 Creating, 1048 Data record, 870, 1085, 1140, 1179, 1305 Date/time, 48, 1077, 1078, 1173, 1299 Date/time PLC, 48, 1135, 1174, 1300 Job mailbox, 1083, 1138, 1177, 1302 Length, 1047, 1049 PLC tag, 1047 Pointer name, 1047 Project ID, 1082, 1137, 1176, 1302 Screen number, 1081, 1134, 1173, 1298 Tab, 1047 Area pointers, 1045 Date/time, 1135 Arrange Object in the screen, 645 Array, 45, 798, 800 Creating, 800 Indirect addressing, 788, 798 ARRAY Constant as array index, 33 Array element Location of use of HMI tag, 45 Name, 45 Array elements, 798 Array tag, 798 Char, 45 AS interface, 440 ASCII code table, 359 ASCII TSAP, 359 Asian characters Input on the HMI device, 1416 Interpretation, 1416 Memory requirements, 1416 Asian languages Configuration, 1416 Font size, 1416 Text field length, 1416 Asian operating system, 1344 Assign Object of a layer, 718 Assign symbol, 387
Assign tag, 387 Assigning a function to a function key, 710 a graphic to a function key, 713 Function key, 705, 707, 709 Assigning an IP address, 32 Assigning parameters Hardware, 278 Asynchronous Transferring data, 1086, 1141, 1184, 1305 AT, 33 Authorization, 1437 Assignment, 903, 924 Changing the name, 908 configuring, 916 Creating, 902, 921 Deleting, 908 Managing, 907 Automation License Manager, 21 Automation system, 1020, 1027 Local, 1530 Remote, 1530 Setting up, 1020 Autonegotiation, 461, 1066, 1116 Availability Object for Basic Panels, 734 Availability for specific devices Screen, 629 AWP command, 398 AWP_In_Variable, 401 AWP_Out_Variable, 399
B
Background color Dynamization, 695 Backing up, 1438 HMI device data, 1412 Backup Data of the HMI device, 1396, 1397 Bar, 735, 1424 Color transition, 735 Display limit lines, 735 Bar segment Defining, 735
1544
Index
Basic Panel Area pointer, 1054 Communication drivers, 1051 Display and operating element, 734 ETHERNET, 1053 HTTP protocol, 1051 IF1B, 1053 Interface, 1053 Mitsubishi, 1051 Modicon Modbus, 1051 Omron, 1051 OPC, 1051 Runtime start, 1389, 1410 S7 1200, 1051 S7 200, 1051 S7 300, 1051 S7 400, 1051 Basics Migration, 88 Behavior Button, 1433 Date/time field, 1425 Graphic IO field, 1430 IO field, 1427 Simple recipe view, 888, 1456 Switch, 1435 Symbolic IO field, 1436 Benefits of using TeleService, 1497 Bit (0, 1) Graphics list, 689 Text list, 682 Bit number (0 - 31) Graphics list , 691 Text list, 683 Block parameters Basics, 548 Borders Insert background image, 208 Placeholder for document information, 210 Specifying the print area, 209 Boundaries, 462, 1067, 1117 Boundary reached Event, 1007
Button, 758, 1433 Application, 1433 Behavior, 1433 Configuring, 922 Configuring access protection, 918 Define hotkey, 759 Graphic, 758 Layout, 1433 Mode, 758 Operation, 1433 Text, 758 Buttons and Switches Library, 725
C
Cabling rules (PROFINET), 461, 1066, 1116 CalibrateTouchScreen, 954 Callback to a number specified during connection establishment, 1519 Canceling printing, 215 Cascaded counting function, 564 Change word order Modicon MODBUS TCP/IP, 1260 ChangeConnection, 991 Changeover contact, 577 Changeover contact sensor type, 577 Changing Displayed name of user group, 908 Logoff time in runtime, 913 Name of the user, 913 Object size, 650 Password, 906 Password in runtime, 913 User group in runtime, 914 Users, 1442 Changing and displaying operating mode (example), 934 Changing the name Authorization, 908 User group, 907 Users, 906 Char Array tag, 45 Checklist for troubleshooting the modem, 1522 Circle, 745 Radius, 745 CJ1, 1291 CJ2, 1291 ClearAlarmBuffer, 963 ClearAlarmBufferProTool, 964 ClearAlarmBufferProtoolLegacy, 964
1545
Index
cleared, 1000 Click, 1005 Clock memory, 517, 538 Closing Runtime, 1411 Color Diagnostics of Ethernet cables, 590 Diagnostics of ports, 590 Color transition Bar, 735 Column Alarm view, 750 Comfort Panel S7-1200, 52 Comment Area pointer, 1047 Commissioning HMI device, 1406 communication Via the point-to-point port with MB_SLAVE, 34 Communication, 1019 Basics, 1020 Definition, 1019 S7 1200, 1055 S7 200, 1163 S7 300, 1104 S7 400, 1104 Third-party drivers, 1190 using area pointers, 1026 Communication drivers, 1026 Allen-Bradley, 1191 Basic Panel, 1051 Mitsubishi, 1230 Modicon Modbus, 1256 Omron, 1282 Communication network, 1027 PROFINET, 1028 Communication partners HMI device, 1019 Networking, 1031 PLC, 1019 SIMATIC S7, 1104, 1160, 1169, 1172 Communication via PUT/GET instructions Basic information on PUT/GET instructions, 361 Creating and assigning parameters to a connection, 366 Deleting an interconnection, 367 Overview of connection parameter assignment, 362 Requirements, 362 Starting connection parameter assignment, 365
Communications Cycle load, 522 Communications instruction "AS_DIAL", 1498, 1530, 1531 "AS_MAIL", 1498, 1533 "PG_DIAL", 1498, 1528, 1529 "SMS_SEND", 1498, 1532 Communications load, 517, 522 Communications modules, 530 Properties, 530 Communications port Configuring, 530 Communications processor Operation, 27 SIMATIC NET DVD, 26 Communications protocol Defining, 534 Overview, 34, 533 Compact, 1265, 1277 CompactLogix, 1199 Compare offline/online Automatic device assignment, 381 Compile Address parameters, 51 Compiling Migrated project, 92 With disabled pulse generator, 32 Components Alarm, 813 Configuration Downloading to device, 470 DP slave, 427 DP slave, simple, 419 Hardware, 278 Tag, 777 Uploading to programming device/PC, 471 Configuration phase, 1405 Configure a PROFIBUS subnet Matching parameters to one another, 311 Setting bus parameters, 311 Configure acknowledgment Alarm message, 1093, 1149, 1188, 1229, 1254, 1281, 1295 Configured Loop-in alarm, 823 configuring Authorization, 916
1546
Index
Configuring, 819, 827 Access protection, 922 Alarm acknowledgment, 834, 835, 836 Alarm group, 817 Alarm view, 830 Analog alarm, 819, 826 Analog alarms, 815 Connections, 1151, 1152, 1154, 1163 Controller alarms, 815 Discrete alarm, 817, 825 Discrete alarms, 815 Event-driven tasks, 821 I slave, 428 Layout of the alarm view, 831 Multiple tags, 778 Recipe view, 884 Rectangle, 675 System events, 815 Trend view for values from the PLC, 803 Configuring a connection Allen-Bradley DF1, 1208 Allen-Bradley EtherNet/IP, 1192 Mitsubishi FX, 1244 Mitsubishi MC TCP/IP, 1231 Modicon Modbus RTU, 1267 Modicon Modbus TCP, 1256 Omron Host Link, 1283 Configuring a PROFIBUS subnet Meaning of the bus parameters, 312 Configuring the network with Ethernet, 316, 1063, 1113 Creating private subnets, 318, 1064, 1114 Linking networks, 318, 1064, 1114 Relationship between IP address and subnet mask, 317, 1063, 1113 Setting the IP address, 317, 1063, 1113 Setting the subnet mask, 317, 1063, 1113 Configuring the remote modem, 1501 Connecting PLC, 1196, 1235, 1248, 1261, 1287 Connecting a TS Adapter with an external modem, 1501 Connecting a TS Adapter with an internal modem, 1501 Connecting cable 6XV1440 - 2P for Mitsubishi PG protocol, 1249 Allen-Bradley cable 1784-CP10, 1218 Mitsubishi FX, 1248 Connecting cables Point-to-point cable 1, Point-to-point cable 2, 1275
Connection, 319, 331, 1025 Address details, 625 Allen-Bradley DF1, 1208, 1212 Allen-Bradley EtherNet/IP, 1192 Area pointer, 1046, 1050 Configuring, 1032, 1036, 1192, 1208, 1231, 1244, 1256, 1267, 1283 Configuring a connection when there is no or no clear network assignment, 324 Creating, 348, 1032, 1036 Deleting, 350 Integrated, 1032 integrated connection, 768, 1042 Mitsubishi MC TCP/IP, 1231 Modicon, 1271 Modicon Modbus RTU, 1267 Modicon Modbus TCP, 1256 offline, 1082, 1138, 1177 Omron Host Link, 1283 Parameters, 1194, 1210, 1233, 1245, 1258, 1269, 1285 S7 200, 1163 Table, 1031 Connection cable Allen-Bradley cable 1747-CP3, 1219 Allen-Bradley cable 1761-CBL-PM02, 1220 Modicon, 1271 Multipoint cable 1:MP/TP/PC, 1288 Multipoint cable 2:RS422, MP/TP/PC, 1288 Omron Host Link, 1287 Point-to-point cable PP2 for Omron, 1289 Connection description Changing parameter values, 356 Data block , 353 Structure, 353 Connection details, 624 Connection diagnostics Detailed, 623 Overview, 621 Connection information, 623 Connection parameter assignment Connection parameters, 345 Overview, 343 Starting, 347 Connection parameter assignment of PUT/GET instructions, 365
1547
Index
Connection parameters Allen-Bradley DF1, 1210 Allen-Bradley EtherNet/IP, 1194 Mitsubishi FX, 1245 Mitsubishi MC TCP/IP, 1233 Modicon Modbus RTU, 1269 Modicon Modbus TCP, 1258 Omron Host Link, 1285 Connection parameters of PUT/GET instructions, 364 Connection resource, 319, 331 SIMATIC S7 1200, 50 Connection resources, 623 Connection status Displaying using icons, 622 Connections Allen-Bradley DF1, 1213, 1214 Configuring, 1151, 1152, 1154, 1163 Editor, 1151, 1152, 1154 Consistency Slot rules, 280 Constant as array index, 33 Context filter, 281 Control element Alarm view, 750, 752 Recipe view, 756 simple alarm view, 1447 Simple alarm view, 840 Trend view, 746 Controller alarms Configuring, 815 ControlLogix, 1199 Conversion Implicit, 34 Converted name (PROFINET), 449 Converting an unspecified CPU, 121 Cookie, 402 Coordinated transfer, 870 With PLC, 870 Coordination, 1026 Copy Screen, 634 Tag, 776 Template, 640 Copy template Library, 723
Copying Adjusting screen size, 1380 Alarm indicator, 42 Alarm view, 42 Alarm window, 42 Color, 1380 Font, 1380 Function key, 1380 Hardware component, 295 HMI device, 38 Invalid object, 1379 Linked objects, 1382 Principle, 1378 Screen, 1380 User-defined folders, 1379 Count (8 DI NAMUR), 562 Counter input, 526 Counter mode, 526 Counter, high-speed, 524 Cover page Insert background image, 208 Placeholder for document information, 210 CP1, 1291 CPM, 1291 CPU Displaying the current LED status, 597 Fill level of all types of memory, 598 Inserting a signal board, 389 Properties, 516 Reading out a diagnostics buffer, 600 Selecting from the hardware catalog, 287 Switching operating mode, 604 CPU control panel Display area, 598 CPU properties, 517 CPU type Allen-Bradley DF1, 1223 Allen-Bradley EtherNet/IP, 1199 FX3 series, 1241 Mitsubishi FX, 1250 Mitsubishi MC TCP/IP, 1241 Modicon Modbus RTU, 1277 Modicon Modbus TCP, 1265 Omron Host Link, 1291 Create Connection, 1057 Global library, 731 Group, 666 Template, 639
1548
Index
Creating, 877 Alarm group, 817 Array, 800 Connection, 1032, 1036, 1106 External tag, 771 Infotext, 819, 821 Internal tag, 774 Recipe, 877 Recipe data record, 1457 Recipe data record on the HMI device, 890, 891 Screen, 633 User group, 902, 924 Users, 904, 925, 1439, 1441 Users in runtime, 911 Creating a print preview, 210 Cross-reference Inspector window, 42 Cross-reference list, (See cross-references) Displaying, 1338 Overview, 1338 Settings, 1339 Sorting columns, 1339 Structure, 1339 Views, 1339 Cross-references Displaying, 1338, 1341 Introduction, 1338 Uses, 1338 CS1, 1291 CSV file, 1314, 1315, 1325 Custom alarm classes, 809 Custom web pages, 394, 408 Cycle load, 522 Cycle time, 517, 521 display configured, 593 display measured, 596 Cyclic Continuous, 785 In operation, 785 Cyclic interrupt OB Assigning parameters, 550 Description, 544 Cyclic OB Description, 542 Cyclic operation, 1162, 1165 Cyclic program execution Options for interrupting, 542 Programming, 542
D
Data areas Area pointer, 1048, 1298 Reading, 1048, 1298 Writing, 1048, 1298 Data backup, 65 HMI device, 1396, 1412 Data bit (DBX), 505 Data byte (DBB), 505 Data double word (DBD), 505 Data exchange, 1019 DP slave, 419 I slave - DP master, 420 using area pointers, 1026 Data exchange over the AS-AS remote link Communication instruction "AS_DIAL", 1530 Data flow, 1454 Data flow control, 532 Data log, 393 Data mailbox For recipes, 870 Data record, 1026 Reading, 891 Transfer, 892 Data record list, 873 Data type Allen-Bradley, 1228 Conversion, 34 Discrete alarm, 1228, 1254, 1294 Internal tag, 771, 1044 Mitsubishi, 1254 Mitsubishi FX, 1249 Mitsubishi MC TCP/IP, 1197, 1240 Modicon Modbus RTU, 1276 Modicon Modbus TCP, 1264 Omron, 1294 Omron Host Link, 1289 Valid, 1197, 1240, 1249, 1264, 1276, 1289 Data types Migration, 110 S7 1200 V1, 1094, 1095 S7 200, 1189 S7 300/400, 1150 Valid, 1094, 1095, 1150, 1189 Data word (DBW), 505 Date/time, 1026 Area pointer, 1077
1549
Index
Date/time field, 737 Application, 1425 Behavior, 1425 Display system time, 737 Format, 738 Layout, 1425 Operation, 1425 Using tags, 737 Date/time PLC, 1026 Deactivate, 1003 Deadband Setting, 821 Decimal places, 25, 1421, 1422 DecreaseFocusedValue, 989 DecreaseTag, 990 Default font, 1365, 1414 Defective devices, 585 Defective license, 66 Define Reference object, 651 Define hotkey, 759 Delay time Setting, 821 Delete Template, 640 Deleting Authorization, 908 Hardware component, 294 Object, 647 Recipe data record, 1459 Screen, 634 Tag, 777 User group, 908 Users, 907, 1443 Deleting a connection, 125 Designation TS Adapter, 1503 TS Adapter, 1505, 1512 Designing a background, 658 Designing a frame, 658 Details view, 152 Determine diagnostics status, 599 Determining time of day, 606 Device Adding to a hardware configuration , 289 Copying, 38, 295 Defective devices, 585 Deleting, 294 Inserting, 1021 Moving, 296 Renaming, 381 Device address, 385
Device information, 201, 585 Device name, 444, 446, 449 Device number, 445 Device overview Address range, 385 Device replacement without exchangeable medium, 463 Device Tool, 468, 469 Device view Area of unplugged modules, 286 Edit parameters, 298 Edit properties, 298 Hardware and network editor, 266 Inserting a signal board, 389 Inserting module, 291 Racks, 282 Device wizard, 1311 Devices Connecting, 1025 Networking, 1024, 1031 Devices & Networks, 1024, 1031 Devices and networks, 1024, 1031 Connections, 1032 HMI connections, 1032 Diagnose repeater, 618 Diagnostic error interrupt OB, 547 Diagnostics, 573 Diagnostics buffer Basics, 509, 612 Organization, 612 Diagnostics status Determine and display online, 586 Diagonal movement Animation, 699 Direct access to the I/O, 510 Disabling Project language, 1346 Discrete alarm, 806, 807 Allen-Bradley, 1228 Configuring, 817, 825 Mitsubishi, 1254 Omron, 1294 Discrete alarm types, 806 Discrete alarms Configuring, 815 display Tooltip, 1423 Display object Availability for Basic Panels, 734 Display PDF files, 57 Display system time, 737 Display the memory types of a CPU, 598
1550
Index
Display Welcome Tour, 57 Displaying Cross-reference, 1341 Cross-references, 1338 Displaying alarms, 491 Displaying the online status, 1481 Displaying values As a trend, 802 Distribute Objects evenly, 653 Distributed I/O, 417, 571 Documentation editor Structure, 205 Documentation function Using frames and cover pages, 203 double-click, 1003 Download Error messages, 1401 Extended download to device, 52 Project, 1388, 1405 Downloading to the device, 470 Downloading data to the PLC Error message, 51 DP, 1075, 1125 DP interface, 422 DP master, 558 Add DP master system, 425 Devices and modules, 422 Disconnection from DP master system, 424 Display on DP slave, 423 DP interface, 422 DP master system Add DP slave, 426 Creating, 418, 420, 422 Disconnect DP slave, 426 Disconnection from subnet, 424 Edit properties, 425 Highlight, 423 Node disconnection, 424 DP slave Add to DP master system, 426 Assign DP master system, 427 configuring, 419, 427 Data exchange, 419 Disconnect from DP master system, 426 DP master display, 423 Hardware catalog, 418 Intelligent, (See I slave) Networking, 420 Types, 425 With preprocessing, (See I slave)
DP standard slave, 438 DP/DP coupler, 418 DPV1 Configuring an ET 200S, 436 DTL data type Restriction, 48 Dynamization Color of an object, 695 Flashing, 695 Object, 692 Dynamize Appearance of an object, 695 Direct movement, 699 Green arrow in Overview, 695 Movement of an object, 697
E
Eastern characters Input on the HMI device, 1416 Edit Object within a group, 670 Edit networking Disconnecting from a network, 308 EditAlarm, 945 Editing Alarm, 1450 Folder link, 662 Function list, 933 Recipe data record, 1458 Editing language, 1342 Selecting, 1346 Editing networking Copying a subnet, 308 Copying subnets and devices, 309 Editor Connection, 1036 Connections, 1151, 1152, 1154 Graphics, 1356 Element list, 873 Ellipse Horizontal radius, 740 Vertical radius, 740 Ellipse , 740 enable, 1000 Enable autonegation, 460, 1065, 1115 End of discovery of accessible devices, 462, 1067, 1117 End of sync domain, 462, 1067, 1117 End of topology discovery, 462, 1067, 1117 Engineering system Performance features, 1461
1551
Index
Enumeration types, 404 Error alarm Acknowledge, 1450 Error message Downloading data to the PLC, 51 Error messages Download, 1401 Establishing a connection from a remote system ("PG_DIAL"), 1529 Establishing a remote connection, 1521 Procedure, 1521 ET 200eco, 556 ET 200eco PN, 556, 571 ET 200iSP, 555 ET 200iSP distributed I/O station Definition, 557 ET 200L, 555 ET 200M, 555 ET 200pro, 556 ET 200R, 556 ET 200S, 555 DPV1 mode, 436 Option handling, 434 Positioning module, 30 Pulse generator module, 30 Reference junctions, 430 Slot rules, 429 ET 200S COMPACT, 555 Ethernet S7 200, 1102, 1158, 1167 ETHERNET Basic Panel, 1053 Ethernet interface Displaying parameters, 1485 Ethernet module, 31 Removal/insertion, 29
Event Acknowledge, 1004, 1007 Adjust, 1001 Alarm buffer overflow, 1006 Boundary reached, 1007 cleared, 1000 Click, 1005 Deactivate, 1003 double-click, 1003 Enable, 1000 Execute, 1001 For function lists, 790 Free space critically low, 1010 Incoming, 1005 Inspector window, 42 Limit , 1006, 1007 Loop-In-Alarm, 1005 Low free storage space, 1009 Outgoing, 1005 Overflow, 1009 Press, 1004 Press key, 1008 release, 1006 Runtime Stop, 1008 Screen change, 1002 Selection changed, 1001 Switch off, 1009 Switch on, 1009 Tags, 790 Time expired, 1010 User change, 1002 Value change, 1010 When dialog is closed, 1002 When dialog is opened, 1002 Event trigger, 1015, 1018 Event-driven tasks Configuring:event-driven tasks, 819 Example Application for alarm classes, 809 Changing and displaying operating mode, 934 System alarm, 806 Example: Discrete alarm, 807 Exchangeable medium, 463 Execute, 1001 Export Alarm, 1317 Project texts, 1335, 1353 Recipe, 1314 Tag, 1325 Text list, 1330 Extended download to device, 52
1552
Index
External graphic Edit folder, 661 Link folder, 662 Removing the folder link, 661 Rename folder, 661 External image file add to graphics library, 1358 Managing, 645 Storing in the image browser, 663
F
FAQs, 276 Field device, 438, 465 Filter Hardware catalog, 281 Find and replace, 219 Additional options for searching, 219 Replacing search keys, 220 Start search, 220 Using the search function, 219 Firmware update memory card, 503 Flash test, 617 Flashing, 695 Flip Object, 645 Flow control, 31 Flutter monitoring, 578 Folder link Editing, 662 Removing, 662 Renaming, 662 Font settings Migrate, 96 Font size Asian languages , 1416 Force job On SD card, 23 Foreground color Dynamization, 695 Format, 738 Formatting Alarm text, 823 Fragment, 405, 410 Free space critically low, 1010 Frequency meter, 568, 571 Function Assigning to a function key, 710
Function key, 705 Assigning a function, 710 Assigning a graphic, 713 Global assignment, 707 Global screen, 637 Local assignment, 638, 709 protect with password, 712 Use global assignment, 638 used for screen navigation, 715 Function list, 790, 929, 1014 Asynchronous execution, 934 Execution, 931 Execution in Runtime, 934 Synchronous execution, 934 System function, 931 User-defined functions, 931 Function lists Editing, 933 Functional scope ProSave, 1396 Functions Updating tag value, 768, 1042 FX1 series, 1250 FX2 series, 1250 FX3 series, 1241
G
Gateways, 1500 General information on troubleshooting, 1535 Generation of packed addresses, 432 GetGroupNumber, 961 GetPassword, 961 GetUserName, 960 Global assignment Of a function key, 705, 707 Global data block Configuring, 1049 Creating, 1049
1553
Index
Global library, 722 Adding a copy template, 248 Adding types, 249 Basics, 240 Closing, 246 Create, 731 Creating, 241 Creating folders, 247 Deleting, 247 Editing elements, 253 Migrating, 103 opening, 733 Opening, 242 Removing elements, 255 Save, 732 Saving, 245 Shared work, 241 Showing properties, 244 Using a supplied global library, 256 Using filter view, 240, 257 Using master copies, 250 Using the element and part views, 231 Using types, 251 Global screen, 637 Function key, 637 Template, 638 Global softkey, 707 Global telephone book properties, 1498 Go online connecting several devices, 1482 Going offline, 617 Going online, 615 multiple TIA portal instances, 28 GoToEnd, 950 GoToHome, 950 Graphic add to graphics library, 1357 Assigning to a function key, 713 Button, 758 Graphic view, 741 Inserting, 645 managing, 661 Stretching, 741, 743 Using from the graphic browser, 661 With transparent background, 661 Graphic browser, 661 Graphic browser , 1358 Graphic I/O field, 742 Output graphics list, 692
Graphic IO field, 1429 Application, 1429 Behavior, 1430 Operation, 1430 Graphic view, 741, 1429 Application, 1429 Layout, 1429 Operation, 1429 transparent color, 742 Graphics, 663 Editor, 1356 Graphics list Application, 684 Bit (0, 1), 689 Bit number (0 - 31), 691 Creating, 685 Graphic I/O field, 692 Outputting configuration data, 691 Range (0 - 31), 686 Range (... - ...), 688 group Cancel, 667 Edit, 666 Ungroup, 667 Group Adding objects, 668 Cancel, 667 Creating, 666 Editing, 666 Removing an object, 669 Ungroup, 667 GSD files Configuring devices (PROFIBUS), 438 GSD revisions (PROFIBUS), 437 Installation, 438 GSD files (PROFINET), 464 Changing revision, 466 Installation, 465 GSDML, (See GSD files (PROFINET))
H
Handshaking, 532 Hardware Configurimg and assign parameters, 278 Detection, 32 Edit parameters, 298 Edit properties, 298 Hardware and network editor Device view, 266 Network view, 263 Topology view, 268
1554
Index
Hardware catalog Adding device, 289 Browsing, 281 DP slave, 418 DP/DP coupler, 418 I slave, 418 Selecting the hardware component, 287 Task card, 274 Hardware configuration Adding device, 289 Adding module, 291 Hardware diagnostics, 584 Hardware editor Components, 261 Function, 261 Hardware catalog, 274 Inspector window , 273 Hardware ID, 385 Hardware interrupt OB Assigning parameters, 549 Description, 545 Hardware requirements, 58 Communication instruction "AS_MAIL", 1533 Communication instruction "SMS_SEND", 1532 Communications instruction "PG_DIAL", 1529 Hardware requirements for AS-AS remote link Communication instruction "AS_DIAL", 1531 Hardware support package Installing, 72 Hardware-controlled data flow control, 532 Harmonize Object size, 653 HART, 559 Help Browsing, 169 Call topic from favorites, 170 Delete topic from favorites, 171 Find keywords, 169 Full-text search, 169 Identification of Help topics, 166 Open, 168 Open tooltip cascades automatically, 172 Printing help topics, 171 Save topics in favorites, 170 Use index, 169 Help indicator, 744 Hewlett-Packard Keyboard driver, 53 Hibernate, 23 Hidden input, 739
High-speed counter Configuring, 527 General, 524 How it works, 525 HMI connection, 122, 331, 1025 Creating, 1057, 1106 MPI, 1126 MPI parameters, 1128 PROFIBUS, 1119 PROFIBUS parameters, 1070, 1120 PROFINET, 1056, 1057, 1105, 1106 PROFINET parameters, 1058, 1108 S7 1200, 1057 S7 300/400, 1106 HMI connections Devices & Networks, 1032 HMI device, 63 Changing the device type, 1403 Commissioning, 1406 Data backup, 1396, 1397, 1412 MPI parameters, 1130 Performance features, 1463 PROFIBUS parameters, 1072, 1122 PROFINET parameters, 1060, 1109 Recommissioning, 1406 Reset to factory settings, 1400 Restoring data, 1396, 1398, 1412 System limits, 1463 HMI device licensing Non-PC-based, 63 HMI device replacement, 38 HMI device type Changing, 1403 HMI device wizard, 1311 Horizontal radius, 740 How the frequency meter works, 569 HSC, 524 HSP, (See Support package) HTTP protocol Basic Panel, 1051 HTTPS, 392
I
I address, 385 I slave, 419, 427 configuring, 428 Data access, 428 Data exchange, 420 Hardware catalog, 418 I/O Direct access to, 510
1555
Index
I/O access error, 508 I/O address, 385, 510 I/O field, 738 Data format, 739 Decimal format, 44 Display format, 44 Hidden input, 739 Mode, 739 I/O input, 505 I/O output, 505 Icon For comparison, 588 For comparison status, 622 for connection status, 622 For diagnostics, 587 for operating mode, 589 Overlay icon, 589 Icons in TeleService, 1525 IE/AS-i link PN IO, 440 IEEE tag, 558 IF1B Basic Panel, 1053 Image file Storing in the image browser, 663 Storing in the image browser , 1358 Import Alarm, 1319 Analog alarm structure, 1320 Project texts, 1337, 1355 Recipe, 1315 Structure of discrete alarms, 1323 Structure of recipe data, 1317 Tag, 1327 Text list, 1332 Importing a recipe Structure for the import, 1317 Importing analog alarms Structure for the import, 1320 Importing discrete alarms Structure for the import, 1323 in the screen Arrange object, 654 Incoming, 808, 1005 IncreaseFocusedValue, 948 IncreaseTag, 949 Index tag, 788, 789 Indirect addressing , 788 Industrial Ethernet, 1027
Information system Components of the information system, 165 Roll-out, 166 Tooltip, 167 Infotext, 814 Creating, 819, 821 Initialization (custom web pages), 394 Initialization of the modem, 1502 Initialization string requirements, 1502 Input (I), 505 Input byte (IB), 505 Input word (IW), 505 Insert Library object, 731 Inserting Graphic, 645 Object, 645 Rectangle, 675 Inspector window Cross-reference, 42 Event, 42 Layout, 148 Reducing automatically, 143 Inspector window Diagnostics tab, 585 Hardware and network editor, 273 Installation Displaying software, 72 Licenses, 28, 67 Log, 68 Modifying products, 73 ProSave, 51 Repairing products, 75 Starting, 69 Support package, 72 System requirements, 57 Target directory, 25 Updating products, 73 virtual drives, 21 Installing support packages, 72 Installing the local modem, 1500 Instructions for configuring a remote modem, 1502 Integrated Connection, 1032, 1036 Integrated connection, 768, 1042 Integrated project Converting an unspecified CPU, 121 Creating an integrated HMI connection, 122 Deleting an unspecified connection, 125 Linking HMI tags, 124 Migrating, 107, 117 Post-editing, 119
1556
Index
Intelligent DP slave, (See I slave) Interconnecting ports Graphic view, 378, 380 In the Inspector window, 457 Table view, 379, 380 Interface Adding, 1483 Basic Panel, 1053 Displaying, 594 Renaming, 381 Interface properties, 594 Interrupts With packed addresses, 436 Invalid license With a time zone change, 66 InverseLinearScaling, 953 InvertBit, 951 InvertBitInTag, 952 InvertLinearScaling, 953 IO device Networking, 455 Update time, 458 Watchdog time, 458 IO field, 1426 Application, 1426 Behavior, 1427 Changing between input fields, 1427 IO field, 1428 Layout, 1427 Operation, 1427 Touch operation, 1428 IO system, 454 Creating, 455 Send clock cycle, 457 IO-Link, 469 IP address, 24, 444 Assigning, 607 IP address parameters, 445 IP parameters, 595 IQ sense, 580 iQ series, 1241 ISO-on-TCP Characteristics, 352 TSAP, 357
K
Key operation Date/time field, 1426 IO field, 1428 Keyboard driver Hewlett-Packard, 53 Keyboard shortcuts Changes in assignment, 22 Editing texts, 162 Project editing, 160 Project tree, 161 Tables, 161 Window, 161 Know-how protection Converting blocks from V10.5, 33
L
Language Activate project language, 1346 Asian languages, 1344 Asian operating system, 1344 Disabling the project language, 1346 Editing language, 1346 Language support, 1344 Language-dependent format, 1343 Language-specific graphic, 1356 Log, 1366 multilingual project , 1348 Reference language, 1346 Regional format of the date, time, currency, and numbers, 1343 Language abbreviation, 414 Language behavior Screen keyboard, 53 Language switching, 414, 1360, 1415 Log, 1366 Runtime language, 1363 Languages Migrating, 101 Layer Assigning objects to a layer, 718
J
Job mailbox, 1026 Transferring data, 1088, 1144, 1181, 1308
1557
Index
Layout Alarm indicator, 754, 841 Alarm view, 748, 749, 752, 839, 1447 Bar, 735 Button, 758, 1433 Circle, 745 Date/time field, 737, 1425 Ellipse, 740 Graphic I/O field, 742 Graphic view, 741, 1429 I/O field, 738 IO field, 1427 Line, 748 Recipe view, 756 Rectangle, 755 Simple recipe view, 887, 1455 Simple user view, 1438 Switch, 757, 1434 Symbolic I/O field, 760 Text field, 761 Trend view, 746, 1431 User view, 736 LED ACK, 1448 Length Area pointer, 1047, 1049 Library, 722 Basics, 227 Buttons and Switches, 725 Copy template, 723 Copying a library object, 724, 729 Deleting a library object, 729 Global libraries, 240 opening, 733 Project library, 232 Save, 732 Storing an object, 730 Task card, 229 Type, 724 Types, 227 Using filter view, 240, 257 Using the element and part views, 231 Library object, 722, 723 Inserting, 731 License Defective, 66 Defective license, 67 Starting without valid license, 63 License key, 65 Working with license keys, 65 License Manager Panel plug-in, 63 Licenses, 28, 67 Limit , 1006, 1007
Limit range Tag, 781 Limit value, 814 Tag, 782 Limit value check, 1420, 1422 Limit value exceeded Analog alarm, 782 Line, 747 design, 658 Line end, 658, 748 Line start, 748 Line break, 574 Line end Line, 748 Line start Line, 748 LinearScaling, 962 Link folder External graphic, 662 Linked objects Copying, 1382 Linking HMI tags, 124 LLDP (Link Layer Discovery Protocol), 462, 1067, 1117 Load from a device, 33 In programming device/PC, 471 SIMATIC PC station, 52 Load memory, 505 Load window layout Loading additional window layouts, 157 Loading via quick access, 157 Loading Downloading project data to the device, 190 Downloading to a memory card, 192 from a device, 193 General information, 189 Loading projects with connected HMI device, 1387 Local assignment Of a function key, 705, 709 Local data bit (L), 505 Local data byte (LB), 505 Local data double word (LD), 505 Local data word (LW), 505 Local time, 517 Log Language switching, 1366 Runtime language, 1366 Log file Modem alarms , 1539 Log language, 1366
1558
Index
Logoff, 939 Users, 1440 LogOff, 939 Logoff time, 1437 Changing, 906 Changing in runtime, 913 Logon, 945 Logon failed, 915 Reporting, 919 Users, 914 Logon dialog Configuring access protection, 918 Logon for web server, 391 Logon web server, 391 Loop-in alarm Configured, 823 Loop-In-Alarm, 1005 Low free storage space, 1009
M
managing Graphic, 661 Managing User group, 907 Users, 906 Users in runtime, 912 Manual fragment, 410 Manuals, 276 Maximum cycle time, 502, 521 Maximum length Tag, 53 MB_SLAVE, 34 Measuring window (GATE), 571 Memory area Load memory, 505 Retentive memory areas, 507 Work memory, 505 Memory bit (M), 505 Memory byte (MB), 505 Memory card, 503, (See Memory Card) Accessing, 226 Adding a card reader, 225 Introduction, 225 Removal/insertion, 28 Showing properties, 227 Memory double word (MD), 505 Memory requirements Recipe, 1467 Memory reset, 503 Making, 606 Memory word (MW), 505
Menu command Simple recipe view, 888, 1456 Message Sending, 536 Specifying the end, 537 Specifying the start, 536 Micro, 1265 MicroLogix, 1199, 1223 Migrated project Compiling, 92 Migrating projects Procedure, 85 Requirements, 85 Migration Adaptations beforehand, 93 Alarm groups, 98 Allen-Bradley DF1 data types, 111 Allen-Bradley Ethernet IP data types, 111 Basics, 88 Data types Modicon Modbus, 112 Data types Modicon Modbus TCP/IP, 113 Data types Omron Hostlink/Multilink, 113 Data types SIMATIC S7 200, 114 Data types SIMATIC S7 300/400, 114 Displaying a log file, 87 Displaying history, 86 Excluding the hardware configuration, 82 Font settings, 96 Global library, 103 Integrated project, 117 Introduction, 87 Introduction to migration, 81 Migrating an integrated project, 107, 117 Migrating projects, 91, 108 Mitsubishi FX data types, 112 of external tags, 110 of languages, 101 of project text, 101 Project library, 103 Recipe data, 104 Runtime data, 104 Supported HMI devices, 93 Supported products, 81 Tags, 97 Text, 101 The migration process, 81 User administration, 104
1559
Index
Migration tool, 89 Connecting the hardware configuration, 83 Creating a migration file, 84 Distribution and sources, 78 Removing, 79 System requirements, 78 Using the migration tool, 82 Minimum cycle time, 502, 521 Mitsubishi, 1190 Address, 1242 Analog alarm, 1254 Basic Panel, 1051 Communication drivers, 1230 Connection interruption, 48 FX, 1230 TCP/IP, 1230 Mitsubishi FX Configuring a connection, 1244 Connection, 1244, 1248 Connection parameters, 1245 CPU type, 1250 Data type, 1249 Migrating data types, 112 Mitsubishi MC TCP/IP Configuring a connection, 1231 Connection, 1231, 1235 Connection parameters, 1233 CPU type, 1241 Data type, 1197, 1240 Mode, 758 Graphic I/O field, 743 I/O field, 739 Modem Local, 1500 Problem, 1535 Remote, 1501 Modem alarms Log file, 1539 Modem connection cannot be established, 1522 Modem connection is closed, 1523 Modem connection is interrupted, 1538 Causes and solutions, 1538 Modem support, 1499 Modem types / media, 1500 Modems without plug-and-play, 1501 Modicon Approved communication with Modbus RTU, 1272 Connection, 1271 Connection cable, 1271 Restrictions with Modbus RTU, 1272 Modicon M340, 1265
Modicon Modbus, 1190 Basic Panel, 1051 Communication drivers, 1256 Migrating data types, 112 RTU, 1256 TCP, 1256 Modicon Modbus RTU, 1277 Configuring a connection, 1267 Connection, 1267 Connection parameters, 1269 Data type, 1276 Modicon Modbus TCP, 1265 Configuring a connection, 1256 Connection, 1256, 1261 Connection parameters, 1258 Data type, 1264 Modicon MODBUS TCP/IP Change word order, 1260 Modicon Modbus TCP/IP Migrating data types, 113 Module Addressing, 385 Configuring and assigning, 28 Copying, 295 Deleting, 294 Determine diagnostics status, 599 Inserting, 29, 293 Moving, 296 Removing, 29 Replacing, 297 Select, 284 Time of day on a module, 606 Module addressing, 509 Module arrangement, 281 Module replacement, 121 Module titles, 283 Module version Updating, 300 Momentum, 1265, 1277 Monitor, 460, 1065, 1115 Monitoring window, 578 Mono-master system, 419 Move Screen, 634 Move view Keyboard shortcuts, 277 Overview navigation, 264, 267, 269 Moving Hardware components, 296
1560
Index
MPI, 1027 Addressing, 1133 Connection, 1154 HMI connection, 1126 Network, 1029 Network architecture, 1030 Parameters, 1128, 1130, 1131 S7 200, 1161, 1170 S7 300/400, 1126 MPI address S7 300, 1133 S7 400, 1133 MPI communication S7 300/400, 1126 MPI parameters S7 300/400, 1128, 1130, 1131 Multiple selection, 284, 650 Multiplexing, 34, 788 Address multiplexing, 792 Address multiplexing Allen-Bradley Ethernet IP, 1203 with absolute addresses, 792 with symbolic addresses, 792 Multi-point connection Allen-Bradley DF1, 1216, 1217 MUX, 34
N
Name Array element, 45 Names of alarm classes Change through migration, 99 Network, 1019 Ethernet, 1028 MPI, 1029 PPI, 1030 PROFIBUS, 1029 PROFINET, 1028 Network access Opening the properties, 1480 Network architecture PPI, 1031 Network card, 31 Network drive, 24 Network editor Components, 261 Function, 261 Hardware catalog, 274 Inspector window , 273
Network overview Basic functions, 305 Basic functions for editing the network overview table, 305 Network view, 1031 Adding device, 289 Hardware and network editor, 263 Networking Communication partners, 1031 Devices, 1031 Networking devices Basics of configuring networks, 301 Editing interface parameters, 307 Editing network parameters, 307 Networking several interfaces at the same time, 303 Networking with an existing subnet, 304 Networking without an existing subnet, 302 Networks within a project, 301 Requirements, 306 Types of communication, 301 Networking in the device view Networking options, 305 Procedure, 306 Non-integrated Connection, 1036 Non-licensed mode Engineering system, 63 HMI devices, 64 Null pointer, 34
O
O, 1473 OB 1, 542 OB 80, 546 OB 82, 547 object Group, 666 Paste, 658 Rotate, 656
1561
Index
Object Arrange, 645, 654 Assigning to a layer, 718 Availability for Basic Panels, 734 Creating a new OLE object, 645 Creating an OLE object from a file, 645 Customizing default properties, 645 Deleting, 647 Design, 658 Dynamization, 692 Dynamization of the appearance, 695 Dynamize direct movement, 699 editing within a group, 670 Evenly distributing, 653 Flip, 645 Flush alignment, 652 Grouping, 666 Inserting, 645 Inserting of the same type, 645 Inserting several times, 658 Multiplying, 658 outside the area, 655 Paste, 645 Repositioning and resizing multiple objects, 645, 660 Repositioning objects, 645, 648 Resize, 650 Resizing, 645 Rotate, 645, 656 Select multiple objects, 650 Selecting multiple objects, 645 Storing in a library, 730 Tab sequence, 645 Object group Animation, 702 Editing an object within a group, 670 Removing an object, 669 Object list Tag, 773 Object names Uniqueness, 88 Object size Harmonizing, 653 Obtaining user rights Logging on to the operating system with administrator privileges, 164 With Windows user account control, 164 OLE object create from a file, 645 Recreate, 645 Save in Graphics, 663 Storing in the image browser , 1358
Omron, 1190 Analog alarm, 1294 Basic Panel, 1051 Communication drivers, 1282 Host Link, 1282 Omron Host Link, 1291 Address, 1291 Configuring a connection, 1283 Connection, 1283, 1287 Connection cable, 1287 Connection parameters, 1285 Data type, 1289 Omron Hostlink/Multilink Migrating data types, 113 On demand, 785 Online access, 1476 Online and Diagnostics view, 584 Online connection, 1473 multiple TIA portal instances, 28 Online displays Orange color, 590 Online mode, 1473 Canceling an online connection, 1481 Display of the online mode, 1475 Displaying accessible devices on an interface, 1479 Displaying all accessible devices as a list, 1479 Go online, 1480 Standby or hibernation of the programming device / PC, 1473 Online operation, 28 Online Tools, 584, 592 OP 73 Baud rate on PROFIBUS, 1103, 1159, 1161, 1168, 1170, 1171 OP 77A Baud rate on PROFIBUS, 1103, 1159, 1161, 1168, 1170, 1171 OP73 Loading a project, 52 OP77A Loading a project, 52 OPC Basic Panel, 1051 Open Global library, 733
1562
Index
Open User Communication Changing parameter values, 356 Ability to read back, 356 Connection description, 353 Connection establishment, 341 Connection parameter assignment, 341, 343 Connection parameters, 345 Creating a connection, 348 Deleting an interconnection, 350 General, 340 Instructions, 341 Port numbers, 356 Protocols used, 351 Starting connection parameter assignment, 347 TCON_Param, 353 TSAP, 357 Opening phone books, 1525 Operand area, 505 Operating behavior Enabling system memory, 539 Using clock memory, 538 Using time-of-day functions, 523 Operating element Availability for Basic Panels, 734 Operating mode Introduction, 496 RUN, 502 STARTUP, 498 STOP, 502 Transitions, 497 Operating recipes Creating a recipe data record, 890 Creating recipe data records, 890, 891 Read recipe data record, 891 Transfer data record, 892 Operating system Asian language setting, 1344 Setting to Western, 1344 Updating, 1400
Operation Alarm indicator, 841 Button, 1433 Date/time field, 1425 Graphic IO field, 1430 Graphic view, 1429 IO field, 1427 simple alarm view, 1447 Simple alarm view, 840 Simple recipe view, 887, 1455 Simple user view, 1439 Switch, 1434 Symbolic IO field, 1436 Trend view, 1432 Operator control Trend view, 1432 Operator input in the recipe view Transferring data, 1087, 1143, 1180, 1307 Optimizing the configuration Allen-Bradley DF1, 1207, 1225, 1243, 1251, 1266, 1277, 1292 Option handling, 434 Options for establishing the connection S7-1200 CPUs, 1528 S7-300/400 CPUs, 1527 Other PLCs Addressing, 1191 Data types, 1191 Special features, 1191 Outgoing, 808, 1005 Output (O), 505 Output byte (QB), 505 Output double word (QD), 505 Output fields Multiplex tag, 46 Output word (QW), 505 Overflow, 575, 1009 Overlay icon, 589 Overlaying Tag, 33 Overview navigation, 264, 267, 269 Overview of TS Adapters that can be used, 1503 Overview window, 38, 153 Comparing objects, 155 Showing and hiding columns, 156
P
PageDown, 978 PageUp, 978 Pane mode, 152 Panning, (See move view)
1563
Index
Parallel installation, 61 Parameter For CPU, 517 Parameters Connection, 1194, 1210, 1233, 1245, 1258, 1269, 1285 MPI, 1128, 1130, 1131 PROFIBUS, 1070, 1072, 1074, 1120, 1122, 1123 S7 200, 1100, 1102, 1103, 1156, 1158, 1159, 1161, 1166, 1167, 1168, 1170, 1171 Password, 1437 Backing up, 1438 Changing, 906 Changing in runtime, 913 for function key, 712 Hierarchy levels, 900 Password aging, 901 Password complexity, 901 Restoring, 1438 Password list, 1437 Password protection, 391, 517, 540 Protection concept, 195 Revoking access rights, 196 Pasting Adjusting screen size, 1380 Color, 1380 Font, 1380 Function key, 1380 Invalid object, 1379 Principle, 1378 Performance features Engineering system, 1461 HMI device, 1463 Performance in telephone networks, 1500 Permitted characters User view, 53 PG/PC interface Connecting online, 1481 Modifiable MPI interface parameters, 1489 Modifiable PROFIBUS interface parameters, 1489 Phone book Printing, 1527
Pin assignment 6XV1440 - 2P for Mitsubishi PG protocol, 1249 Allen-Bradley cable 1747-CP3, 1219 Allen-Bradley cable 1761-CBL-PM02, 1220 Allen-Bradley cable 1784-CP10, 1218 Multipoint cable 1:MP/TP/PC, 1288 Multipoint cable 2:RS422, MP/TP/PC, 1288 Point-to-point cable 1, Point-to-point cable 2, 1275 Point-to-point cable PP1 for Omron, 1289 Point-to-point cable PP2 for Omron, 1289 PLC Connecting, 1196, 1235, 1248, 1261, 1287 MPI parameters, 1131 PROFIBUS parameters, 1074, 1123 PROFINET parameters, 1061, 1111 Reading recipe data record, 1459 Tag, 788 Transferring recipe data record, 1460 PLC tag reconnecting, 780 PLC tags, 398, 399, 401 PLC5, 1223 PN/PN couplers Grouping, 467 Linking Ethernet subnets, 467 Pointer name Area pointer, 1047 Point-to-point communication (PtP), 529 Freeport protocol, 530 Point-to-point connection Allen-Bradley DF1, 1215 Port Renaming, 381 Port numbers, 356 Port options, 461, 1066, 1116 Enable autonegation, 460, 1065, 1115 Monitor, 460, 1065, 1115 Transmission medium/duplex, 460 Transmission rate / duplex, 1065, 1115 Portal view, 133 Position an object , 645 Editing multiple objects, 660 Of objects, 648 Possible cause of error Transferring data, 1090, 1146, 1183, 1310 PPI, 1027 Network, 1030 Network architecture, 1031 S7 200, 1171 Predefined alarm classes, 809, 810
1564
Index
Premium, 1265 Press, 1004 Press key, 1008 PressButton, 975 Print scope, 198 Printable contents, 197 Printing Changing the settings, 198 Creating a cover page, 203 Creating borders, 202 Documentation function, 196 Elements in the library, 202 Elements in the project tree, 201 Non-printable contents, 197 Non-printable objects, 198 Print contents, 200 Printing device view, 270 Printing network view, 270 Process a cover page, 204 Process borders, 204 Specify layout, 199 Specify print layout, 199 Specifying the print area, 209 Structure of printout, 197 Use borders, 201 Use borders and cover pages, 197 Use cover page, 200 Printing a project, 214 Printing of alarms Configuring:printing of alarms, 827 Printing phone books, 1527 Process control phase, 1405 Process data area Module addressing, 509 Module start address, 509 Process image, 510 Basics, 507 I/O access error, 508 Updating, 508 Product support, 276 Enabling, 276
PROFIBUS, 313, 1027, 1075, 1125 Connection with PROFINET, 440 ET 200S in DPV1 mode, 436 HMI connection, 1069, 1119 Network, 1029 OP 73, 1103, 1159, 1161, 1168, 1170, 1171 OP 77A, 1103, 1159, 1161, 1168, 1170, 1171 Parameters, 1070, 1072, 1074, 1120, 1122, 1123 S7 1200, 1068, 1069 S7 200, 1103, 1159, 1168 S7 300/400, 1118, 1119 Standard, 1075, 1125 Universal, 1075, 1125 PROFIBUS cable configuration Optical ring, 315 PROFIBUS communication S7 1200, 1068 S7 300/400, 1118 PROFIBUS DP, 420, 1029 Connection, 1152 PROFIBUS parameters S7 1200, 1070, 1072, 1074 S7 300/400, 1120, 1122, 1123 PROFIBUS profile, 313, 1075, 1125 Different profiles on the same subnet, 313, 1075, 1125 Effect on the transmission rate, 313, 1075, 1125 Meaning of profiles, 314, 1076, 1125 Profile, (See bus profile) PROFINET, 1027 Connection, 1151 Connection with PROFIBUS, 440 Device replacement without exchangeable medium, 463 HMI connection, 1056, 1057, 1105, 1106 S7 1200, 1056 S7 300/400, 1105 PROFINET device name, 449 PROFINET interface, 517, 594 PROFINET IO, 439, 444, 445, 453, 455 Port options, 460, 1065, 1115 PROFINET IO device Assigning a name, 610 Name assignment from the project tree, 611 Name assignment from within the project context, 611 Name assignment via the "Online" menu, 611 PROFINET IO system, 454
1565
Index
PROFINET parameters HMI connection, 1058, 1108 HMI device, 1060, 1109 PLC, 1061, 1111 S7 1200, 1058, 1061 S7 300/400, 1108, 1109, 1111 PROFINET RT class, 440 Program editor General settings, 129, 131, 132 Program execution Cyclic, 542 Project Basics, 175 Closing, 179 Comparing data, 194 compile (overview), 1384 Compiling , 1385 Compiling project data, 188 Creating, 176 Deleting, 179 Download, 1388, 1405 download (overview), 1384 Migrating, 91, 108 multilingual, 1348 multiple connections, 1082, 1138 Multiple connections, 1177 Opening, 176 Saving, 178 Showing properties, 178 Simulation with a tag simulator, 1392 Project data Compiling, 188 Downloading to a memory card, 192 Export alarm, 1317 Export text list, 1330 Exporting a recipe, 1314 Exporting tag, 1325 Importing alarms, 1319 Information on compiling, 187 Information on loading, 189 Loading, 190 Loading to an accessible device, 191 Uploading from a device, 193 Project ID, 1026 Project language, 1342 Activate, 1346 Disabling, 1346
Project languages Changing the editing language, 182 Specifying project languages, 182 System texts, 180, 1349 Use, 180 User texts, 180, 1349 Project library, 39, 722 Adding a copy template, 233 Adding types, 234 Basics, 232 Creating folders, 232 Editing elements, 237 Migrating, 103 Removing elements, 239 Using filter view, 240, 257 Using master copies, 235 Using the element and part views, 231 Using types, 236 Project text Exporting, 1335, 1353 Project texts Application example, 186 Compiling project texts, 183 Displaying reference text, 183, 1352 Exporting all texts, 185 Exporting individual texts, 185 Importing, 186, 1337, 1355 Migrating, 101 Translating individual texts, 1350 Translation into project languages, 180, 1349 Project tree Adding device, 289 Function, 137 Keyboard shortcuts, 161 Reducing automatically, 143 Project view, 135 Properties (CPU), 517 ProSave, 1396 Installation, 51 Protect Function key with password, 712 Protection concept Introduction, 195 Revoking access rights, 196 Protection level, 540 Revoking access rights, 196 Pulse generator Compiling hardware, 32 Pulse stretching, 578
1566
Index
Q
Q address, 385 Q series, 1241 Quantum, 1265
R
R, 313 Racks, 282 Inserting a module, 292 Radius, 745 Range (... - ...) Graphics list, 688 Read continuously Tag, 785 READ_DBL, 35 Reading out Recipe data record, 1459 Reading out a diagnostics buffer, 600 Reading tags, 399 Read-only, 540 Recipe, 864, 866, 867, 1317, 1451 Application example: Machine parameter assignment, 866 Application example:Batch production, 866 Basics, 864, 866 Control, 1453 Creating new, 877 Data flow, 1454 Data record, 867, 1452 Entry, 867 Exporting, 1314 Importing, 1315 Memory requirements, 1467 Use, 866 Use of text lists, 872 Recipe data Migration, 104
Recipe data record Create on the HMI device, 890, 891 Creating, 1457 Creating new, 877 Creating on the HMI device, 890 Deleting, 1459 Editing, 1458 Reading from PLC, 1459 Synchronize with PLC, 1458 Transferring the project, 55 Transferring to PLC, 1460 Use of text lists, 872 Recipe element Creating new, 877 Recipe list, 873 Recipe view, 873 Application, 756 Behavior with screen change, 874 Configuring, 884 Control element, 756 Layout, 756 Operation using the function key, 874 Recipe data record, 868, 875 Simple, 873 Updating, 874 RecipeViewBack, 973 RecipeViewClearDataRecord, 969 RecipeViewGetDataRecordFromPLC, 968 RecipeViewMenu, 969 RecipeViewNewDataRecord, 968 RecipeViewOpen, 970 RecipeViewRenameDataRecord, 972 RecipeViewSaveAsDataRecord, 971 RecipeViewSaveDataRecord, 971 RecipeViewSetDataRecordToPLC, 970 RecipeViewShowOperatorNotes, 972 Recommissioning HMI device, 1406 Reconnecting Tag, 780 Reconnecting a PLC tag, 780 Recording a log file for the modem, 1535 Rectangle Configuring, 675 Inserting, 675 Inserting and configuring, 674 Radius corners X, 755 Radius corners Y, 755 Redoing actions Basics of redoing actions, 215 Redoing actions, 218 Reference junction, 430, 560, 575
1567
Index
Reference language, 1342 Selecting, 1346 Reference object Defining, 651 release, 1006 ReleaseButton, 975 Remote connection cannot be established, 1522 Remote connection from the TS Adapter is not established, 1537 Remote connection to the TS Adapter is not established, 1536 Remote system access to a programming device/ personal computer, 1528 Remove Object from the group, 669 Removing Folder link, 662 Formatting in the alarm text, 823 Rename Screen, 634 Tag, 776 Template, 640 Replacing Module, 297 Replacing devices Limitations on connections, 1370 Principle, 1370 Report System Errors, (See System diagnostics) Created error OBs, 475 Requirements for establishing a remote connection, 1521 Requirements for sending an SMS, 1532 Requirements for sending e-mails, 1533 Required communication instructions, 1534 Reset to factory settings, 1399 ResetBit, 973 ResetBitInTag, 974 Resetting the MPI/PROFIBUS settings, 1496 Resetting the TCP/IP settings, 1488 Resetting the user interface layout, 159 Resource SIMATIC S7 1200, 50 Restore process Authorization, 64 License key, 64, 65 Restore window layout, 158 Restoring, 1438 Data of the HMI device, 1396, 1398 HMI device data, 1412 Restoring data HMI device, 1396, 1398, 1412
Restrictions due to user rights, 163, 164 Recognizing, 163 Retentivity, 507 Rotate Object, 645 RS-232/PIP multi-master cable, 534 RT class, 440 Rules for configuring MPI networks Rules for assigning the MPI address, 309 Rules for network configuration for PROFIBUS networks Assigning device addresses, 309, 310 RUN, 502 Runtime Execution of the function list, 934 Mouse wheel, 54 Simulating, 1390 Start screen, 635 Runtime data Migration, 104 Runtime language, 1342, 1360, 1413 Font, 1365, 1414 Log, 1366 Order for language switching, 1363 Selecting, 1361, 1413 Runtime settings User administration, 899 Runtime start Basic Panel, 1389, 1410 Runtime Stop, 1008
S
S7 1200 Basic Panel, 1051 Communication, 1055 HMI connection, 1057 PROFIBUS, 1068, 1069 PROFIBUS parameters, 1070, 1072, 1074 PROFINET, 1056 S7 1200 V1 Data types, 1094 S7 1200 V2 Data types, 1095
1568
Index
S7 200 Communication, 1163 Connection, 1163 Connection parameters, 1100, 1166 Data types, 1189 Ethernet, 1102, 1158, 1167 MPI, 1161, 1170 Parameters, 1100, 1102, 1103, 1158, 1159, 1161, 1166, 1167, 1168, 1170, 1171 PPI, 1171 PROFIBUS, 1103, 1159, 1168 S7 300 Basic Panel, 1051 Communication, 1104 MPI address, 1133 S7 300/400 Connection parameters, 1156 Data types, 1150 HMI connection, 1106 MPI, 1126 MPI parameters, 1128, 1130, 1131 Parameters, 1156 PROFIBUS, 1118, 1119 PROFIBUS parameters, 1120, 1122, 1123 PROFINET, 1105 PROFINET parameters, 1108, 1109, 1111 S7 400 Basic Panel, 1051 Communication, 1104 MPI address, 1133 S7 connection, 319 TSAP, 330 S7 CPU Work memory, 505 Load memory, 505 Operand area, 505 S7-1200, 30 Web server, 29 S7-1200 modules, 30 S7-PCT, 469 Safety guidelines, 172 Safety instruction Changing the recipe data record in the background, 874 Switching tooltip, 1423 Save Global library, 732 Save table layout, 156 Save user interface Save layout in editors, 156 Save window layout, 156 Save window layout, 157
Saving the user interface, 156 Scaling Applying linear scaling to a tag, 785, 787 Scheduler, 1010 Deactivated task, 1015 Event trigger, 1015, 1018 Function list, 1014 Triggers, 1014 Work area, 1013 Screen Availability for specific devices, 629 Copy, 634 Copying, 1380 Creating, 633 Deleting, 634 Font, 629 Inserting, 634 Move, 634 Rename, 634 Use template, 641 Working steps in creating, 633 Zooming, 632 Screen change, 1002 Screen keyboard Alphanumerical, 1420, 1422 Key assignment, 1420, 1421 KTP400 Basic, 1419 KTP600, KTP1000, TP1500 Basic, 1421 Language behavior, 53 Numerical, 1420, 1422 Screen number, 1026 Screen object Dynamic movement, 697 Screen saver, 23 Screen template, 707 ScreenObjectCursorDown, 947 ScreenObjectCursorUp, 946 ScreenObjectPageDown, 948 ScreenObjectPageUp, 947 Script Updating tag value, 768, 1042 SD card Open force job, 23 Search Hardware catalog, 281 Security system, 1437 Segment diagnostics Graphic display, 619 Icons, 619 Text display, 619 Select Multiple objects, 650
1569
Index
Selecting Multiple objects, 645 Selection changed, 1001 Send clock cycle, 457, 458 Service & Support, 276 Enabling, 276 SetBit, 980 SetBitInTag, 980 SetBitWhileKeyPressed, 981 SetColorBackgroundLighting, 983 SetConnectionMode, 985 SetDeviceMode, 979 SetLanguage, 983 SetTag, 984 Setting Deadband, 821 Delay time, 821 Language, 1424 Languages in the operating system, 1343 Setting AS-i network configuration parameters, 318 Setting language, 1424 Setting parameters for the Ethernet interface, 1486 Adding a dynamic IP address, 1487 Connecting to a subnet, 1486 Deleting dynamic IP addresses, 1488 Modifiable parameters, 1484 Options in the parameter settings, 1484 Setting the communication load, 316 Settings Changing, 133 General, 129, 131, 132 Settings for the PG/PC interface, 1483 Automatic bus parameter detection, 1490 Setting parameters for the MPI interface, 1490 Setting parameters for the PROFIBUS interface, 1492 Show Limit lines on the bar, 735 ShowAlarmWindow, 994 ShowLogonDialog, 992 ShowOperatorNotes, 993 Shutting down Windows XP, 23 Signal board, 389 Inserting, 389 SIMATIC NET DVD for communications processors, 26 SIMATIC S7 Communication partners, 1104, 1160, 1169, 1172 SIMATIC S7 1200 Connection resource, 50 Resource, 50
SIMATIC S7 200 Migrating data types, 114 SIMATIC S7 300/400 Migrating data types, 114 simple alarm view, 1446 Control element, 1447 Operation, 1447 Use, 1446 Simple alarm view, 839 Control element, 840 Operation, 840 Use, 839 simple alarm window Application, 839 Use, 1446 Simple recipe view, 873 Behavior, 888, 1456 Layout, 887, 1455 Menu command, 888, 1455, 1456 Operation, 887, 1455 Simple user view, 1438 Layout, 1438 Operation, 1439 Use, 1438 Simulate hardware, 258 Simulate modules, 258 Simulate software, 258 SimulateTag, 987 Simulating Project with tag simulator, 1392 Simulating devices, 258 Simulation, 54 PLC connection, 54 Runtime, 1390 Size An object, 645 Editing multiple objects, 660 SLC, 1223 Slot Racks, 283 Select, 284 Slot rules, 280 ET 200S, 429 Smoothing, 574 Softkey, 705, 709 global, 707 Software requirements at the plant end Communication instruction "AS_MAIL", 1533 Communication instruction "SMS_SEND", 1533 Communications instruction "PG_DIAL", 1529 Software requirements for AS-AS remote link Communication instruction "AS_DIAL", 1532
1570
Index
Software requirements for the programming device/ personal computer Communications instruction "PG_DIAL", 1530 Software-controlled data flow control, 533 Special characters Alarm text, 46 Special tag (web server), 402 Stamping, 658 Standard PROFIBUS, 1075, 1125 Standard device, 464 Standard slave, 438 Standby Mode, 23 Standby module Substitute value, 435 Start address, 385, 509 Start screen, 635 Start the online and diagnostics view, 590 Start the simulation, 259 Start value Tag, 783, 784 Starting removal, 77 Starting the migration tool, 84 Starting the topology view, 371 Startup Organization blocks, 541 STARTUP Function, 498 STARTUP activities, 500 Startup OB Description, 541 Start-up parameters, 501 Startup program, 541 Startup type, 517 Station Copying, 295 Deleting, 294 Moving, 296 Renaming, 381 Station name, (See device name) Status Module defective, 599 Status of the online connection, 615 STOP, 502 StopRuntime, 988 Storing External graphic, 663 Structure of the cross-reference list, 1339 Structure of the phone book, 1524 Subnet mask, 445
Substitute value Standby module, 435 Supported telephone networks and modems, 1499 Restrictions, 1499 Switch, 757, 1434 Application, 1434 Behavior, 1435 Layout, 1434 Operation, 1434 Type, 757 Switch off, 1009 Switch on, 1009 Switching operating mode, 604 Switchover time, 535 Switchport, 461, 1066, 1116 Symbol Alarm classes, 829 Symbolic addressing of a tag, 769, 1043 Symbolic I/O field, 759 Mode, 760 Text list, 683, 760 Symbolic IO field, 1435 Application, 1435 Behavior, 1436 Operation, 1436 Sync domain, 462, 1067, 1117 Synchronization (custom web pages), 395 Synchronous Transferring data, 1142, 1185, 1306 Syntax for AWP commands, 398 System alarm, 806 Meaning, 843, 844, 848, 853 System diagnostics Created blocks, 475 General settings, 485 Introduction, 472 Send alarms, 485 Settings for "PLC in STOP", 488 Settings for configuring alarms, 486 System event, 806 Meaning, 843, 844, 847, 848, 850, 852, 853, 854, 855, 857, 859, 860 Parameters, 843 System events Configuring, 815 System function Application, 929 Function list, 931 In the function list, 929 Usage, 928 Use, 929
1571
Index
System functions, 927 AcknowledgeAlarm, 967 ActivateCleanScreen, 943 ActivatePreviousScreen, 944 ActivateScreen, 941 ActivateScreenByNumber, 942 AdjustContrast, 940 AlarmViewAcknowledgeAlarm, 966 AlarmViewEditAlarm, 965 AlarmViewShowOperatorNotes, 967 AlarmViewUpdate, 966 Available, 937 CalibrateTouchScreen, 954 ChangeConnection, 991 ClearAlarmBuffer , 963 ClearAlarmBufferProTool , 964 DecreaseFocusedValue, 989 DecreaseTag, 990 EditAlarm, 945 GetGroupNumber, 961 GetPassword, 961 GetUserName, 960 GoToEnd, 950 GoToHome, 950 IncreaseFocusedValue, 948 IncreaseTag, 949 InvertBit, 951 InvertBitInTag, 952 InvertLinearScaling, 953 LinearScaling, 962 Logoff, 939 Logon, 945 PageDown, 978 PageUp, 978 PressButton, 975 RecipeViewBack, 973 RecipeViewClearDataRecord, 969 RecipeViewGetDataRecordFromPLC, 968 RecipeViewMenu, 969 RecipeViewNewDataRecord, 968 RecipeViewOpen, 970 RecipeViewRenameDataRecord, 972 RecipeViewSaveAsDataRecord, 971 RecipeViewSaveDataRecord, 971 RecipeViewSetDataRecordToPLC, 970 RecipeViewShowOperatorNotes, 972 ReleaseButton, 975 ResetBit, 973 ResetBitInTag, 974 ScreenObjectCursorDown, 947 ScreenObjectCursorUp, 946 ScreenObjectPageDown, 948 ScreenObjectPageUp, 947 SetBit, 980 SetBitInTag, 980 SetBitWhileKeyPressed, 981 1572 SetConnectionMode, 985 SetDeviceMode, 979 SetLanguage, 983 SetTag, 984 ShowAlarmWindow, 994
System limits HMI device, 1463 System memory, 517, 539 Diagnostics buffer, 509, 612 Operand areas, 505 process image input/output, 507 System requirement for WinCC Basic, 59 System requirements STEP 7 Basic, 58 System-defined text lists Editing, 224 Modifying texts, 224 System-relevant information Module information, 592 Vendor information, 592
T
Table Connection, 1031
Index
Tag absolute addressing, 768, 1042 Acquisition cycle, 784, 791, 801 Acquisition mode, 784 Addressing, 771 Changing the PLC, 788 Comment, 774 Configuration, 777 Configuring several tags, 778 Connection to PLC, 771 Copy, 776 Creating external tags, 771 Creating internal tags, 774 Data type, 774 Deleting, 777 Displaying values, 802 Event, 790 Exporting, 1325 External tag, 767, 1041 Importing, 1327 in Runtime, 784 Index tag, 788, 789 Indirect addressing, 788, 789 Internal tag, 770, 1044 Length, 774 Limit range, 781 Limit value, 782 Linear scaling, 785, 787 Maximum length, 53 Multiplexing, 788 Name, 774 Object list, 773 Output in alarm, 822 Read continuously, 785 reconnecting, 780 Rename, 776 Start value, 783, 784 symbolic addressing, 769, 1043 Update, 785, 791 Tag data Structure for the import, 1328, 1333 Tag import Tag data structure, 1328, 1333 Tag list Indirect addressing, 788, 789 Tag simulator, 1394 Tag table Default, 766, 1040 for HMI devices, 766, 1040 user-defined, 766, 1040 Tag value Output, 802
Tags Basics, 765, 1039 Migrating, 97 Migration, 110 Task, 1012 Deactivate, 1015 Task card, 630 Changing the pane mode, 152 Function, 150 Hardware catalog, 274 Reducing automatically, 143 Tools, 641 Task Card Online Tools, 592 TCI (Tool Calling Interface), 468 TCON_Param, 353 TCP Characteristics, 352 Port numbers, 356 Telephone book at TeleService, 1498 Telephone networks which can be used, 1499 TeleService Meaning of the icons, 1525 AS_DIAL, 1530 Callback variants, 1517 Establish connection to AS, 1530 Global telephone book, 1498 TeleService callback options, 1519 TeleService functionality, 1498 TeleService telephone book, 1498 Temperature coefficient, 573 Temperature compensation, 560 template Template, 640 Template, 705 Copy, 640 Creating, 639 Deleting, 640 Global screen, 638 Inserting, 640 Move, 640 Rename, 640 Use in screen, 641 Terminal modules and electronic modules, 558 Terminating the remote connection, 1522 Text Button, 758 Text field, 761 Text field, 761 Size, 762 Text field length Asian languages , 1416
1573
Index
Text list Application, 677 Bit (0, 1), 682 Bit number (0 - 31), 683 Creating, 678 Exporting, 1330 Importing, 1332 Symbolic I/O field, 683, 760 Value/Range, 680 Text lists Introduction, 221 System-defined, 222 Use in recipe data records, 872 User-defined, 222 Texts Migrating, 101 Third-party drivers Communication, 1190 Special features, 1191 TIA Portal Exiting, 129 Starting, 129 Time error interrupt OB, 546 Time expired, 1010 Time of day Setting the time of day in the Online and Diagnostics view, 606 Time stamp, 814 Time stamping, 561 Time-delay interrupt OB, 543 Time-of-day, 517 Time-of-day function Basics, 523 Clock parameters, 524 Reading the time of day, 524 Setting the time of day, 524 Time-of-day format, 523 Time-of-day synchronization, 517 Toggle Between runtime languages, 1415 Between Runtime languages, 1360 Tool Calling Interface (TCI), 468 Toolbar Order, 645, 654 Tools, 641 Tooltip display, 1423 Topology discovery, 462, 1067, 1117
Topology view Adding device, 289 Adopt devices identified online, 384 Adopt port interconnections identified online, 384 Compare offline/online, 376 Configured topology, 372, 373 Diagnostics status in the graphic view, 374 Diagnostics status in the table view, 375 Differences compared with the network view, 370 Functions, 370 Hardware and network editor, 268 Interconnecting ports, 377 Touch operation IO field, 1428 TP177A Loading a project, 52 TraceUserChange, 989 Transfer card, (See Memory Card) Transferring Recipe data record, 1460 Transferring data Area pointer, 1045, 1076, 1133, 1172, 1297 Area pointer screen number, 1081, 1134, 1173, 1298 Coordination area pointer, 1080, 1136, 1175, 1301 Data record are pointer, 1305 Data record area pointer, 1085, 1140, 1179 Date/time area pointer, 1077, 1078, 1135, 1173, 1299 Date/time PLC area pointer, 1135, 1174, 1300 Job mailbox, 1088, 1144, 1181, 1308 Job mailbox area pointer, 1083, 1138, 1177, 1302 Operator input in the recipe view, 1087, 1143, 1180, 1307 Possible cause of error, 1090, 1146, 1183, 1310 Project ID area pointer, 1082, 1137, 1176, 1302 Triggering by means of a configured function, 1090, 1145, 1183, 1310 With synchronization, 1142, 1185, 1306 Without synchronization, 1086, 1141, 1184, 1305 Transferring the project HMI device, 55 Recipe data record, 55 Translate Editor, 1348 Transmission medium/duplex, 460 Transmission rate / duplex, 1065, 1115 Transparency In graphic, 661
1574
Index
transparent color, 742 Display on panels, 742 Display on the panel HMI, 1429 Trend view, 745, 1431 Application, 1431 Button, 746 Configuring for values from the PLC, 803 Layout, 1431 Operation, 1432 Operator control, 1432 TrendViewBackToBeginning, 959 TrendViewCompress, 956 TrendViewExtend, 955 TrendViewRulerLeft, 957 TrendViewRulerRight, 957 TrendViewScrollBack, 955 TrendViewScrollForward, 954 TrendViewSetRulerMode, 958 TrendViewStartStop, 959 Trigger tag, 814 Triggering by means of a configured function Transferring data, 1090, 1145, 1183, 1310 Triggers, 1014 Event trigger, 1015, 1018 TS adapter, 54 TS Adapter Installing additional software, 1504 TS Adapter MPI Brief description, 1504 Default parameter assignment, 1505 Direct connection, 1505 Establishing a modem connection, 1506 Establishing the direct connection, 1506 Exporting adapter parameters, 1510 Importing adapter parameters, 1510 Modem connection, 1506 parameter Assignment, 1508 Parameter assignment , 1508 Parameter assignment options, 1507 Principle of operation, 1505 Restoring the default parameter assignments, 1509 Setting up access protection, 1518 TS Adapter IE Brief description, 1511 Default parameter assignment, 1512 parameter Assignment, 1515 Principle of operation, 1512
TS Adapter IE Basic Connection to the GSM network, 1514 Connection to the telephone network, 1513 Connection to the telephone network through an external modem, 1514 Connection types, 1513 TSAP ASCII code table, 359 Structure, 330, 357 TSAP assignment Examples, 359 Type Library, 724 Types of DP slave, 425
U
UART data transmission, 529 UDP Characteristics, 352 Port numbers, 356 Underflow, 575 Undoing actions Basics of undoing, 215 Undoing last action, 217 Undoing multiple actions, 217 Uniqueness of object names, 88 Universal PROFIBUS, 1075, 1125 unlock Users, 914 Unplugged module, 286 Unspecified CPU, 290 Update Tag, 785, 791 Update cycle, 801 Update time, 458 UpdateTag, 944 Updating Operating system, 1400 Updating the operating system, 1398 USB network card, 31 Use, 866 Of recipes, 866 Screen navigation function keys, 715 simple alarm view, 1446 simple alarm window, 1446 Simple user view, 1438 System function, 929 Use global assignment Function key, 638
1575
Index
Useful information on configuring the TS Adapter MPI, 1507 User administration, 895 Migration, 104 Object with access protection, 917 Runtime settings, 899 Setting up, 920 User change, 1002, 1017 User data Area, 510 Backing up, 1438 Restoring, 1438 User group, 1437 Administer authorizations, 907 Assigning, 925 Assigning users, 905 Change displayed name, 908 Changing in runtime, 914 Changing the name, 907 Creating, 924 Deleting, 908 Managing, 907 Unauthorized, 915 User interface Details view, 152 Inspector window, 148 Maximizing the work area, 142 Minimizing the work area, 142 Overview window, 153 Portal view, 133 Project tree, 137 Project view, 135 Task card, 150 Views, 133 Work area, 140 User interface language, 1342 Selecting, 1345 User view, 909 Application, 736 Configuring, 910 Layout, 736 Number of lines, 736 Permitted characters, 53 Simple user view, 909 User-defined functions In function lists, 931 User-defined text lists Creating, 222 Editing, 223 Editing value ranges and texts, 224
Users, 1437 Admin, 1443 Assigning a user group, 905 Changing, 913 Changing the name, 906 Changing, touch operation, 1442 Creating, 904, 925, 1439 Creating in runtime, 911 Creating, touch operation, 1439, 1441 Deleting, 907, 1443 Deleting in runtime, 914 Logging logons, 919 Logoff, 1440 Logon, 914 Managing, 906, 912 Unlock, 914 Updating after change of user, 1017 Using a TS Adapter for TeleService, 1502 Using frames and cover pages from the library, 203 Using tags, 737 Using the on-screen keyboard, 163
V
Valid Data type, 1197, 1240, 1249, 1264, 1276, 1289 Data types, 1094, 1095, 1150, 1189 Valid data type Allen-Bradley DF1, 1221 Value change, 1010 Value/Range Text list, 680 Vertical movement Animation, 699 Vertical radius, 740 Views of the cross-reference list, 1339 Virtual drives, 21
W
Warm restart, 499 Watch table Loading data blocks during an active control job, 36 Multiple access to the same CPU, 35 Rounding floating-point numbers, 35 Watchdog time, 458 Web application, 394 Web Control DB, 409 Web pages in browser, 413
1576
Index
Web server, 390, 391, 394 Enable, 392 HTTPS, 392 S7-1200, 29 When dialog is closed, 1002 When dialog is opened, 1002 WinCC flexible project Migrating, 91, 108 WinCC flexible Runtime Closing, 1411 Window layouts Changing order, 158 Deleting window layouts, 158 Wire break, 574 Wireless LAN/PB link, 440 Wizard Device wizard, 1311 Work area Embedding floating elements, 145 Floating elements, 145 Function, 140 Maximizing, 142 Maximizing elements, 147 Minimizing, 142 Minimizing elements, 147 Saving a layout of editors and tables, 159 Splitting, 144 Switching between elements, 148 Using grouped elements, 145 Work memory, 505 Working step to create screens, 633 Working with the phone book, 1523 WRIT_DBL, 35 Writing tags, 401 WWW (instruction), 408
X
xlsx file, 1319, 1326, 1330, 1331 XOFF, 31 XON, 31
Z
Zoom Adjusting the zoom setting, 264, 266, 269 Keyboard shortcuts, 277 Zooming Screen, 632
1577