SIMATIC Visualization Architect (SiVArc) Getting Started

Transcription

1 Application Example 11/2016 SIMATIC Visualization Architect () Getting Started TIA Portal V14

2 Warranty and Liability Warranty and Liability Note The Application Examples are not binding and do not claim to be complete regarding the circuits shown, equipping and any eventuality. The Application Examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for ensuring that the described products are correctly used. These Application Examples do not relieve you of the responsibility of safely and professionally using, installing, operating and servicing equipment. When using these Application Examples, you recognize that we cannot be made liable for any damage/claims beyond the liability clause described. We reserve the right to make changes to these Application Examples at any time without prior notice. If there are any deviations between the recommendations provided in this Application Example and other Siemens publications e.g. Catalogs the contents of the other documents have priority. We do not accept any liability for the information contained in this document. Any claims against us based on whatever legal reason resulting from the use of the examples, information, programs, engineering and performance data etc., described in this Application Example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act ( Produkthaftungsgesetz ), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract ( wesentliche Vertragspflichten ). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health. The above provisions do not imply a change of the burden of proof to your detriment. It is not permissible to transfer or copy these Application Examples or excerpts of them without first having prior authorization from Siemens AG in writing. Security information Siemens provides products and solutions with industrial security functions that support the secure operation of plants, systems, machines and networks. 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. Products and solutions from Siemens are only one part of such a concept. The customer is responsible for preventing unauthorized access to the customer s plants, systems, machines and networks. Systems, machines and components should be connected to the company network or the Internet only if and to the extent necessary and if appropriate protective action (e.g., use of firewalls and network segmentation) was taken. In addition, Siemens recommendations regarding appropriate protective action should be followed. For more information about industrial security, visit Siemens products and solutions undergo continuous development to make them even more secure. Siemens strongly recommends to perform updates as they become available and use only the latest product versions. Using versions that are out of date or no longer supported can increase the risk of cyber threats. To stay informed about product updates as they occur, subscribe to the Siemens Industrial Security RSS feed at Entry ID: , V1.1, 11/2016 2

3 Table of Contents Table of Contents Warranty and Liability Task Solution Overview Hardware and software components Basics Supported objects Basics of rules Configuration Example Description Configuration Configuration Example Description Configuration Expanding faceplates Creating the layout Creating screen rules Creating tag rules Creating copy rules Generating the visualization Additional Notes Links & Literature History Entry ID: , V1.1, 11/2016 3

4 1 Task 1 Task Introduction TIA Portal V14 or higher provides the (SIMATIC Visualization Architect) option package. Using the control program, automatically generates your visualization. To this end, you set rules that define the assignment between visualization elements (e.g., faceplates) and control blocks. This simplifies recurring tasks, avoids errors and allows you to implement company standards more easily. Figure 1-1 Example: Screen rules Entry ID: , V1.1, 11/2016 4

5 2 Solution 2.1 Overview 2 Solution 2.1 Overview The use of is scalable. You can use the option for both simple and complex tasks. For example, to automatically generate HMI tags from the controller or visualize an entire plant area. Aside from basics, this application example also includes two configuration examples. In these configuration examples, you will learn about the different functions in order to use them for your own projects. In the first configuration example, you will get to know the basic principle of operation of. The second configuration example uses the Digital sample block to show you more functions. 2.2 Hardware and software components Hardware components supports the following devices: Controllers SIMATIC S SIMATIC S SIMATIC S Software Controller ET200SP CPU Operator panels 2 nd -generation Basic Panels Comfort Panels 2 nd -generation Mobile Panels WinCC Runtime Advanced WinCC Runtime Professional Software components To install, you require at least STEP 7 Professional and WinCC Comfort. Sample files and projects The following list contains all files and projects that are used in this example. Table 2-1 Component Note GettingStarted_en.pdf _ExampleProjectStart.zip _DigitalStart.zip This document TIA Portal V14 project for Configuration Example 1 TIA Portal V14 project for Configuration Example 2 Entry ID: , V1.1, 11/2016 5

6 3 Basics 3.1 Supported objects 3 Basics 3.1 Supported objects Control program HMI objects supports functions (FC) and function blocks (FB) in LAD, FBD, STL and SCL and global and instance data blocks (DB). It supports all elementary data types that the operator panel can display and the Array, Struct and UDT data types. If the selected operator panel supports the respective objects, you can create the following HMI objects by rules. Depending on the control program: External tags Screens and pop-up screens Screen objects As master copies in the library: Bar, Screen Window, IO Field, Graphic IO Field, GRAPH Overview, PLC Code View, ProDiag Overview, Round Button, Switch, Button, Slider, Symbolic IO Field, Text Field, Gauge As types in the library: Faceplates, screens as screen windows Text lists Without control program: Screens Internal tags Scripts (C and VB programming language) Text lists Entry ID: , V1.1, 11/2016 6

