Controller Configuration Library - Importing 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 previously exported controller template can be imported in a 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 Add and then select the Import tab in the Create new controller template window.
Select Open file and select the desired import file. The file must have the format <controller_template_name>.json. Select Open.
The workspace shows an updated list of Controller templates.
The exported file can be given any name with the *.json extension. The *.json file contains a controller template name that is shown in the list of controller templates. When a controller template is imported, the name given to the controller template is taken from 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 having identical names, it is advised to give the template a unique name before exporting and not to change the file name.
