 |
UaModeler
1.6.5.472
|
|
UaModeler
1.6.5.472
|
Before working with UaModeler, you have to create a project. This is described step-by-step in the section HowTo and Short Tutorial.
By default, project files are saved to the user’s home directory and contain the extension tt2pro. To load an existing project file, choose File → Open… from the menu or click on the yellow folder icon.
A graphical representation of the current project is shown in the Project Window. The screenshot below shows the project created in the HowTo (Windows): Create a New Project With a Method. The top node represents the Project itself, beneath it you can find a folder containing the models which have been added to the project and the template set which has been chosen when creating the project.
When selecting one of these nodes in the project window, some associated information is displayed in the Attributes Window.
When selecting the project node, the Attributes Window shows general project related information.
To edit these settings, choose Project → Project Settings… from the menu.
To select another template set, choose Project → Project Settings… from the menu. Select a new template set and continue by clicking Next. Depending on the template set, it might be necessary to fill in additional information on the following pages.
This folder contains all Models which have been added to the project.
For each new project, it is necessary to create a project specific model, which will be stored in a separate file (in our case examplemodel.ua. The standard OPC UA Server model as defined in the OPC UA Specification is added automatically.
The blue gear wheel symbol in front of a model node indicates that this model is selected for generating code for this model namespace.
Right-clicking on the Models folder opens a context menu providing the following options.
The Add New Model dialog is devided in two parts. On the top, you have to specify settings that are saved in the model file. When picking a model name, the file name and the namespace URI are filled automatically. Of course, these values can be changed to your liking.
The settings at the bottom of the dialog are template set specific and stored in the project file. Click on the question mark in the title bar of the dialog and then on the tile of the input field to display a description.
To remove a model from a project, choose Remove Model… from the context menu of the model. A model can only be removed if it is not needed by other models. UaModeler will check dependencies and show a dialog window if other models depend on the model to be removed, allowing you display the affected nodes in the Output Window.
See the page Models for more options.
The following information is displayed in the attributes window regardless of the template set which has been chosen
All other information depends on the template set.
If the user does not specify a NodeId, newly created nodes receive their NodeId directly from the UaModeler. Thus, the user doesn’t need to worry about picking unique identifiers. By default, each node class has “its own” range of numeric NodeIds, i.e. beginning from a numeric identifier, UaModeler selects the next NodeId that is not used so far. By default, these starting NodeIds are:
| NodeClass | Starting NodeId |
|---|---|
| ObjectTypes | 1001 |
| VariableTypes | 2001 |
| Objects | 5001 |
| Variables | 6001 |
| Methods | 7001 |
| DataTypes | 3001 |
| ReferenceTypes | 4001 |
| Views | 8001 |
You can modify these starting NodeIds by selecting the menu entry Settings → Select NodeIds for new nodes. To eliminate “gaps” between automatically assigned identifiers, you can use Compress Numeric NodeIds from the context menu of a model.