Models

You can use the UaModeler to create types, instances and references, which are represented as nodes in the address space (see Modeling). Each node can be identified by its node id which is composed of an identifer and a namespace index. For each namespace index there exists one model which is composed of all nodes with a specific namespace index. Each model is saved in a separate .ua file. To identify the models, a Namespace URI is used (e.g. http://opcfoundation.org/UA/).

The *.ua files are proprietary binary information model files that are used by the UaModeler. Instead of the *.ua files, *.xml files can be used for importing the information models. These XML files have to be valid XML files compliant with the schema of the OPC foundation (http://opcfoundation.org/UA/2011/03/UANodeSet.xsd). You can save information models in XML format with by choosing “Export XML” from the context menu of the model node in the Project Window. When using the eval version, the number of nodes to be exported is limited. To export an unlimited number of nodes, the full version of the UaModeler is required.

The UaModeler provides the following models:

• Server (http://opcfoundation.org/UA/)
• DI (http://opcfoundation.org/UA/DI/)
• PLCopen (http://PLCopen.org/OpcUa/IEC61131-3/)

The DI model is based on the Server model, the PLCopen model is based on the Server model and the DI model. It is not possible to add nodes to these models.

When you create a project you have to choose at least the Server model and create at least one custom model in the wizard. All newly created nodes have to be added to one of the custom models. You can add a new custom model (Project → Add new Model) or an already existing custom model (Project → Add Existing Model) to an open project.

In the UaModeler, all selected and created models are merged to one information model, which can be viewed in the Information Model Window.