Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Importing xml models from different projects
January 8, 2018
16:05, EET
Avatar
jacob.saoumi
Member
Members
Forum Posts: 4
Member Since:
January 19, 2017
sp_UserOfflineSmall Offline

Hallo,

We want to import different xml models into the OPCUA Server address space. For Modelling we are using the unified automation OPC UA Modeler tool.

When the local server is filled with xml models generated out of one modeling project, the models can be loaded successfully without any problem . The problem occurs when the xml models are generated out of different modeling projects.

For example:

Project A Project B
0:OpcUA basics 0:OpcUA basics
1:Base model 1:Base model
2:Sensor A 2:Sensor B

At the beginning the local server has the OpcUA bas model per default and our base model gets imported.
Now the Sensor A model with namespace 2 gets imported.
When the Sensor B model from project B should be loaded, it has also namespace 2 including all references.
When there are two identical ids in namespace 2 of Sensor A and B, the according node doesn’t get loaded and thus the model is corrupted
because other references could end up in the wrong node (of Sensor A).

Is there a way of solving this issue with the SDK?
We thought of changing the namespace id for the conflicting namespaces.
Any suggestions?

January 9, 2018
10:37, EET
Avatar
Heikki Tahvanainen
Member
Members
Forum Posts: 402
Member Since:
April 17, 2013
sp_UserOfflineSmall Offline

Hello Jacob,

Thank you for the question. You should concentrate on the NamespaceUris instead of the NamespaceIndexes. The NamespaceIndexes may change on every server startup.

The issue here is that two different modeling projects are created with the same NamespaceUri. Every project should define their own NamespaceUri in order to guarantee that the NodeIds are unique.

The best way to achieve this is to edit the existing UaModeler project(s) and change the NamespaceUri(s). You can do this by right clicking the project in “Project” view and selecting “Model settings”. Here you can edit the NamespaceUri.

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 1919

Currently Online:
21 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Heikki Tahvanainen: 402

hbrackel: 144

rocket science: 88

pramanj: 86

Francesco Zambon: 83

Ibrahim: 78

Sabari: 62

kapsl: 57

gjevremovic: 49

Xavier: 43

Member Stats:

Guest Posters: 0

Members: 730

Moderators: 7

Admins: 1

Forum Stats:

Groups: 3

Forums: 15

Topics: 1529

Posts: 6471

Newest Members:

toneylapham544, rondawolinski7, Marypof5711, roycedelargie91, kourtneyquisenbe, ellis87832073466, zkxwilliemae, gabriellabachus, Deakin, KTP25Zof

Moderators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1032, Jimmy Ni: 26, Matti Siponen: 349, Lusetti: 0

Administrators: admin: 1