102602994 wincc-course-ppt

Editor's Notes

• #2: Introduction The interface between the human and the machine is called the human machine interface or HMI for short connects the world of automation with the individual requirement of the operator . Operator control and monitoring is about managing the process, about availability and productivity.
• #3: Process visualization The process is visualized on the HMI device. The screen on the HMI device is dynamically updated. This is based on process transitions. Operator control of the process The operator can control the process by means of the GUI. For example, the operator can preset reference values for the controls or start a motor. Displaying alarms Critical process states automatically trigger an alarm, for example, when the set-point value is exceeded. Archiving process values and alarms The HMI system can log alarms and process values. This feature allows you to log process sequences and to retrieve previous production data. Process values and alarms logging The HMI system can output alarms and process value reports. This allows you to print out production data at the end of a shift, for example. Process and machine parameter management The HMI system can store the parameters of processes and machines in recipes. For example, you can download these parameters in one pass from the HMI device to the PLC to change over the product version for production.
• #4: WinCC flexible Engineering System The WinCC flexible Engineering System is the software for handling all your essential configuring tasks. The WinCC flexible edition determines which HMI devices in the SIMATIC HMI spectrum can be configured. WinCC flexible Runtime WinCC flexible Runtime is your software for process visualization. You execute the project in process mode in Runtime. WinCC flexible options The WinCC flexible options allow you to expand the standard functionality of WinCC flexible. A separate license is needed for each option.
• #11: Multi Panels They are used in a wide range of industries and applications which can be extended by means of the Multi Panel options, e.g. presentation of HTML documents via Microsoft Pocket Internet Explorer. The disk-less and fan-less design permits their use even where dust or vibration limits the use of a PC. Short power-up times mean the Multi Panels are soon ready to use. Panels PCs SIMATIC Panel PCs are suitable for use in control cabinets, consoles and control panels. Typical areas of application can be found in both production and process automation.
• #12: The engineering tools of the SIMATIC WinCC flexible range are based on one another. The available editors largely depend on the respectively configured target systems and their functions. A more comprehensive engineering tool such as WinCC flexible Standard also offers the facilities of the smaller engineering tools, e.g. WinCC flexible Compact or Micro. Upgrading of a smaller engineering tool to a larger one is possible using a Power pack. An exception is WinCC flexible Micro. The scope of functions of the WinCC flexible engineering tools already includes project support for the Runtime options available for SIMATIC Panels or WinCC flexible Runtime, independent of the RT licenses purchased. Separate licensing is required for the target system in order to use the configured Runtime options.
• #13: • WinCC flexible Micro - Micro Panels: OP 73micro, TP 170micro, TP 177micro • WinCC flexible Compact - - Mobile Panels: Mobile Panel 177 - 70 Series Panels: OP 73, OP 77A, OP 77B - 170 Series Panels: TP 170A, TP 177A, TP 170B, TP 177B,OP 170B, OP 177B - C7 devices: C7-635 (Touch), C7-635 (Keys) • WinCC flexible Standard - 270 Series Panels: TP 270, TP 277, OP 270, OP 277 - 270 Series Multi Panels: MP 270B, MP 277 - 370 Series Multi Panels: MP 370 - C7 devices: C7-635 (Touch), C7-635 (Keys) , C7-636 • WinCC flexible Advanced - Standard PC SIMATIC Panel PC Panel PC 477, Panel PC 577, Panel PC 677, Panel PC 877 SIMOTION Panel PC: P012K, P015K, P012T, P015T, PCR, PCR-Touch SINUMERIK Panel PC: OP010, OP012, OP015, TP012, TP015, OP015A
• #16: Menus and Toolbars You can access all the functions provided by WinCC flexible by means of its menus and toolbars. When the mouse pointer is moved over a function, a ToolTip appears. Work area Project objects are edited in the work area. All WinCC flexible elements are arranged on the borders of the work area. With the exception of the work area, you can organize, configure and, for example, move or hide any of the elements to suit your individual requirements. Project View All component parts and editors available in a project appear in a tree structure in the Project View. Folders are provided as sub-elements of each editor in which you can save objects in a structured way. In addition, direct access to the configured objects is available for screens, recipes, scripts, protocols and user dictionaries. In the project windows you have access to the device settings of the HMI device, the language settings and the version management. Property view The Property View is used to edit object properties, e.g. the color of screen objects. The property view is only available in specific editors. Toolbox The toolbox contains a selection of objects which you can add to your screens, e.g. image objects or operator control elements. In addition, the toolbox also provides libraries containing object templates and collections of faceplates. Library The "Library" is an element of the Toolbox view. The "Library" provides access to screen object templates. You can always add screen objects and thus increase programming efficiency either by multiple use or reuse of object templates. The library is your central database for storing frequently used objects, such as screen objects and tags. Output View The output window displays system alarms generated, for example, in a project test run. Object view The "Object View" shows all elements of the area selected from the "Project View". Note With the exception of the work area, you can show or hide all windows in the "View" menu.
• #17: As part of the device settings of a WinCC flexible project, you specify which services should be available on the HMI device during runtime also you can change the device type
• #19: Acquisition cycle 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. If the acquisition cycle is set too low, it will strongly increase the communication load on the process. Steps to add new cycle Select the "Add cycle" command in the "Cycles" pop-up menu or press two clicks on the empty line. The cycles' editor will open. The cursor will be placed in the row of the newly created cycle. In the remaining steps, adjust the default settings as needed. Select the desired "Cycle unit". Select the desired value for the "Cycle time". The available selection of values varies depending on the cycle unit selected. 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 available values are always an integer multiple of the value of the cycle unit. Enter a name for the cycle in the "Name" field. As an option, you can enter a comment regarding the use of the cycle.
• #20: Parameters Tab The parameters tab is divided into 3 parts Part1 : HMI device Baud Rate : in this part you specify the baud rate of the communication between the PLC and the HMI device (bits/sec). Address : HMI address which must be the same as the address you specify from the HMI control panel itself . Part2 : Network in this part you specify the protocol you will use for data interchange between the HMI and the PLC. Part3 : PLC device In this part you specify the PLC settings PLC address (configured from the H/W configuration software) Expansion slot (slot number of the PLC on the Rack) Rack (Rack number)
• #21: Types of TAGs External tags enable the communication (data exchange) between the components of an automation process, e.g. between the HMI device and the PLC. Internal tags is used for the programming on the HMI and doesn’t go through the connection of 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 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 your configuration, create tags that point to specific PLC addresses. The HMI reads the value from the defined address, and then displays it. The operator may also enter values on the HMI which will be written to the relevant PLC address.
• #23: To create screens, you need to take the following initial steps: • Create a draft of the process visualization structure, i.e. define the structure and the number of screens. Example: Process partitions can be visualized in separate screens and merged in a master screen. • Define your screen navigation control strategies. • Adapt the template. The template which is stored in WinCC flexible for the selected HMI device applies to all your project screens. In this template, you can define objects locally and assign global functions keys. For some of the HMI devices, you can store the objects you want to integrate into all screens in the permanent window. • Create the screens. Use the following options of efficient screen creation: – Create a screen structure in the "Screen Navigation" editor. – Working with libraries – Working with faceplates – Working with layers
• #24: In WinCC flexible, you create screens which 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 process screen which was created in WinCC flexible. With the help of this screen, you could operate and monitor the mixing unit of a fruit juice manufacturing system. Fruit juice base is supplied from various tanks to a mixing unit. The screen indicates the filling levels of the tanks and of the mixer. The screen also contains operator control elements for the valve units and for the mixer motor. Screen design You add screen elements you need for process visualization, and configure these to suit the requirements of your process. A screen may consist of static and dynamic elements. • Static elements such as text or graphic objects do not change their status in runtime. The tank labels shown in this example of a mixing plant are such static elements. • Dynamic elements change their status based on the process. They visualize current process values which are output from the memory of a PLC or operator station, in the form of alphanumeric displays, trends and bar graphs. Operator input boxes also belong to the category of dynamic elements. The filling level values of the tanks in our example of a mixing plant also belong to the category of dynamic screen objects. The PLC and the operator station exchange process values and operator input data by means of tags.
• #25: 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. It contains an image of the function keys, for example, provided the selected HMI device is equipped with such keys. Other properties such as the screen resolution, fonts and colors are also determined by the characteristics of the selected HMI. Function keys and softkeys A function key is a physical element of the operator station. You can assign one or several functions in WinCC flexible. 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 assigned local functions are softkeys. They 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 softkeys. The operator control elements for the valve and the motor in our example of a mixing plant represent softkeys.
• #26: Navigation All configured screens must be integrated into the operator control system, in order to enable runtime access to these at the operator station. You have various options of configuring these functions: • Use the "Screen Navigation" editor to define the screen structure and configure the entire screen navigation system. • You use the "Screen" editor to configure buttons and function keys for calling other screens.
• #27: "Screen Navigation" editor The "Screen Navigation" editor is used for the graphics configuration of the navigation between several screens. This editor allows you to organize your project screens in a hierarchical structure. Operators can use the navigation control in runtime to navigate between the various screens of the structure, for example, to change to the parent screen, or to the neighboring screen. In addition to these structured connections, the "Screen Navigation" editor also allows you to generate direct screen connections, regardless of the given structure. Open To open the "Screen Navigation" editor, double-click on the "Screen Navigation" are under the "Device Settings" in the project view.
• #28: Using the navigation control You can open a navigation control in all screens. The navigation control contains a number of preconfigured screen navigation buttons. These buttons can be used in runtime to call further screens of the project. Customizing the navigation control The navigation control is adapted in the "Screen Navigation" editor: • You can display or hide the navigation control. • You can configure the navigation control and the command buttons contained in it The button is disabled if it is not assigned a target. In this case, the button appears in runtime without a label.
• #29: Note: The Navigation bar automatically created after using the screen navigation You can enable and disable any button from the navigation control also you can customize the appearance of the button
• #30: Objects are graphic elements which you use to design the process graphics of your project. The "Toolbox" contains various types of objects which are frequently required for use in process screens. • "Simple objects" Simple objects are graphic objects such as the "Line" or "Circle" and standard operator control elements, such as the "I/O field" or "Button". • "Enhanced objects" These objects provide an enhanced functional scope. One of their purposes is to display processes dynamically, e.g. integrating bars or Active X controls in the project, such as the Sm@rtClient view. • "User-specific controls" In this object group, you can add ActiveX controls which are registered in the Windows operating system of your PG / PC to the toolbox, and thus integrate them into your project. • "Graphics" Graphical objects e.g. of machinery and plant components, measuring equipment, control elements, flags and buildings are displayed thematically in a directory tree structure. You can also create shortcuts to your graphic files. External graphics that are placed un this directory and parent directories are shown in the toolbox window and thereby integrated into the project. • "Library" A library contains object templates such as graphics of pipes, pumps, or default buttons. You can integrate multiple instances of a library object in your project, without any need to reconfigure these. The WinCC flexible software package includes libraries. You may also store user-defined objects and faceplates in user libraries. The "Faceplates" represent preconfigured object groups. Some of their properties, but not all of these, can be configured at the relevant place of their application. The faceplates can be edited from a central location. The use of faceplates helps you to reduce the work involved in configuration and ensure uniform project design.
• #45: Name The data log may be given any desired name, but the name must include at least one letter or number. Memory location The data log may be stored in an ODBC database (only on a PC) or in a separate "*.csv" file. Select "File" or "Database" as the storage location correspondingly. Depending on the configuration of the HMI device, you can select the local hard disk of the PC or the storage card of the panel or, if present, a network drive as "path." If you have chosen an ODBC database as the storage location, you can accept the name given by the system (system-defined data source name) or enter one yourself (user-defined data source name). Size The size of a log is calculated as follows: The number of items * the length of each tag value to be logged.
• #46: Logging method Here you can specify what should happen when the log is full. You can choose one of the following options: Circular log: When the log is full, the oldest entry will be overwritten. Segmented circular log: Multiple logs of the same size will be created and filled one after the other. When all logs are completely full, the oldest log is overwritten. Display system message when: a defined fill level is reached a system message is displayed. Trigger event: The "Overflow" event is triggered as soon as the log is full.
• #47: Start-up behavior Under Enable you can specify that logging starts when runtime is started. Enable the checkbox "Enable logging at runtime start." You can also control the behavior at runtime start in other ways. Enable "Reset log" if you want to overwrite previously logged data with the new data or "Append data to existing log" if you want to append new data to an existing log. Note :You can use system functions to control the Restart of a log during runtime. "Comment" Here you can enter descriptive text regarding the log.
• #54: Tasks of the alarm system • Visualization on the HMI: To report events or states that occur in the plant or the process. A state is reported as soon as it occurs. • Reporting: Alarm events are output to a printer. • Logging: Alarm results are saved for further editing and evaluation.
• #55: Acknowledging Alarms For alarms displaying critical or hazardous operating and process states, a stipulation can be made requiring the plant operator to acknowledge the alarm. Alarm states: The following alarm statuses exist for discrete alarms and analog alarms: • When the condition for triggering an alarm is satisfied, the alarm status is "Activated." Once the operator has acknowledged the alarm, it assumes the "Activated/acknowledged" status. • When the condition for triggering an alarm no longer applies, the alarm status is "Activated/deactivated." Once the operator has acknowledged the deactivated alarm, it has "Activated/deactivated/acknowledged" status. Each occurrence of an alarm status can be displayed and logged on the HMI device as well as printed out.
• #56: When configuring alarms, you can specify whether alarms must be acknowledged individually by the operator or whether alarms in the same alarm group can be acknowledged together. It is helpful to use alarm groups, for example, when alarms are caused by the same error.
• #57: Alarm classes mainly determine how alarms will appear when they are displayed on the HMI device. Alarm classes are also used to group alarms for various means of display. WinCC flexible has both predefined alarm classes and the option to configure user-defined alarm classes.
• #58: Available alarm class settings The following settings can be defined for each alarm class: • Acknowledge: Alarms in this class must be acknowledged. • Texts, colors, and flash modes to identify each alarm status when alarms are displayed • An alarm log for logging all events related to alarms in this class. • A text placed in front of the alarm number to indicate the alarm class when alarms are displayed on the HMI device. • An e-mail address to which all messages about events related to the alarms in this class will be sent.
• #59: Example We want to make a warning when a motor works. the feed back of the motor contactor comes on the input (I0.0) so the alarm Text = Main motor ON Class = warning Trigger tag = motor_tag (IW0 (input word 0)) Trigger bit = 8 (not bit 0 why) Because the IW 0 starts with the bit 0 in the input byte 1 and ends with bit 7 in the input byte 0
• #61: • Alarm view The alarm view is configured for a certain screen. More than one alarm can be displayed simultaneously, depending on its configured size. More than one alarm view can be configured for different alarm classes and in different screens. The alarm view can be configured in such a way that it includes only one alarm line. • Alarm window The alarm window is configured in the screen's template and is thus a component of all screens in a project. More than one alarm can be displayed simultaneously, depending on its configured size. An event can trigger closing and reopening of the alarm window. Alarm windows are saved in their own layer for the practical reason that this allows them to be specifically hidden during the configuration. Alarm indicator The alarm indicator is a configured graphic symbol that is displayed on the screen when an alarm activates. The alarm indicator is configured in the screen's template and is thus a component of all screens in a project. The alarm indicator can have one of two states: • Flashing: At least one unacknowledged alarm is pending. • Static: The alarms are acknowledged but at least one of them is not yet deactivated. Function lists can be used to configure HMI device responses.
• #62: Introduction In runtime, alarms can be stored in logs for later evaluation. When configuring the logging of alarms and alarm classes, the user defines the log in which the alarms are to be stored and whether just the alarm events are stored or the associated alarm texts and error location, too. Several steps are involved in alarm logging: • Creating and configuring alarm logs When creating an alarm log, the following must be defined: – General settings, e.g. name, size, storage location – Behavior at runtime start – Behavior when the log is full • Configuring logging of the alarms in an alarm class An alarm log can be specified for each alarm class in which the alarm events are stored during runtime. • Further processing logged alarms The logged alarms can be evaluated directly in your WinCC flexible project, e.g. in an alarm view, or via another application, e.g. Excel.
• #63: Logging method Here you can specify what should happen when the log is full. You can choose one of the following options: – Circular log: When the log is full, the oldest entry will be overwritten. – Segmented circular log: Multiple logs of the same size will be created and filled one after the other. When all logs are completely full, the oldest log is overwritten. – Display system message : When a defined fill level is reached a system message is displayed. – Trigger event: The "Overflow" event is triggered as soon as the log is full.
• #66: Introduction Recipes are a collection of associated data, e.g. machine configuration or production data. You can transfer these data, for example, from the HMI device to the controller in a single step in order to change the production variant. If you have programmed directly at the machine, for example, you can transfer the data to your HMI device and write these to the recipe. Examples of recipe applications Recipes are used in the manufacturing industry and in machine building. These two examples illustrate typical applications that you can implement with the recipe functionality of the WinCC flexible engineering system: Machine parameter assignment One field of application for recipes is the assignment of machine parameters in the manufacturing industry. A machine cuts wooden boards of various sizes to specified dimensions and drills holes. Depending on the board size, the guide rails and drill must be moved to a new position. The required position data are stored as data records in a recipe. You reassign the machine parameters using "Teach in" mode if, for example, a new board size is to be processed. You transfer the new position data directly from the PLC to the HMI device and save it as a new data record. Batch production Batch production in the food processing industry represents another field of application for recipes. A filling station in a fruit juice plant produces juice, nectar, and fruit drinks in a variety of flavors. The ingredients are always the same, differing only in their mixing ratios. Each flavor corresponds to a recipe. Each mixing ratio corresponds to a data record. All of the required data for a mixing ratio can be transferred to the machine control at the touch of a button.
• #67: Each recipe represents a drawer of the file cabinet shown, and thus precisely one product. If the fruit juice mixing plant is producing orange, apple, and tropical fruit flavors, you would then configure one recipe for each flavor.
• #68: You define the recipe elements in the recipe. A recipe element consists of the display name and a tag. The display names are indicated in the recipe data records and on the HMI device in the recipe view. In Runtime, the appropriate tag value is read from the controller or transferred to the controller.
• #69: Editing recipe data records You can edit recipe data records during configuration or in runtime on the HMI device. During configuration, you can define recipes in the "Recipes" editor in the "Elements" tab. You can enter values in the recipe data records in the "Data records" tab. During runtime, you have the option of entering recipe data record values directly on the HMI device or importing them via a CSV file. You can also export the recipe data records to a CSV file.
• #70: Introduction The WinCC flexible ES offers you two configuration options of viewing and editing recipes and their corresponding data records in Runtime on the HMI device: Recipes view Recipe screen Recipes view The recipe view is a screen object that is configured in the "Screens" editor. For example, you can specify what operating function the recipe view will have in Runtime: The recipe view shows recipe data records in tabular form. The Recipe view is particularly useful if data records are small in size or only a few values are to be modified.
• #71: Introduction With structures you bundle a number of different tags that form one logical unit. Structures are project global data and apply to all HMI devices within the entire project. Principle For instance, the various states of a valve can be replicated by means of four tags. With a structure, the different states can be united. Within the structure you set up a structure element for each tag. To the structure element you assign the properties that the tag created from it should include, e.g. data type.
• #73: Structures are used in faceplates. In the faceplate you can assign the structures a dynamic property as a data type. A respective dynamic property is set up for each structure element in the faceplate. You can link the dynamic property with the properties of the objects included in the faceplate. In this way you can pre-configure the faceplate so that every faceplate instance that is created from it possesses the same dynamic control. in the faceplate instance with a tag of a structure data type. This tag provides the dynamic property with values in Runtime.
• #74: Faceplates are objects that you compile from existing screen objects. Faceplates offer the following advantages: Central modification Reuse in other projects Reduce configuration time Faceplates are created and edited in the Faceplate Designer. The faceplates you create are added to the "Project library", and can be inserted into screens in the same way as other objects.
• #75: Establish the faceplate properties under "Properties" in the "Faceplate configuration" dialog. The dialog consists of the list of "Interface" and the list of "Inner objects". Specify the properties of the faceplate and the faceplate tags under the "Interface" list. The properties included here can be configured in the faceplate instance just the same as all the other object properties. The symbol identifies dynamic properties. Dynamic properties can be interconnected with process values or animations of the objects included in the faceplate. In the faceplate instance, the dynamic properties are listed in the Properties view under the "Properties" group under "Dynamic interfaces". These properties will be linked with a tag that provides the properties with values during runtime. The symbol identifies a static property. You configure static properties directly in the Screen Editor. In the faceplate instance, the static properties are listed in the Properties view under the "General" group. The faceplate tags can be directly linked to an object contained within a faceplate, e. g. to an IO field. The list "Inner objects" contains all the properties of the objects included in the faceplate. The properties will be listed in a tree structure. Fields with a dark blue background identify properties that you can "control dynamically" with tags. Fields with a light blue background identify properties whereby you can only edit the values. Those properties are therefore considered "static properties."
• #76: You can create an interconnection between the "Interface" list and the list of "Inner objects" by means of drag-and-drop. If an interface is linked with an included object, the property of the object changes dependent on the settings on the faceplate instance. In addition, you can define new properties in the interface and link these with a property of an included object. The faceplate consists of, e.g. an ellipse, an IO field and a button. Link the "Font" property of the IO field with the "Font" property of the faceplate.
• #79: 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 the user, for example Mr. Foreman, a specific access to the project. However, a user Foreman does not exist at the end customer. Similar difficulties arise, for example, when different projects on a plant are to be integrated into one project in process engineering. In order to integrate the projects you have to be able to access the data of each individual project without restriction during commissioning. Authorizations are therefore not assigned directly to users in the user administration, but rather to user groups. The user Foreman is then, for example, assigned to the "Operator" user group and receives its authorizations. Authorizations do not have to be assigned individually to each user, only to the user group. In a different environment, for example at the customer, there are other users. The authorizations and user groups of the project, however, remain unchanged. Only the users are re-assigned to the user groups, for example "Operator." The user administration separates the administration of the users from the configuration of the authorizations. This ensures flexibility at the access protection.
• #80: The "Groups" table shows the existing user groups. When you select a user group in this table, the "Group 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.
• #85: Layout The user view contains four columns for the user, password, group and log-off time. The passwords are encrypted by means of asterisks. All users on the HMI device system are displayed in the User view to the administrator or to a user with administrator authorizations. When user administration authorization is lacking, only the personal user entry is displayed. Operation Depending on the configuration you can: Manage users, e.g. create, delete. Change existing user data. Export or import user data.
• #87: The station address is defined from the control panel of the HMI device it self