GWS templates: Difference between revisions
(Uus lehekülg: 'Starting from GWS version ..., GWS supports creating device templates to simplify the configuration process of Martem RTU-s. There are built-in templates included in GWS, and als...') |
No edit summary |
||
| Line 1: | Line 1: | ||
Starting from GWS version ..., GWS supports creating device templates to simplify the configuration process of Martem RTU-s. | Starting from GWS version ..., GWS supports creating device templates to simplify the configuration process of Martem RTU-s.<br/> | ||
There are built-in templates included in GWS, and also an option to create user specific templates. | There are built-in templates included in GWS, and also there is an option to create user specific templates. | ||
A template may contain Port settings, Device settings, Object list and Formulas. | |||
Templates can be included to the setup (and created) from the Devices tab. Note the dropdown sign next to the + button (for creating a new device). | |||
[[Pilt:Templates1.jpg]] | |||
Once a template device is selected from the list of available templates, a new device will be generated to the setup. Verify all the settings of the generated port, device, objects and formulas (if any). | |||
In order to create user specific templates, create the user specific configuration: port settings, device settings, object list and formulas (if any). Navigate to the Devices tab and click on the dropdown sign next to "New device" button (+ button). Select "create template". Note that this option is only visible, if a device exists in the setup. | |||
[[Pilt:Templates2.jpg]] | |||
The new template is now visible from the templates list. In the PC, the template is stored in the folder named "templates" that is located in the same directory as GWS.exe. The templates are stored in a csv format. | |||
It is also possible to create a template from a slave port. Note that this option is only visible, if a slave port exists in the setup. | |||
In this case, the template device contains all the objects of the specified port, that are configured in the setup (including object list, formulas and device physical I/O). The slave port template is useful for gathering all the objects from one Martem RTU to another Martem RTU (i.e slave port template is created in one RTU, but used in a setup of another RTU). | |||
Revision as of 12:19, 26 February 2015
Starting from GWS version ..., GWS supports creating device templates to simplify the configuration process of Martem RTU-s.
There are built-in templates included in GWS, and also there is an option to create user specific templates.
A template may contain Port settings, Device settings, Object list and Formulas.
Templates can be included to the setup (and created) from the Devices tab. Note the dropdown sign next to the + button (for creating a new device).
Pilt:Templates1.jpg
Once a template device is selected from the list of available templates, a new device will be generated to the setup. Verify all the settings of the generated port, device, objects and formulas (if any).
In order to create user specific templates, create the user specific configuration: port settings, device settings, object list and formulas (if any). Navigate to the Devices tab and click on the dropdown sign next to "New device" button (+ button). Select "create template". Note that this option is only visible, if a device exists in the setup.
The new template is now visible from the templates list. In the PC, the template is stored in the folder named "templates" that is located in the same directory as GWS.exe. The templates are stored in a csv format.
It is also possible to create a template from a slave port. Note that this option is only visible, if a slave port exists in the setup. In this case, the template device contains all the objects of the specified port, that are configured in the setup (including object list, formulas and device physical I/O). The slave port template is useful for gathering all the objects from one Martem RTU to another Martem RTU (i.e slave port template is created in one RTU, but used in a setup of another RTU).