7 3 Basics 3.2 Basics of rules 3.2 Basics of rules Editors The editors can be found in TIA Portal in the project tree, Common data >. Figure 3-1 editors The following editors are available to you: Table 3-1 Editor Screen rules Tag rules Text list rules Copy rules Generation matrix Generation overview Settings Description The screen rules allow you to define which control objects are created in your HMI device depending on the control program. You can create tag rules to store the external tags generated by in the operator panel in a structured manner. You can create text list rules to create text lists in the operator panels. You can create copy rules to copy HMI objects without a PLC connection from the library to the HMI operator panel. The Generation matrix displays the screens and screen objects of a selected operator panel that were generated by. In addition, you can change the assignment of the generated objects. The Generation overview displays the screens, screen objects, tags and text lists of all operator panels in the project that were generated by. In this editor, you can define general settings such as the default setting for tag acquisition. Entry ID: , V1.1, 11/2016 7

8 4 Configuration Example Description 4 Configuration Example Description In the first configuration example, you add rules to an existing project so that automatically generates the visualization for an existing control program. The ExampleProjectStart.zip sample project that you can download from the download page of this entry includes the SpeedAxisControl FB. This FB is used to control a virtual speed axis. In the control program, three virtual axes are configured as examples. An fpspeedaxis faceplate is prepared for the visualization. This is the faceplate you use to operate the axis. The project does not yet include elements and the visualization. You create them yourself in the next chapter, 4.2. A PLC UDT is used for data transfer between the controller and the HMI. This UDT is used at both the interface of the SpeedAxis function block and the interface of the fpspeedaxis faceplate. For more information on how to create faceplates and UDTs, please refer to this entry: Creating Faceplates with WinCC Runtime Advanced and Comfort Panels \3\ Figure 4-1 Communication structure Main Speed Speed Axis Speed Axis Axis UDT UDT fpspeedaxis Entry ID: , V1.1, 11/2016 8

9 4 Configuration Example Configuration 4.2 Configuration Table Download the ExampleProjectStart.zip sample project you will find on the download page of this entry and unzip the *zip file. Use TIA Portal V14 to open the project. The controller already contains all the necessary elements. The project library additionally includes the typespeedaxis UDT and the fpspeedaxis HMI faceplate. Note: If you want to simulate the SIMATIC S7-Software Controller with SIMATIC S7-PLCSIM Advanced follow the steps below: 1. Activate the check box Support simulation during block compilation in the project properties ( project properties > Protection ). 2. Delete the program blocks MC-Interpolator [OB92] and MC-Servo [OB91]. 3. Recompile the PLC program. The motion control blocks will build new. 2. Right-click the fpspeedaxis faceplate and select Edit type. Entry ID: , V1.1, 11/2016 9

10 4 Configuration Example Configuration 3. In the Inspector window, open the Plug-ins tab. 4. To open the expressions editor, select Property interface > Properties_Faceplate > typespeedaxis and in the Printout of tags column, click the... button. In this editor, enter the expressions in a VBScript-based script language. The editor supports you by autocomplete and syntax highlighting. During generation, the expressions entered are evaluated by and replaced by contents. 5. The tags of the UDT type are in the HMIData data block of the controller and named following the pattern <typespeedaxisx> where X is replaced by a serial number. This number corresponds to the number of the instance data block of the SpeedAxisControl FB at the respective point of use. Entry ID: , V1.1, 11/

11 4 Configuration Example Configuration 6. Enter the following expression in the editor: "HMIData" & TagNaming.SeparatorChar & "TypeSpeedAxis" & TrailNum(Block.DB.SymbolicName) The expressions in quotation marks, HMIData and typespeedaxis, are interpreted as text and applied without any changes. The TagNaming.SeparatorChar expression outputs the separator for PLC tags defined in the Runtime settings. The TrailNum() expression outputs the last positive number from a string. The Block.DB.SymbolicName expression reads the symbolic name of the instance data block. The & operator is used to connect the individual strings. For a detailed description of the individual expressions, please refer to the TIA Portal Help, Chapter SIMATIC Visualization Architect > References. 7. In the Printout of the static value column, open the editor at the Miscellaneous > Name property. Enter the following expression: "fpspeedaxisinst" & TrailNum (Block.DB.SymbolicName) When generating elements using, you have to assign a unique name. This prevents from generating multiple elements of the same name. If the name is not unique, SIVArc generates only one element and outputs a warning. 8. Release the changes to the faceplate. 9. Insert an HMI operator panel (Comfort Panel, 2 nd -generation Mobile Panel or WinCC Runtime Advanced) into the project. At this point, the restriction of the operator panel is related to the faceplate. Basically, you can use for all operator panels listed in Open a blank screen. Entry ID: , V1.1, 11/

