Transcription

1 (Design template for your project) WinCC Comfort V15, SiVArc V15 Siemens Industry Online Support

2 Legal information Legal information Use of application examples Application examples illustrate the solution of automation tasks through an interaction of several components in the form of text, graphics and/or software modules. The application examples are a free service by Siemens AG and/or a subsidiary of Siemens AG ( Siemens ). They are nonbinding and make no claim to completeness or functionality regarding configuration and equipment. The application examples merely offer help with typical tasks; they do not constitute customer-specific solutions. You yourself are responsible for the proper and safe operation of the products in accordance with applicable regulations and must also check the function of the respective application example and customize it for your system. Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the application examples used by technically trained personnel. Any change to the application examples is your responsibility. Sharing the application examples with third parties or copying the application examples or excerpts thereof is permitted only in combination with your own products. The application examples are not required to undergo the customary tests and quality inspections of a chargeable product; they may have functional and performance defects as well as errors. It is your responsibility to use them in such a manner that any malfunctions that may occur do not result in property damage or injury to persons. Disclaimer of liability Siemens shall not assume any liability, for any legal reason whatsoever, including, without limitation, liability for the usability, availability, completeness and freedom from defects of the application examples as well as for related information, configuration and performance data and any damage caused thereby. This shall not apply in cases of mandatory liability, for example under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for damages arising from a breach of material contractual obligations shall however be limited to the foreseeable damage typical of the type of agreement, unless liability arises from intent or gross negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens against existing or future claims of third parties in this connection except where Siemens is mandatorily liable. By using the application examples you acknowledge that Siemens cannot be held liable for any damage beyond the liability provisions described. Other information Siemens reserves the right to make changes to the application examples at any time without notice. In case of discrepancies between the suggestions in the application examples and other Siemens publications such as catalogs, the content of the other documentation shall have precedence. The Siemens terms of use ( shall also apply. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks. In order to protect plants, systems, machines and networks against cyber threats, it is necessary to implement and continuously maintain a holistic, state-of-the-art industrial security concept. Siemens products and solutions constitute one element of such a concept. Customers are responsible for preventing unauthorized access to their plants, systems, machines and networks. Such systems, machines and components should only be connected to an enterprise network or the Internet if and to the extent such a connection is necessary and only when appropriate security measures (e.g. firewalls and/or network segmentation) are in place. For additional information on industrial security measures that may be implemented, please visit Siemens products and solutions undergo continuous development to make them more secure. Siemens strongly recommends that product updates are applied as soon as they are available and that the latest product versions are used. Use of product versions that are no longer supported, and failure to apply the latest updates may increase customer s exposure to cyber threats. To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed at: Entry ID: , V1.0, 04/2018 2

3 Table of contents Table of contents Legal information Introduction Overview Design of the Components used Overview of library contents HMI Template Design Design of the Screens Design components... 9 Status bar Main Window Navigation Operating philosophy Feedback Style Button styles Text styles Input and output field styles Rectangular styles Commissioning Information on commissioning Using the basic library Operation Template screens for visualization Screen_ListView Screen_MachineModule Screen_TabView Screen_MachineOverview Pop-up_CallToAction Pop-up_Parameter Extending the library with a separate plant module Configuring plant screens Saving completed storage screens in the library More information and links Appendix Service and Support Links and Literature Change documentation Entry ID: , V1.0, 04/2018 3

4 1 Introduction 1 Introduction 1.1 Overview Plants and machines are becoming increasingly complex and therefore more and more difficult to operate. For this reason, designing an intuitive and graphically appealing user interface as a link between human and machine is becoming steadily more important. The allows you to easily create modern visualizations for your machine. Generate the visualizations with the optional SIMATIC Visualization Architect (SiVArc) and adapt the HMI screens to your requirements. Figure 1-1 Plant visualization example using the The layout and design are designed for smooth operation, transparency and expandability. This simplifies the operation of your machine and avoids operator error. 1.2 Design of the The is a modular concept consisting of a basic project with a basic library as well as optional supplementary libraries. It also allows for the integration of user-generated content. The basic project contains the cross-project layout and basic functions such as user login, diagnostic screens and additional settings screens. The basic project is required for including supplementary libraries. The supplementary libraries contain applicative visualization templates for plant sections as well as tools for commissioning and controlling individual functions and devices (e.g., robots). Entry ID: , V1.0, 04/2018 4

5 1 Introduction Figure 1-2 Concept: Design and expansion of the Basic Framework Advanced feature - Libraries Flow Packer Robotics Feature 3 Note The use of SiVArc is optional in this project. Using SiVArc to generate visualizations saves you configuration time as compared to manually creating the project. If you prefer not to use SiVArc, you will have to manually copy and interconnect all the required objects in your project. 1.3 Components used This application example was created using these hardware and software components: Table 1-1 Component Number Article number Note SIMATIC S PN CPU 1 6ES7515-2AM01-0AB0 S CPU Firmware V2.0 or higher SIMATIC HMI TP900 Comfort 1 6AV2124-0JC01-0AX0 The HMI project is intended for 7 and 9 inch displays. STEP 7 Professional V15 1 6ES WinCC Comfort V15 1 6AV2101-0AA05-0AA5 - SIMATIC Visualization Architect (SiVArc) V15 1 6AV2107-0PX05-0AH5 TIA Portal optional package This application example consists of the following components: Table 1-2 Component File name Note Library _LhmiTemplateSuite_V15.zip The library can be downloaded using the Entry ID Documentation _HMITemplateSuite_Doc_de.pdf This document Entry ID: , V1.0, 04/2018 5

6 1 Introduction 1.4 Overview of library contents The "hmitemplatesuitev15" library contains the following objects in "Master Copies": Table 1-3 hmitemplatesuite library structure Main folder Subfolder Content 01_PLC Template_Program Contains S7 program code. Only required for generating HMI operator panels with SiVArc. 02_HMI 00_Device Contains a completely configured operator panel (SIMATIC TP900 Comfort Panel). 01_Template 02_Application Contains HMI objects that are required for generating the template. You can find an exact list of the content in Table 1-4. Contains HMI objects for displaying a technical plant module, e.g. a packaging machine. A wildcard is included in this folder in the factory settings that can be used for storing data such as user-generated content. 03_Tools Contains HMI objects for generating tools, e.g. a file explorer. A wildcard is included in this folder in the factory settings. This folder can be used to store configured tools in order to distribute them together with the HMI Template Suite. Table 1-4 Contents of the "01_Template" subfolder Folder 00_Templates 01_Screens 02_PopUpScreens 03_Scripts 04_Tags 05_Rules 06_CopyManual 07_Examples Content Contains 5 HMI templates that are used for the Template Suite. Contains the default screens of the Template Suite for displaying messages, the diagnostics, and a settings page. Contains status bar pop-up screens as well as other control elements. Contains the required scripts for the templates. The template requires a total of 10 VBscripts. Contains the required HMI tags. Contains the SiVArc rules that you are to copy to your project in order to automatically generate HMI screens. Contains elements that may be copied manually to the TIA Portal project due to the fact that these objects are not generated by SiVArc. Contains sample visualizations (screens) that you can use as templates for your plant visualization. Entry ID: , V1.0, 04/2018 6

7 2 HMI Template Design 2 HMI Template Design This section contains an introduction and explanation of the design and concept of the "" project. The following section only covers the basic project. This basic project contains the layout, navigation as well as user management, reporting and diagnostic systems. When project upgrades become available, they can be downloaded from the entry page: The figure below shows the basic design of the template. Operation of the is explained in Section 4. Figure 2-1 Slide-in 2.1 Design of the Screens For the, names have been defined for the individual elements, which are listed in the following table along with their intended uses. The individual template elements are presented and described in detail in Section 2.2. Table 2-1 Element Position Uses 1. Title bar Displaying the title, opening the navigation slide-in 2. Status bar Displaying important information, e.g., current recipe, logged in user or status of the machine. The display can be adjusted according to the machine 3. Navigation slidein 1st level navigation Displaying the menus, switching between modules and displaying messages or settings Entry ID: , V1.0, 04/2018 7

8 2 HMI Template Design Element Position Uses 4. SubNavigation 2nd level navigation Navigation bar within a machine module at the bottom edge of the screen. 5. ThirdNavigation 3rd level navigation Structuring functions in more detail Note Fourth level navigation is possible via tab distribution on the corresponding HMI screen, see Section Entry ID: , V1.0, 04/2018 8

9 2 HMI Template Design 2.2 Design components Title bar Figure 2-2 Status bar The top bar is the "Title bar". This corresponds to the header in a document and shows plant operators where they are currently located in the project. The navigation slide-in can be activated using the menu button on the right-hand side. An accent color is used for the "Title bar". Figure 2-3 The "Status bar" is found directly beneath the "Title bar". The status bar has a variable design and displays information such as the status of the plant section, the recipe currently being processed and the user. Depending on the module, various elements are displayed in the Status bar. The diagnostics icon is displayed on the right-hand side if there is an error status. A shade of dark gray is used for the Status bar. This helps distinguish it from the "Title bar" above and the main window below Main Window This area is reserved for operating the corresponding plant module. This centrally positioned section covers an area of about 70%. The central position is intended to draw the main focus of the operator. The content of the main displays may contain additional tabs or controls for navigating within the screen. Entry ID: , V1.0, 04/2018 9

10 2 HMI Template Design Navigation The following section describes the concept for navigating through the template via the individual HMI screens. The contains a total of four levels of navigation. First level navigation (Navigation-Slide) Figure 2-4 Slide-in: Navigation-Slide First level navigation is triggered using a slide-in on the right-hand side. The slide-in gives you access to the global HMI screens. You can use it to switch between the configured application, the global message page and the diagnostics page. In the "Settings", you can edit aspects such as the display language or the brightness of the operator panel. Second level navigation (SubNavigation) (optional) Second level navigation is the main navigation of a module. It is located at the bottom of the screen and is permanently visible. Figure 2-5 Note The navigation bar can also be designed using icons. As graphics can be understood by everyone, this offers the advantage of not having to translate texts. You can switch between the individual HMI screens of a plant module using the navigation bar. Entry ID: , V1.0, 04/

11 2 HMI Template Design The absolute sizes depend on the resolution of the operator panel. Pressed navigation buttons are displayed with a light background. The selected accent color is used for the font. This ensures that operators can immediately identify their current location. The appearance of unpressed navigation buttons varies only slightly from the navigation bar. This ensures that attention is drawn to the pressed button. Third Level Navigation (optional) Third level navigation can be used within a module to give a more detailed structure to the module functionalities. Figure 2-6 Empty navigation bar The navigation bar is designed for icons, as text-based navigation takes up too much space on smaller operator panels, and does not allow enough room for plant configuration. Configuration: This navigation is included in the example template screens in the library. The example screens are presented in Section 4.1. Drag one of the screens into your project and add appropriate icons to the navigation. A click event can be used to perform a suitable screen switch. Entry ID: , V1.0, 04/

12 2 HMI Template Design Fourth level navigation (In-Screen Tab-Navigation) (optional) On an HMI screen you also have the option of displaying the following tab switch values in a coherent and organized structure. Operators are familiar with tab views as they appear in a number of everyday applications, which makes them intuitive to use. This navigation describes the lowest level of navigation, as it is only accessible within an HMI screen. Figure 2-7 Tab-Navigation In the figure, the active tab (Tab 1) is displayed in a lighter color. The display of the values belonging to Tab 1 is triggered using "visibility" animation. Note This level of navigation is optional. This kind of navigation is used if related information can no longer be displayed on one HMI screen. Configuration: The "InScreen Tab-Navigation" is stored in the library as a template screen. You can use the "Screen_TabView" HMI screen as a template for your configuration in order to save development time. In Section 4.1, all stored template screens are briefly described. 2.3 Operating philosophy There is a philosophy behind every operating concept. This philosophy covers points such as the following: How is the operator notified of the current status of the machine? How is the operator notified of when or where an operator action is necessary? How is the operator notified of the implications of an operator action? Humans are not able to register as much information as they would like to at one time. For this reason it is necessary to present accumulating information in such a way as to allow the operator to register all the information quickly and intuitively. An easy-to-follow user interface plays a major role in this regard. Entry ID: , V1.0, 04/

13 2 HMI Template Design Retrieving information In order to simplify plant operations for the operator, it is necessary to prepare, structure and present information in a clear way. In this project, some information was displayed as follows. - Messages, alarms and diagnostics Alarms are marked by a message indicator in the operator panel and a red indicator in the status bar. Figure Plant information, e.g. process values Important information for the operator is displayed in the corresponding module on the overview page, allowing the operator immediate access to all necessary information available for the plant module. - General information, e.g. current operators, recipe, time The current operators, the recipe currently being processed and other general information can be displayed in the status bar. Feedback Feedback from the HMI system is important. It helps increase the operator s effectiveness and efficiency as well as eliminate operating errors and uncertainties. Mechanical pushbuttons and emergency stop pushbuttons have a mechanical feedback that the operator experiences as soon as the button is pressed. Panel operating units are missing this haptic feedback. For this reason, the haptic feedback must be replaced by visual or audible feedback. The aim of the feedback is to make sure the operator knows what operating steps the HMI system has taken at all times. Operation of the plant module Operation of the plant module only takes place in the main window. Figure 2-9 Main operating window for plant functions Entry ID: , V1.0, 04/

14 2 HMI Template Design This can essentially be separated into the following operator actions: Operations that have an effect on the machine (e.g., controlling a drive) In this case, increased operator attention is required as an operator action could have an undesirable effect on the machine. For this reason, these operating objects are color-coded. Operations that have no direct effect on the machine, but that change properties in the operator panel. These operations can be reversed without causing any lasting impact on the machine. Only neutral colors may be used for these operating objects. In this case, a shade of gray has been selected. 2.4 Style The entire project uses flat design. Flat design emphasizes a minimalist style and refrains from using three-dimensional effects (shadows or textures). This facilitates configuration and provides clarity for operators, as the focus remains on the content rather than the design. Color concept For optimal usability and ergonomics, a simple color concept was chosen for this project. Table 2-2 Main colors used Color RGB color Application example Accent color, blue 0; 95; 135 Title bar Light 218; 220; 224 Main window, background Dark gray 39; 51; 56 Status bar, background Gray 64; 77; 83 Status bar, buttons Light gray 196;199;204 Option panel, background The accent color is used to highlight objects such as the title bar or buttons/tabs (when they are active). Shades of gray are used to contrast the navigation bars and the status bar from the content of the main screen. A light color was chosen for the background. By placing the operator panel in the center and starkly contrasting the other objects at the edge of the screen, the actual contents stand out and help facilitate the operation of the configured functions. Entry ID: , V1.0, 04/

15 2 HMI Template Design HMI styles Using the HMI styles ensures a uniform design for the TIA Portal project. The properties and appearance of the objects are defined in the HMI style. The "style template" can be found here: "Project navigation > Common data > Styles >"01_Template\04_Style\styleTemplate V1.x" You can edit the HMI style to specify new objects or change the existing design for the entire project. Figure 2-10 HMI style preview The individual styles are each intended for a specific use. The locations of use are described in the following tables. The styles used for this application example are described in this subsection. Entry ID: , V1.0, 04/

16 2 HMI Template Design Button styles For the, a minimum button size of 40x40 px has been defined. This ensures that all buttons can be operated easily and without error. Using the following HMI styles ensures the uniform appearance of the buttons. Table 2-3 Overview of the buttons used in the project Style name Appearance Uses/Location of use ButtonDefault Standard button for normal operator actions such as triggering a function or opening a pop-up screen Cancel_Abort_C lose Delete Execute_Action Statusbar Button for canceling actions or closing pop-up windows. ->Action has no affect on the machine Button for actions performing a delete activity. ->Action has a critical effect on the machine Button for actions that have an effect on the machine, such as executing scripts or setting machine parameters. Button for opening a pop-up window for the status bar, e.g. a log-on dialog or a recipe view. SubNavigation_I nactive SubNavigation_I nactive Button for opening a pop-up-screen for controlling the plant module. -> additional content via pop-ups Navigation button for the "SubNavigation" bar. Display of inactive status (unpressed). Navigation button for the "SubNavigation" bar. Display of active status (pressed). btn_prevscreen When this button is pressed, you jump to the previous screen. Using styles ensures that the same element design is used consistently for each operator action Text styles An HMI style is defined for each application in order to ensure a consistent and clean typeface for the operator panels. This not only ensures consistency, but also makes the HMI more intuitive and faster to configure. The default font size in this project is 14pt. Headers and titles are displayed in 18pt. Bold font is used for highlighting important content as well as for headers. Entry ID: , V1.0, 04/

17 2 HMI Template Design Table 2-4 HMI text styles used in the template Style name Appearance Uses/Location of use Standard style Regular (center) Regular (right) PopUp_SubHeadline PopUp_SubHeadline center lightheadline Headline Standard object, free use Standard object, free use Standard object, free use Header. Only used in pop-up screens Header. Only used in pop-up screens Light header, free use Dark header, free use Headline (Center) SubNavigation The middle header, free use Text for the navigation bar StatusBar_Display Font for the status bar display. StatusBar_Title StatusBar_Text TitleBar navigation OptionPanel_Title Faceplate_Title Faceplate_Text State Header for the status bar Text, only for the status bar Font, only for the title bar Font, only for navigation purposes Header for the option panel Header. Only used in HMI faceplates. Text content. Only used in HMI faceplates. Machine status display Input and output field styles Table 2-5 IO field styles used in the template Style name Appearance Uses/Location of use Standard style Standard object, free use Regular (center) Regular (right) Regular_Out (left) Standard object, free use Standard object, free use Only used for the output of values Entry ID: , V1.0, 04/

18 2 HMI Template Design Style name Appearance Uses/Location of use Regular_Out (right) PopUp_InOut PopUp_InOut_Right StatusBar_PopUp StatusBar Faceplate_Output Only used for the output of values Output and input field in pop-up screens Output and input field in pop-up screens Only used for the status bar in a pop-up screen. Only used for the status bar. Only used in HMI faceplates Rectangular styles For the rectangular styles, coordinated colors for backgrounds are defined to create a coherent overall picture. Table 2-6 Style name Appearance Uses/Location of use Standard Standard color, for free use PopUp_Background Background for pop-up screens TitleBar_Background Accent color for the title bar StatusBar_Background Color for the status bar SubNavigation_Background ScreenTab_Background InScreenNav_Background Background color for the navigation bar Background color for the "Screen tab" display Background color for the navigation elements on an HMI screen ThirdLevelNavigation_Inactive Faceplate_Background Background color for third level navigation Background color for faceplates Faceplate_State Background color for status display StateColor_Green Color for status: OK Entry ID: , V1.0, 04/

19 2 HMI Template Design Style name Appearance Uses/Location of use StateColor_Yellow Color for status: Warning level 1 StateColor_Orange Color for status: Warning level 2 StateColor_Red StateColor_Blue Color for status: Alarm Color for status: Action required The following styles are also relevant: Table 2-7 Special object styles Switch Circle Object name Appearance Uses/Location of use Switch for free use, e.g. switching a motor on Display of status Faceplate_Circle_State Settings Display of status in a faceplate Setting the brightness of the operator panel. 8-point design pattern The 8-point design pattern only uses multiples of the number 8 (pixels) for object sizes and the distances between objects. For example: 8, 16, 24, 32, etc. If the sizes and positions of the objects are all based on the number 8, a square may be, for example, 40x40 px. If it is enlarged by one step, then it would be 48x48 px. Using the 8-point design pattern offers the following advantages Easier to make decisions on sizes and distances of objects (saving time). A more consistent graphic interface Beneficial when scaling to other resolutions This type of HMI configuration has been implemented in this project. Entry ID: , V1.0, 04/

20 3 Commissioning 3 Commissioning You do not require a SiVArc option package in order to open the basic project. The quickest way to add the extra content is to use SiVArc rules, otherwise you have to manually drag and drop all the objects into your project and, if necessary, interconnect them manually. Using SiVArc saves you configuration time and reduces the probability of configuration errors. Note For quick commissioning or for testing the application example, watch the video on the entry page of this application example. 3.1 Information on commissioning Please observe the following notes before starting with commissioning, otherwise errors in the configuration may occur. You can use SiVArc to integrate the into existing projects. In this case, note the second installation variant with SiVArc. Alternatively, you can create a new TIA Portal project. In this case, use the first installation variant and drag the preconfigured operator panel into the newly created project. Languages Activate "German (Germany)" and "English (USA)" as project and runtime languages for the operator panel. Figure 3-1 Project navigation: Changing project languages Figure 3-2 HMI runtime settings: Changing runtime language Entry ID: , V1.0, 04/

21 3 Commissioning Requirements for installation variants 2 and 3 Note The installation variants 1-3 are explained in Section 3.2. The following steps are used to create settings that prevent translation errors and display errors. In the "Runtime settings" of your HMI operator panel under "General> Style of the HMI device", set the StyleTemplate V1.x style. Deactivate the check box for "Default style of the project" Full name: "01_Template\04_Style\styleTemplate V1.x". Figure 3-3 Deactivating HMI permanent areas Make sure that you have not set a permanent area for your HMI screens. A permanent area would distort the display. To deactivate the permanent area, you can set the height to "0" in the project navigation under "Screen Management > Permanent area > Properties". Figure 3-4 Figure 3-5 Entry ID: , V1.0, 04/

22 3 Commissioning Adding a project font (optional) Note This section is optional. You can choose whether to use the "Siemens Sans" font or your own font for the project. The HMI Template uses the "Siemens Sans" font for the visualization. If you want to apply this font for the project, proceed as follows: If you have inserted the HMI template into your existing operator panel, configure the "Siemens Sans" font in the Runtime settings of the operator panel as "configured font". 1. Open the Runtime settings in your operator panel. 2. Go to the settings for "Language & font" 3. For all configured languages, enter the "Siemens Sans" font in the "Configured font" column. Figure 3-6 Entry ID: , V1.0, 04/

23 3 Commissioning 3.2 Using the basic library The basic project is packaged as a library, allowing you to easily integrate it into any project of your choice. 1. Download the library from the entry page " _HMITemplateSuiteV15.zip" 2. Unzip the library named " _HMITemplateSuiteV15.zip". 3. Open a project in the TIA Portal. Open the unzipped library from the TIA Portal. Figure 3-7 Contents of the "hmitemplatesuite library 4. Copy the folders "01_PLC" and "02_HMI" from the "Master Copies" folder in the "LhmiTemplateSuite" library into the folder of the same name in your project library. Figure 3-8 View of the project library after copying Entry ID: , V1.0, 04/

24 3 Commissioning You have the following three options for running the project: Installation variant 1: Running the library with a new HMI device Use this variant if you have not yet configured an HMI device. The template uses a SIMATIC TP 900 Comfort Panel for the visualization. The device can be exchanged via the TIA Portal function "Change device". 1. Copy the S7 program named "Template Program", "Project library> Master Copies> 01_PLC> Template Program" into your configured controller. 2. Open the folder "02_Hmi > 00_Device" in the project library. Drag the "HMI" device into your project and interconnect the HMI device with your controller. Figure 3-9 View of the object to be copied 3. Compile and load the HMI device or start the simulation. Installation variant 2 Integrating the library into an existing project - with SiVArc Note Observe the installation instructions in Section Copy the S7 program named "Template Program", "Project library> Master Copies> 01_PLC> Template Program" into your configured controller. 5. Copy the folder 00_Templates "Project library > Master Copies > 02_HMI > 01_Template > 00_Templates" into the templates of your existing HMI device. "HMI > Screen management > Templates" 6. From the folder 05_Rules "Project library > Master Copies > 02_HMI > 01_Template > 00_Templates copy the SiVArc rules into the corresponding open SiVArc editor. "Common Data > SiVArc > Screen rules / Tag rules" Entry ID: , V1.0, 04/

25 3 Commissioning Figure 3-10 Note: To copy the rules into the project, you must first double-click to open the rule editors. 7. From the file "06_CopyManual" in the project library, copy the "User Name task "Project library > Master Copies > 02_HMI > 01_Template > 06_CopyManual > User Name" into "Scheduled tasks" in the HMI device. Figure 3-11 View of the object to be copied 8. Open the "Slide-in right" section of your HMI device "Project navigation> Screen management> Slide-in screens" 9. Activate the slide-in and set the width to 220 px under "Layout". Entry ID: , V1.0, 04/

26 3 Commissioning Figure 3-12 Activating the slide-in screen Figure 3-13 Setting the slide-in screen to size 220 px 10. From the folder "06_CopyManual", copy the "Slide-in right" group into the open slide-in editor. 11. Right-click on the slide-in and select "Group > Ungroup" in the menu. Figure Compile your controller. 13. Start the SiVArc generator and select your controller. Figure 3-15 SiVArc generator in the status bar of the TIA Portal Entry ID: , V1.0, 04/

27 3 Commissioning 14. Define the screen "10_Startscreen" as the start screen. "HMI > 02_HMI > 02_Application > Application Name > 01_Screens > 10_Startscreen" 15. Compile and load the HMI device or start the simulation. Entry ID: , V1.0, 04/

28 3 Commissioning Installation variant 3: Integrating the library into an existing project - without SiVArc Note This installation variant requires a configured HMI device. 1. If you are not using SiVArc, copy the objects listed in the following folders to the correct place in your project. From the folder "Project library > Master Copies > 02_HMI > 01_Template": 00_Templates 01_Screens 02_Pop-up-Screens 03_Scripts 04_Tags Also, from the folder "Project library > Master Copies >02_HMI > 02_Application > ApplicationName, copy the "Folder 01_Screens" into the HMI screen of the HMI device. Figure 3-16 Copy objects; left: Project navigation, right: Library 2. From the folder "06_CopyManual", copy the "User Name" task in the Scheduled Tasks in the HMI device. 3. From the folder "06_CopyManual", copy the group "Slide-in right" in the slide-in area of the HMI device. Entry ID: , V1.0, 04/

29 3 Commissioning 4. Define the screen "10_Startscreen" as the start screen. "HMI > 02_HMI > 02_Application > Application Name > 01_Screens > 10_Startscreen" Figure Compile and load the HMI device. Entry ID: , V1.0, 04/

30 4 Operation 4 Operation This section shows how to operate the HMI template using a sample application. This is intended to demonstrate the options for this operating concept. In this application example, the operating concept is provided without a specific plant. The example application shown here is an illustration of the design and operation options and shows you what the visualization of your machine could look like. Opening the application 1. Click the button at the top right. 2. Click the "Application" button. Figure 4-1 Slide-in Overview page The application starts with an overview page that includes the most important information for the individual modules "Foil Feed", "Tapped Chain" and "Cross Sealer". The SubNavigation bar can be used to navigate within these individual modules. Figure 4-2 Example application for the HMI screen "Screen_MachineOverview" Entry ID: , V1.0, 04/

31 4 Operation In the module page "Tappet Chain", the control area of the module is located in the right. There is room for a module screen in the left. For security reasons, you cannot directly change the machine parameters at this level. Click on the "..." buttons to open pop-up screens. These pop-up screens can then be used to make adjustments or change machine parameters. Note The "[...]" button is commonly used to show that there is more content for a particular point. This content is displayed in an additional pop-up screen when the [...] button is pressed. Figure 4-3 Example application for the HMI screen "Screen_MachineModule" Opening the control - pop-up screens Click on the [...] button to open the corresponding control panel. Figure 4-4 Example application for the HMI screen "Pop-up_Parameter" Here you can adjust the values accordingly. The values are accepted without confirmation. The "Close" button closes the pop-up screens. Entry ID: , V1.0, 04/

32 4 Operation Note Using pop-up screens to change machine parameters help prevent operator errors caused by accidentally touching the screen. Option panel You can activate the option panel using the following button on the right side of the screen. The option panel gives you access to general functions. Figure 4-5 Activating the option panel Figure 4-6 View of option panel Entry ID: , V1.0, 04/

33 4 Operation The advantage of the option panel is that it can display functions that are important throughout the entire module. This could include a manual mode for a robot, or application-specific functions (robot calibration, driving to a particular point, etc.). Functions accessed using the option panel do not result in permanent parameter changes to the machine. Configuration The option panel is triggered using a pop-up screen ("Template_ManFunctions"). You can customize the option panel for your application in this pop-up screen. Access to the option panel is integrated onto the example template screens, see Section Template screens for visualization The "LhmiTemplateSuite" library contains a folder with example templates. You can use these templates for creating plant module visualizations. This section presents and briefly describes the template screens. The folder can be accessed using the following path in the library: "Masters copies >02_HMI > 01_Template > 07_Examples" Figure 4-7 Entry ID: , V1.0, 04/

34 4 Operation Screen_ListView Figure 4-8 Use Template for displaying list elements Screen_MachineModule Figure 4-9 Use Overview screen of a plant module Template for displaying the most important parameters/statuses of a plant module Entry ID: , V1.0, 04/

35 4 Operation Screen_TabView Figure 4-10 Use Easy-to-follow display of parameters or statuses within a section of a plant with intuitive tab switching Tab switching serves as an additional level of navigation directly on an HMI screen Screen_MachineOverview Figure 4-11 Use Overview of individual plant modules. Template for displaying the most important parameters of each module. Entry ID: , V1.0, 04/

36 4 Operation Pop-up_CallToAction Figure 4-12 Use This pop-up is used to execute operator actions or functions. Example: Save dialog Log on dialog Pop-up_Parameter Figure 4-13 Use This pop-up screen is used to activate machine parameters or to change values. Entry ID: , V1.0, 04/

37 5 Extending the library with a separate plant module 5 Extending the library with a separate plant module You can configure your plant module based on the template. 5.1 Configuring plant screens For improved clarity in the TIA Portal project, configure the HMI screens in the "02_Application" folder. Figure 5-1 The HMI screen "10_Startscreen" is the start screen for your application. This screen is interconnected with the "Application" button in the slide-in menu: Figure 5-2 Note Use the template screens in the library to construct your user interface. The example screens are displayed in Section 4.1. Figure 5-3 Entry ID: , V1.0, 04/

38 5 Extending the library with a separate plant module Storage path in the library "Masters Copies >02_HMI > 01_Template > 07_Examples" Note Use the "HMI templates" to quickly assign the design options to a new HMI screen. Figure 5-4 The "TemplateSubNav" template is designed for creating HMI screens for plant modules. In this "HMI template", the lower navigation bar "SubNavigation" is used for navigating the plant module to be configured. 5.2 Saving completed storage screens in the library Once you have configured your plant module, you can save the HMI objects in the existing library. The advantage of saving completed visualizations in libraries is that you can reuse certain parts of this visualization for other projects, saving development time in the future. An empty folder structure has already been created in the library for this purpose: Figure 5-5 Copy the individual elements of your plant module into the folder structure "Application Name". In the library, the individual HMI elements are stored separately in the subfolders for greater clarity. SiVArc rules should be filed in the folder "05_Rules" if SiVArc is used. Entry ID: , V1.0, 04/

39 6 More information and links 6 More information and links HMI Toolbox This application example contains a few useful tools that you can easily integrate into your HMI configuration via the libraries, such as a stopwatch, file explorer or calculator. Figure 6-1 Link to application example "Toolbox for HMI projects": SiVArc SiVArc automatically generates your HMI visualization. With the help of rules, you can define the allocation between the control program and the visualization elements. SiVArc analyzes the control program and generates the visualization automatically. The use of SiVArc saves you configuration time and prevents errors, especially for recurring tasks. In addition, it also facilitates the implementation of corporate standards. Figure 6-2 Link to application example "SiVArc-Getting Started": Entry ID: , V1.0, 04/

40 7 Appendix 7 Appendix 7.1 Service and Support Industry Online Support Do you have any questions or need assistance? Siemens Industry Online Support offers round the clock access to our entire service and support know-how and portfolio. The Industry Online Support is the central address for information about our products, solutions and services. Product information, manuals, downloads, FAQs, application examples and videos all information is accessible with just a few mouse clicks: Technical Support The Technical Support of Siemens Industry provides you fast and competent support regarding all technical queries with numerous tailor-made offers ranging from basic support to individual support contracts. Please send queries to Technical Support via Web form: SITRAIN Training for Industry We support you with our globally available training courses for industry with practical experience, innovative learning methods and a concept that s tailored to the customer s specific needs. For more information on our offered trainings and courses, as well as their locations and dates, refer to our web page: Service offer Our range of services includes the following: Plant data services Spare parts services Repair services On-site and maintenance services Retrofitting and modernization services Service programs and contracts You can find detailed information on our range of services in the service catalog web page: Industry Online Support app You will receive optimum support wherever you are with the "Siemens Industry Online Support" app. The app is available for Apple ios, Android and Windows Phone: Entry ID: , V1.0, 04/

41 7 Appendix 7.2 Links and Literature Table 7-1 No. \1\ Siemens Industry Online Support Topic \2\ Link to the entry page for the application example \3\ Introduction to SiVArc: SIMATIC Visualization Architect (SiVArc) - Getting Started \4\ Link to application example "Toolbox for HMI projects": Change documentation Table 7-2 Version Date Change V1.0 04/2018 First edition Entry ID: , V1.0, 04/