Skip to main content

the `nodesets` section

The nodesets section in the configuration file allows you to specify which OPC UA nodesets (NodeSet XML files) should be loaded by the server at startup. This is essential for defining the structure and semantics of the OPC UA information model that your server will expose.

example of nodesets section in the configuration file​

nodesets:

    - di
    - uri: http://sterfive.com/UA/MyAnalyserDevice/
      alias: t
      nodeset2: ./model/MyAnalyserDevice.Nodeset2.xml

  • NodeSet2.xml contains mainly new ObjectType and VariableType, or DataType definition.
  • Opcua Omni Edge allows you to easily instantiate these new ObjectType and VariableType in the instances section, allowing you to create a rich and extensible OPC UA information model.

Importing Custom Nodesets​

You can also import custom nodesets by specifying their file paths in the nodesets section of the configuration file. This allows you to extend the OPC UA information model with your own data types and structures.

Example of importing custom nodesets in the configuration file​

nodesets:

    - uri: http://sterfive.com/UA/MyAnalyserDevice/
      alias: t
      nodeset2: ./model/MyAnalyserDevice.Nodeset2.xml

Notes:​

  • The nodeset file is referenced by a file filepath relative to where the config.yaml file of your edge server is located.
  • You can use a OPCUA Modeler tool to create your own nodeset XML files. The server will load these files at startup, allowing you to extend the information model with custom data types and structures. One such tool is the OPC UA Modeler, which provides a great way to create, manage, document, and versionned OPC UA nodesets.
  • The server will automatically load the nodesets specified in the configuration file when it starts up. If you add or remove nodesets, you will need to restart the server for the changes to take effect.
  • The standard nodeset (UA) is always loaded by default, so you don't need to specify it in the configuration file. However, you can still reference it in your custom nodesets or mappings if needed.