12 4 Configuration Example Configuration 11. In the Inspector window, open the Plug-ins tab. In the Name field of the Printout of the static value column, enter a unique name. For example: "Speed Axis" & TrailNum(Block.DB.SymbolicName) 12. Use drag and drop to move this screen to the Master copies folder of your project library and delete it in your operator panel. 13. Select Common data > > Screen rules to open the Screen rules editor. 14. Create a new rule, SpeedAxis. 15. As the program block, select the SpeedAxisControl FB of the controller. This ensures that the rule is run once each time the SpeedAxisControl block is called. Entry ID: , V1.1, 11/

13 4 Configuration Example Configuration 16. As the screen object, select the fpspeedaxis faceplate. As the screen, select the created screen from the Master copies folder of the library. The fpspeedaxis screen object is integrated into the Screen_1 screen template when the rule is run and inserted into your project as a new screen. generates the names and tag connection based on the previously defined expressions. 17. Open the Devices & networks editor and create an HMI connection between the controller and the operator panel. 18. Compile the controller. 19. Right-click the operator panel and select Generate the visualization (). 20. Click Generate. If the project contains multiple controllers, you can choose for which controller the visualization will be generated. In addition, you can set whether all control tags or only the used ones (default setting) will be created in the operator panel. Entry ID: , V1.1, 11/

14 4 Configuration Example Configuration 21. generates three screens and one instance of the fpspeedaxis faceplate is inserted into each screen. This faceplate is automatically linked to the appropriate UDT in the HMIData data block. 22. If you now make changes in the control program, e.g. add an axis, regenerate the visualization (see step 19). You do not have to make any further changes to your visualization. Entry ID: , V1.1, 11/

15 5 Configuration Example Description 5 Configuration Example Description The second example uses the Digital sample block to show more functions. As the source project for this example, you can use the DigitalStart project that you can download from the download page of this entry. The principle of operation of the sample block is not part of the scope of this application example. For more information, please refer to this entry: Example Blocks for WinCC (TIA Portal) and STEP 7 (TIA Portal) for S and S with SCL \4\. In this entry, you can also download libraries with other sample blocks configured for, including the required rules. These libraries allow you to directly generate the visualization for the blocks without any configuration overhead on your part. As in Configuration Example 1, a PLC UDT is used for communication. The editors, expressions, etc. described in Chapter 4 are assumed as a given in the following configuration steps and not explained in greater detail. 5.2 Configuration Expanding faceplates First prepare the faceplates for generation using. To this end, link the faceplate to the appropriate UDT in the HmiData DB. As only one faceplate is used per screen (exception: the Digital_Icon faceplate), you can skip setting the names (step 5 of Table 5-1). Table Open the DigitalStart project that you can download from the download page of this entry In the Libraries task card, open the Project library > Types > DIGITAL folder. 3. Right-click the Digital_1_Overview faceplate and select Edit type. Entry ID: , V1.1, 11/

16 5 Configuration Example Configuration 4. In the Inspector window, open the Plug-ins tab. 5. In Miscellaneous > Name of the Printout of the static value column, click the... button. Enter the following expression: "fpoverview"& Right(Block.DB.SymbolicName, 9) The Right(string, no) expression outputs a certain number (no) of characters, starting from the right side of a string. For example: (Right(instDigital01, 9) -> Digital01) 6. In Property interface > Process > Value of the Printout of tags column, click the... button. Enter the following expression: "HmiData" & TagNaming.SeparatorChar & Right(Block.DB.SymbolicName, 9) 7. In Property interface > Property > Visibility of the Printout of tags column, click the... button. Enter the tag name Visibility. To make the individual tabs visible, the same tag is used for all faceplates in this example. Therefore, it can be specified directly. 8. Release the faceplate version. 9. Perform steps 3 through 8 also for the Digital_2_Messages and Digital_3_Service faceplates. Entry ID: , V1.1, 11/

17 5 Configuration Example Configuration 10. Perform steps 3 through 5 also for the Digital_Icon faceplate. In Property interface > Process > State of the Printout of tags column, click the... button. Enter the following expression: "HmiData" & TagNaming.SeparatorChar & Right(Block.DB.SymbolicName, 9) & ".qdwstate" In this case, not the entire UDT will be used, but only one tag included in it, qdwstate Creating the layout The faceplates are used in a pop-up screen. To this end, one pop-up screen with three faceplates (Overview, Messages and Service) is created per FB. The following guide shows you how to create the individual faceplates in the pop-up screen using layout fields. Table Open the Template PopUp Digital pop-up screen. 2. Draw a rectangle over the white background. Entry ID: , V1.1, 11/

18 5 Configuration Example Configuration 3. Open the Layout task card and drag the rectangle to Layer In the Inspector window, open the Plug-ins tab and check the Use as layout field check box. 5. Enter a name for the layout field, for example Overview. 6. Use Horizontal alignment and Vertical alignment to select the later alignment of the faceplate using the layout field if the rectangle s size differs from the faceplate s size. Entry ID: , V1.1, 11/

19 5 Configuration Example Configuration 7. Insert another rectangle. Move this rectangle to Layer 2. Check the Use as layout field check box and enter the name Messages. Set the alignment. 8. Insert a third rectangle. Move this rectangle to Layer 3. Check the Use as layout field check box and enter the name Service. Set the alignment. 9. To view the pop-op screen properties, press <Esc>. 10. In properties > General > Name, enter the following expression: "PopUp" & Right(Block.DB.SymbolicName, 9). 11. If necessary, Screen group allows you to define the name of a folder to which the pop-up screens will be sorted, e.g. Digital. This enables you to design your project more clearly. Entry ID: , V1.1, 11/

20 5 Configuration Example Configuration 12. Click the X button in the top right corner of the pop-up screen. In the Inspector window, open the Plug-ins > events tab. Enter the ShowPopupScreen event. In the Name of the screen row, enter the name of the pop-up screen: "PopUp" & Right(Block.DB.SymbolicName, 9). Enter any value for the x- and y-coordinate, e.g. 0. From the Display mode drop-down list, select Off. 13. Use drag and drop to move the button to the Master copies folder of the project library and delete the button from the screen. 14. Put a BtnClose layout field to the place where the button was. 15. Use drag and drop to move the pop-up screen to the Master copies folder of the project library. 16. Open Screen_1. The screen includes an invisible button that will later be used to open the pop-up screen. A system function has already been configured to the Release event of the button. Entry ID: , V1.1, 11/

21 5 Configuration Example Configuration 17. Select the button and in the Inspector window, open Plug-ins. In Miscellaneous > Name, enter the following expression: "btn" & Right(Block.DB.SymbolicName, 9) 18. Open the events tab. 19. In Click, select the ShowPopupScreen event. In Name of the screen, Name, enter the name that you have set in the pop-up screen (step 12). In this example: "PopUp" & Right(Block.DB.SymbolicName, 9) Enter the x- and y-coordinates as an integer value or HMI tag. Set the other parameters using the drop-down list. 20. Use drag and drop to copy the button to the Master copies folder of the library and then delete the button from the screen. 21. Insert a rectangle into the screen and configure it as an Icon layout field. Entry ID: , V1.1, 11/

22 5 Configuration Example Configuration 22. Copy the layout field and paste it into the screen multiple times. successively generates the screen elements for which you select the Icon layout field (see next chapter) at the positions defined by the recatangles. Note: If less screen elements are generated than there are layout fields, the other positions remain free. If more screen elements are generated than there are layout fields, a new screen is created. Entry ID: , V1.1, 11/

23 5 Configuration Example Configuration 23. Insert another Button layout field group. Position it at layer 1 exactly above the Icon layout fields. 24. Use drag and drop to move the screen to the Master copies folder of the library. Entry ID: , V1.1, 11/

24 5 Configuration Example Configuration Creating screen rules Using screen rules, you assign the screen elements in the operator panel to the blocks in the controller. Unlike the screen rules in Configuration Example 1, you additionally use the layout fields. Table Select Common data > > Screen rules to open the Screen rules editor. 2. Insert a new rule, digitaloverview. As the program block, select the Digital block. As the screen object, select the Types > Digital > Digital_1_Overview faceplate. As the master copy of a screen, select Template PopUp Digital. Select the Overview layout field. 3. Insert three more rules: digitalmessages, digitalservice and digitalclose. The entries of the last rule are automatically applied. For the rules, customize only the Screen object and Layout field fields. 4. Insert a digitalicon rule. As the screen object, select Digital_Icon ; as the master copy of a screen, select Screen_1 and as the layout field, select Icon. Entry ID: , V1.1, 11/

