Controller Configuration Library - Exporting a Controller Template
The Controller template is an entire virtual controller. It allows a user to create, edit and analyze all controller configurations without having access to a physical controller. A controller template can be created from the beginning with all parameter values empty. A controller template can be created by copying an existing controller with valid configurations and parameters.
A Controller template does not show information about tools, as no tools are connected. Hardware related information and configurations are not possible. Configurations of supporting functions, like various servers, are not possible from a template. When a template is distributed to a controller, these parameters must be checked or added.
A controller template can be exported and then reused (imported) in another ToolsTalk 2 installation or in a ToolsTalk 2 Station Setup installation.
Select Library
in the left-side menu bar. Go to Controller configuration
.The workspace shows a list of Controller templates.
Select the check box of the controller template to be exported.
Select Manage and choose Export from the drop-down menu.
A browser window opens for saving the export file.
The default file name is <controller_template_name>.json Select Save.
The exported file can be given any name with the *.json extension.
Inside the exported *.json file the controller template is given the name from the controller column. When a controller template is imported, the name given to the controller template is taken from this field inside the *.json file, regardless of the file name. This means that an imported controller template may have a different name than the imported file name.
To avoid controller templates with identical names it is advised to give the template a unique name before exporting and not to change the file name.
