UAG Technical Training

1. UAG Technical Training 08 Template Types

2. What you learn in this chapter • Template Types • Pre-defined higher level functions • Organized in Libraries • Setting up a Library and Template Types • Change Propagation of Template Types • Template Instances • Instantiating a Template • Linking to the Topological Model • Additional Control Modules and Variables • Handling of Change Propagation

3. Template Types and Instances • Template Types • Pre-defined higher level functions, e.g. PID Control, Sequence • Combination of multiple Control Modules with • Variables and Properties • Pre-wired Links and Interlocks • Common or single HMI symbols • Organized in Libraries • Instances • Instantiation on Equipment Level • As Equipment and Control Modules • Naming of Equipment is applied • Wiring of the open Links and Interlocks • Connection to the Topological Model

4. Add a Template Library • Add a Template Library • Select “New Template Library” from Template Libraries’ context menu • Enter a name and a description • Apply Template Library • Remarks • A new Template Library can also be added from the Customization • Existing Libraries can be opened in the UAG project and included.

5. Add a Template Type • Add a new Template Type • Select “New Template Type” in the context menu of the library • Enter a name and a description • Select the HMI Symbol • HMI symbol of template: A common symbol (Genie) for the entire template • HMI symbol of members: The symbols (Genies) of the single member Control Modules are used • Optionally add a help file • Apply the Template Type

6. Add Members to Template Type • Add a Control Module Member • Select “New Control Module” from the type’s context menu • The dialog opened is the same as for regular Control Modules in the Physical Model • Select the SCoD type, enter a name and description • Set the properties of the Control Module as necessary • Apply the Control Module

7. Properties of a Template Type • Template Properties • Allow quick configuration of Template instances (like Control Module Properties) • Add Properties to the Type • Select “Open Property List” from type’s context menu • Select “add from Member Control Modules”, if an existing property should be visible on Type level • Select “New” from context menu of the property list, if property that does not exist for a Control Module should be created

8. Properties of a Template Type • Add existing Property • Select “Add from Member…” in property list’s context menu • Select the properties that should appear on the level of the Template • Name of the Tab and Position on the Tab can be adjusted in the property list

9. Properties of a Template Type • Add new Property • Select “New” in property list’s context menu • Select the variable and its property that should become a Template property • Enter a caption name for the property • Name of the Tab and Position on the Tab can be adjusted in the “Position” tab • Apply Property

10. Links and Interlocks in Template Types • Links • Links of member Control Modules can be pre-wired with all variables that exist inside the Template Type • New Variables can be defined on Template or member level • Workflow is the same as for regular Links • Interlocks • Interlocks of member Control Modules can be pre-wired with all variables that exist inside the Template Type • New Variables can be defined on Template or member level • Workflow is the same as for regular Links • An Interlock must be fully configured. It is not possible to keep function block connections open that are set in the instance

11. Connection to the Topological Model • Template Type • There is no link to the Topological Model • Template Instances • On instantiation, or later via Equipment properties can be set • The executing PLC • The HMI/Control Domain and the Picture • Once a PLC is set the IO signals can be assigned • There is no difference in Workflow compared to a standard Equipment

12. Save a Template Library • Save a Template Library • In opposite to the rest of a UAG project a Template Library has to be saved • A modified and unsaved Library is indicated by an asterisk • In the UAG project always the last saved version is applied • Changes are propagated to the instances • For save use “Save” from context menu of the Template Library

13. Instantiate Template Type • Instantiate a Template • Select “New Equipment” in context menu of Physical Model • Checkmark “Use Template” and select the Template • Enter a name and a description • Optionally assign PLC and HMI • Set the Template’s properties • Apply Template

14. Instantiate Template Type • Appliance of Naming Rules • When the Template is instantiate the following dialog is popped up • Instance names can be adjusted according to the needs • Instance names must be adjusted according to the naming rules • The checkmark indicates a valid name according to the rules

15. Use instantiated Template • Interlocks, Links • Interlocks and Links can be defined with the standard workflow for Control Modules • Only those Interlocks and Links can be defined that were not defined in the Template Type definition • Already in the Type defined Interlocks and Links do not appear in the lists of Interlocks and Links • Connection to the Topological Model • The connection to the Topological Model is done in the same way as for standard Equipment and Control Modules, i.e. • Assigning of PLC, HMI and Picture in the Equipment • Assigning of IO_PLC variables to the IO cards

16. Additional Control Modules & Variables • Additional Control Modules • Additional Control Modules can be added to a Template Instance • They are not part of the Template instance but displayed on the same HMI picture • Additional Hierarchy Elements • If the definition of the Physical Model allows additional hierarchy levels can be added to a Template Instance • Color Indication • Template Instances are displayed in blue, standard instances are displayed in black • There is no color indication for Variables

17. Modification of Template Type • Modifications of Template Type • Template Types can be modified • Modifications are applied to the instances when the library is saved • Impact on Instances • A dialog is popped up that list all affected instances and the changes done • The user can decide if the particular instance is updated, deleted or disconnected • In case of disconnection the instances are converted to regular Equipment and Control Modules • There are cases where an update of particular instances is not possible due to name conflicts, e.g. an additional Control Module exists with the same name

18. Define Template Types by Drag & Drop • Drag & Drop from Physical Model • Existing Equipment with Control Modules can be dragged to a Template library node • User is asked for a name and description • All links to the Topological Node are stripped • All references that are outside the Equipment and the Control Modules are stripped, e.g. • A Link Variable that is not part of the Equipment • Interlocks that use those Variables • New Template Type gets created and has to be saved

19. Reference Existing Template Libraries • Existing Libraries • Existing libraries can be opened via the context menu • Include • To use an existing library it has to be included into the project via the context menu • Exclude • An included library can be excluded via the context menu • Read only • Only the first UAG project that opens a library gets the write access

20. Summary Template Types • Template Types • Combination of multiple Control Modules with • Variables and Properties • Pre-wired Links and Interlocks • Common or single HMI symbols • Organized in Libraries • Changes are propagated • Instance • Instantiation on Equipment Level as Equipment and Control Modules • Wiring of the open Links and Interlocks • Connection to the Topological Model • Propagated Changes can be applied or Instance is disconnected