Application and project settings
The application itself and each project includes XML-based configuration files, which contain different settings that influence the behavior of the application. Such settings are described in the following chapters.
Application settings
The configuration file directory (see Application directories) includes the file TE6100.config, which contains configuration parameters for the TwinCAT OPC UA Nodeset Editor application. There is a graphical dialog for this file in the user interface under Tools => Options. Unless otherwise stated, changes take effect immediately.
The following options are available.
Section | Option | Description |
|---|---|---|
General | Color Theme | Sets the default theme for the application. |
General | Show namespace index in tree | Enables/disables the display of the NamespaceIndex as a number in the Type and Instance Explorer. |
General | Show data type in tree | Enables/disables the display of the DataType in brackets in the Type and Instance Explorer for variables. |
General | Enable live scrolling | Enables that the view is updated live when the scrollbar is moved in the tree. Has a significant impact on performance when searching and scrolling in larger projects. |
General | OPC UA server dir | Default storage location of the TwinCAT OPC UA Server installation. This path is used when deploying a nodeset to the TwinCAT OPC UA Server. |
General | Projects dir | Default base directory for new projects. |
Logging | Enable Logging | Enables/disables logging. |
Logging | Output Directory | Path to the log file |
Logging | Severity Level | Sets the severity level at which messages are logged and displayed in the Message Viewer. Debug activates all messages and is not recommended for productive use. |
Nodesets | Core Nodeset File Path | Path to the OPC UA base nodeset (used for all base data and object types). This nodeset is loaded by default for every new project. |
Nodesets | Library Directory | Default base directory for type nodesets. This directory is opened by default whenever you import type nodesets. |
Nodesets | Order Attributes On Export | If this option is set to true, the attributes of all XML elements are sorted in alphabetical order, with common attributes at the top (e.g. NodeId and BrowseName) and others following in alphabetical order. Tip: If you want to compare a nodeset saved by this software with another nodeset (e.g. with “git diff”), it can be useful to set this to false to avoid unnecessary changes. |
Nodesets | Order Nodes On Export | If the setting is "true", the nodes are sorted uniformly according to NamespaceId and NodeId and sub-elements (DisplayName etc.) in accordance with the specification. Tip: If you want to compare a nodeset saved by this software with another nodeset (e.g. with “git diff”), it can be useful to set this to false to avoid unnecessary changes. |
Nodesets | Xml Schema File Path | Path to the OPC UA Nodeset XmlSchemaFile, which is used for the (syntax) validation of nodesets. |
Advanced | AllowDownloadFromInternet | The Nodeset Editor already contains a specific version of the base nodeset. By changing this setting to “true”, the most current version will be downloaded from the OPC Foundation instead. |
Advanced | Disable mapping validation | If activated, all mappings are allowed, regardless of whether the mapping validation fails. (Mapping a BOOL to an Int32, for example, would otherwise be prevented) |
Advanced | Show hint if mapping may not be valid | If activated, a message is displayed if the validation of a mapping fails. |
Advanced | Enable value editor | Activates an experimental editor for editing the values of instance nodes. |
Advanced | Allow add of user specific extensions | Activates an experimental editor for editing the extensions of instance nodes. |
Advanced | Show new name prompt when instantiating new nodes | Activates a dialog that allows you to name an instance node directly during drag and drop. |
Project settings
There is no graphical dialog for these settings yet. Changes to this file require the editor to be stopped beforehand or the project to be unloaded, as changes could otherwise be overwritten.
Parameter | Description |
|---|---|
LocalOpcUaServer | Default storage location of the TwinCAT OPC UA Server installation. This path is used when deploying a nodeset to the TwinCAT OPC UA Server. When creating a new project, this path is taken from the corresponding application settings parameter (see above) but you can overwrite it on a per project-specific basis. |
Nodesets | Contains a list of all nodesets that belong to this project including their path, NamespaceName, version and PublicationDate. |
If an invalid configuration is recognized, you will be presented with a dialog informing you about the invalid parameter.
The software will attempt to correct invalid configurations automatically if you click OK. This is done by resetting the configuration to its default value. Example:
