Page 1 of 1

Replacing the base model in the current UaModeler version

Posted: 21 Feb 2023, 14:12
by Patrick1337
Hello,
I have a problem that when I create my own InformationModel, I need to use a specific version of the base model "Opc.Ua.NodeSet2.ua".
E.g.:
exactly this one:
<RequiredModel ModelUri="http://opcfoundation.org/UA/" PublicationDate="2020-07-15T00:00:00Z" Version="1.04"/>.

Now the question is how do I implement this with UaModeler. When creating the project it could theoretically be selected, but the base model is always selected and cannot be deselected. Replacing the models stored in the installation folder is after all not recommended.

Best regards
Patrick

Re: Replacing the base model in the current UaModeler version

Posted: 21 Feb 2023, 15:55
by Support Team
Hi,

OPC UA specifications tend to be downward compatible, hence there is no reason to load an "old" NS0 model. In fact you should typically not load any NS0 model into the UaModeler, because UaModeler comes with its own built-in NS0 Model (and it has features that relate to the built-in model, including templates for generating code for different versions of the different SDKs). The "version" of NS0 has no meaning, the type system grows with the version (new types added), but remains downwards compatible (with very few, but irrelevant exceptions).