Supported features

With the help of OPC UA, complex information models can be created. This page provides an overview about the currently available features of the TwinCAT OPC UA Nodeset Editor. Additional features will be provided as updates over time.

Feature	Description
Creation of nested folders	Allows the creation of (nested) folders, e.g. to structure instances.
Instantiation of data types	Allows the instantiation of data types from the OPC UA Core Nodeset. The following data types, as well as their derived types, are supported: Boolean, ByteString, DataValue, DateTime, DiagnosticInfo, Enumeration, ExpandedNodeId, Guid, LocalizedText, NodeId, Number, QualifiedName, StatusCode, String, XmlElement
Instantiation of data types as arrays	Enables the instantiation of arrays of data types from the OPC UA Base Nodeset. The above types are supported. To do this, the ValueRank and ArrayDimensions attributes must be set accordingly on the instance created. Example: For a one-dimensional array with a length of 10:
Instantiation of object types (with and without methods)	Allows instantiation of object types from an imported nodeset, e.g. a companion specification. Certain restrictions may apply, see below.
Instantiation of structured data types	Enables the instantiation of structured types (all data types derived from “Structure”) from an imported nodeset, e.g. a companion specification. Certain restrictions may apply, see below. This may require further configuration steps, which are explained in more detail in our documentation about Mapping.
Mapping of variables and methods	Enables the linking of the created instances with elements from the PLC. The TwinCAT Target Browser (Tools => TargetBrowser) serves as the basis for this feature.
Online and offline mapping to various target systems	Mappings can be added to various active target systems via the ADS tab in the TargetBrowser. Mappings can be added offline using a TMC file via the TMC tab.
Handling of the ModelingRules (Optional, Mandatory, etc.)	When an object type is instantiated, sub-elements with the “Optional” and “Mandatory” ModellingRule are automatically added. Unwanted optional elements can be removed manually.
Export to TwinCAT OPC UA Server	Allows to export the created nodeset project to the TwinCAT OPC UA Server.
Export to a folder	Allows you to export the created nodeset project to a user-defined folder.

Restrictions

Below you will find an overview of which features are currently not available, yet. Additional features are added over time via software updates of this product.

Feature	Description
Dynamic array lengths	The instantiation of arrays with dynamic length is possible, but such arrays cannot currently be used in the TwinCAT PLC or the TwinCAT OPC UA Server. This applies for ArrayDimensions = 0 or ValueRank = [ -3 \| -2 \| 0].
Handling of the ModellingRules (OptionalPlaceholder, MandatoryPlaceholder, etc.)	Nodes with the "OptionalPlaceholder" and "MandatoryPlaceholder" ModellingRule must be created manually. This is currently only possible to a limited extent. Placeholder instances in the type cannot be instantiated directly. When instantiating manually under the instance of the correct data type, the reference type for the parent node cannot be modified (see below).
Create/Modify types	Creating new data or object types or changing existing types is currently not supported.
Static node values	It is currently possible to set a static value for a node using an experimental editor. This is only recommended for experts.
References	Currently the references of a node cannot be modified. When adding folders or Instances of nodes, these are referenced using Organizes references.