For the graphic design of the user interface, the toolbar offers a comprehensive set of objects and graphic elements.
Customized display and operating objects consisting of a configured group of objects are created as faceplates. The screen window technology is used for the display of a screen in screen.
By storing configured objects, object groups and faceplates in libraries, they can be used repeatedly.
The objects stored there are available to all similar type HMI devices in the project (“Project Library”) or in other projects (“Global Library”).
For dynamization of faceplates and screen windows, it is preferable to use a user data type that bundles various tag types in a user-defined data structure for a process unit such as a motor. User data types are stored in the project library and are available throughout the project.
The object-oriented configuration is useful for:
• Configured objects and object groups
• Faceplates (see chapter 5.3.2)
• Screen windows (see chapter 5.3.3)
• User data types (see chapter 5.3.4)
• Project functions (see chapter 5.3.5)
Note
Configured objects or object groups, faceplates and user data types are created for the respective use case and tested with the customer before they are copied or
5.3.1
Master copies and types
Each of the libraries mentioned above (see chapter 5.2) contains two folders named “Types” and “Master copies”. Library objects can be created or used either as a master copy or as a type.
As a master copy, a configured object group is moved to the master copy area of the project library and can be used repeatedly in the project. Changes to the master copy are not transferred to the copies previously created. Master copies can also be stored in a global library for use in other projects.
Faceplates and user data types are created and maintained in the “Types” folder. These are based on the type-instance model. For example, when a faceplate is integrated in a process screen, a local instance of the type is created. Changes in the type are automatically transferred to all of its instances. If necessary, an instance of the type can be deleted.
A distinction is made between the Panel / RT Advanced and RT Professional device families when the faceplates are stored under Types. The faceplates can only be reused in the same type of device family.
See also
• TIA Portal Information System > Visualize processes > Using global functions
> Working with libraries > Copy templates and types
5.3.2
Faceplates
A faceplate consists of a grouping of objects which are tailored to the special requirements of the plant with respect graphic representation and dynamization. The object properties and events used to dynamize the faceplate are individually defined in the faceplate editor. User data types are recommended for connecting the interface to the process screens.
A faceplate is always created as a type in the project library. A copy can be saved in the cross-project global library under types. Thereafter, it is available in other projects as well.
There are significantly more options for designing and dynamization with WinCC RT Professional.
See also
• TIA Portal Information System > Visualize processes > Creating screens > Working with faceplates
5.3.3
Screen window
The “Screen window”control allows you to call a screen within a screen. This functionality is used, for example, to call a window for controlling a process unit (valve, drive). Such an operator control screen is configured once for a particular function and then opened as an instance in a screen window. The dynamization of a screen window is carried out based on user data types. When the screen is called, a tag prefix is transferred.
See also
• TIA Portal Information System > Visualize processes > Creating screens > Display and Control Objects > Objects > Screen window (RT Professional)
5.3.4
User data type
User data types are used for dynamization of faceplates and screen windows. For a process unit, such as a motor, a user data type is defined, which contains all tag types of the motor as elements.
Each user data type is created for a particular type of communication (SIMATIC S7-300/400, SIMATIC S7-1200, SIMATIC S7-1500, internal communication, etc.) and for a Panel / RT Advanced or RT Professional device family and can only be used in this environment.
The example shows a simplified form.
See also
• TIA Portal Information System > Visualize processes > Working with tags > Working with user data types (Panels, RT Advanced, RT Professional)
5.3.5
Project functions in the form of scripts
Customer-specific requirements that are not covered by the basic functionality can be realized in the form of functions or local scripts. A function consists of
standardized system functions and/or user-defined functions.
If such user-defined functions are required repeatedly, they should be configured as project functions in the “Scripts” editor.
The function code is created one-time in the script, then tested and qualified. The function is then available for this HMI device and after moving it to the project library under “master copy” it is also available project-wide for several HMI devices (see chapter 6.3 “User-specific functions and scripts”).