25 5 Configuration Example Configuration 5. Insert a digitalbutton rule. From the Master copies folder of the library, select the Digital_001_Button screen object and select the Button layout field. 6. If you are using many rules in your project, you can group the rules for greater clarity. To do this, select the rules and click the Create folder button. 7. Enter a descriptive name for the group. Entry ID: , V1.1, 11/

26 5 Configuration Example Configuration Creating tag rules While the visualization is generated, you define whether will apply all PLC tags to the operator panel or only used ones. If no other settings are made, will insert the HMI tags into the default tag table. Tag rules allow you to define to which tag table will generate the tags. Table Open the Common data > > Tag rules editor. 2. Create a new rule. As the tag table, enter TagTable_Digital. As the condition, enter the following expression: Contains (HmiTag.SymbolicName, digital ) Using conditions, you define under which circumstances a rule will be run. Aside from the tag rules, the conditions are also available to you in screen rules and text list rules. The Contains(string, search) function checks whether a string contains another string (search) and returns true or false. If you define multiple tag rules, the index allows you to define the order in which runs the rules. Entry ID: , V1.1, 11/

27 5 Configuration Example Configuration Creating copy rules Using the copy rules, you create elements without a PLC connection in the operator panel. You have to store the elements as a master copy in a library. In this Configuration Example 2, you create a tag table that contains tags for navigation. Table Use drag and drop to move the MenuControl tag table to the Master copies folder of the library. 2. Open the Common data > > Copy rules editor. 3. Create a new rule, MenuTags, and as the library object, select the MenuControl tag table. Entry ID: , V1.1, 11/

28 5 Configuration Example Configuration Generating the visualization You have made all the settings necessary for this example. Now you can generate the visualization. Generation requires that an HMI connection has been established between the operator panel and the controller. In addition, the control project must have been compiled. Table Create an HMI connection between the operator panel and the controller and compile the control project. 2. In the project tree, select the operator panel for which you want to generate the visualization. You can either use the operator panel in the project or you can add new operator panels. If you want to generate multiple operator panels at the same time, select the project name from the project tree. Using the faceplates in this project, you can generate the visualization for Comfort Panels, 2 nd -generation Mobile Panels and WinCC Runtime Advanced. In Entry \4\, you will find more faceplates for WinCC Runtime Professional. 3. Right-click and select Generate the visualization () or click the appropriate icon in the menu bar. 4. Use the check boxes to select the devices for which you want to generate the visualization. Then click Generate. 5. The window shows the current progress. Entry ID: , V1.1, 11/

29 5 Configuration Example Configuration 6. In the Inspector window, you will find information, warnings and errors that have occurred during generation. 7. automatically generates the elements highlighted in the below figure. Entry ID: , V1.1, 11/

30 6 Additional Notes 6 Additional Notes Analyzing objects You have the following options to identify objects generated by in your project. Screens and pop-up screens are marked by the following icon in the project tree. Figure 6-1 icon In the screens, the screen elements generated by are marked with color. This allows you to directly see which screen elements were included in the master copy and which ones were generated using screen rules. Figure 6-2 Screen element marking Use Options > Settings > to disable this marking or change the color. Figure 6-3 Marking settings The marking is only visible in the engineering system and does not affect Runtime. Entry ID: , V1.1, 11/

31 6 Additional Notes In the Generation overview, you can see which screens/screen objects, tags and text lists were generated by. In addition, you can see the program blocks and rules by which the elements were generated. Figure 6-4 Generation overview The Generation matrix shows you which screen elements were generated by which program blocks. Figure 6-5 Generation matrix When you select a block in the controller, Plug-ins displays the rules associated with this block and the Generation overview. Figure 6-6 STEP 7 view Entry ID: , V1.1, 11/

32 6 Additional Notes Editing objects If you edit the layout of objects after generation (e.g., reposition a screen element in the screen, resize it, etc.), this setting will be retained by for the next generation process. If you delete objects generated by after generation without modifying the appropriate rules, they will be generated again in the next generation process. Editing projects You can also open and edit projects created using with a TIA Portal installation without. If you want to create or change settings and rules or generate the visualization, you need the installation. Entry ID: , V1.1, 11/

33 7 Links & Literature 7 Links & Literature Table 7-1 Topic \1\ Siemens Industry Online Support \2\ Download page of the entry \3\ Creating Faceplates with WinCC Runtime Advanced and Comfort Panels \4\ Example Blocks for WinCC (TIA Portal) and STEP 7 (TIA Portal) for S and S with SCL 8 History Table 8-1 Version Date Modifications V1.0 11/2016 First version V1.1 12/2016 Note added (SIMATIC S7-PLCSIM Advanced) Entry ID: , V1.1, 11/