Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodeset import error #85

Open
Lukas1811 opened this issue Aug 19, 2019 · 4 comments
Open

Nodeset import error #85

Lukas1811 opened this issue Aug 19, 2019 · 4 comments

Comments

@Lukas1811
Copy link

There are a few different bugs while importing nodesets, in my case it is the official DI nodeset by the OPC foundation. The first problem is that it only works if I import the Opc.Ua.Di.Nodeset2.xml file from the python-opcua schema folder, if I import the one from the OPC Doundations GitHub repo I get a lot of errors.
The next issue is that if I save the file and reload it, the programm couldn't reload the previously imported Nodeset, due to the fact that only the file name is saved in the .uamodel file and not the path. If you add the path each time manually the import works flawless.

@oroulet
Copy link
Member

oroulet commented Aug 19, 2019

I known there are many rough edges in that progam. Great if you could try to fix this. The issue with saving path is that you cannot move the file afterward... not sure how to solve that...

@zerox1212
Copy link
Collaborator

Saving path might be better. If someone moves it we could throw a file not found error.

As for other bugs, keep in mind you also need to look at code in the main python opcua library. That is where all the XML stuff is.

@oroulet
Copy link
Member

oroulet commented Aug 20, 2019

maybe we can save the path but if the file name is found in the same directory then use it

@benkinooby
Copy link
Contributor

How about using prioritized "include paths" where the modeler searches for the referenced model files. The paths may be absolute as well as relative paths. By default, the current path ./ has highest priority (this is what is proposed in #85 (comment) with optional, additional paths to search)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants