Section: Visu SEC Visu //optional: yes, modifier: [UPDATE] Toplevel_Tab; //optional: yes, type: bool Embedded := [%PAGE_VISU%, <visu1>,...]; //optional: yes, type: VisuList Embedded_Proxy := [%PAGE_VI

Section: Trend SEC tre.Trend //optional: yes, modifier: [UPDATE] SEC TrendRecording : <CFC trend identifier> //optional: yes, modifier: [UPDATE] Task := <trend task> //optional: yes, type: TimeLiteral

Section: Proxies The section Proxies defines a function block which implements the proxy. A proxy serves for data exchange of modules of different application. The instance of the proxy FB represents

Section: Constraints This special section allows to check if each module instance is referenced at least once. SEC Constraints //optional: yes, modifier: [UPDATE] Referenced_By := <interface name>; //

Section: mse.Sequence This section determines the definitions of the sequence editor. The section must be present in the module declaration, in order that the editor of the modules offers the addition

Section: MacroModule This section describes the parameters for the MacroModule. The section is created automatically when you generate a macro module. As an alternative, you can insert the section int

Section: Device Generator The section DeviceGenerator serves to define all settings related to the Device Generator. It contains the following subsections: Subsection: Device : Definitions to add devi

Step 1: Create Toplevel Module "Room" Add a module declaration and a function block to the POUs pool. The function block is used for the implementation (function program) of the module. In this exampl

Step 3: Create Submodule "Switch Simple" The second switch module, which we want to declare, is a simplified one with only two states: on and off. Therefore a module declaration and a function block h

Step 4: Create Submodule "Light" As it was done before for the Switch and the SwitchSimple , for the module Light , a module declaration Light , a function block Light and an interface ILight have to