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

can't import new official nodeset xml #84

Open
flyingToast3r opened this issue Jul 31, 2019 · 4 comments
Open

can't import new official nodeset xml #84

flyingToast3r opened this issue Jul 31, 2019 · 4 comments

Comments

@flyingToast3r
Copy link

I tried to import the nodeset file Opc.Ua.Di.NodeSet2.xml and got the error:
opcua.common.xmlimporter - WARNING - failure adding node NodeData(nodeid:NumericNodeId(ns=1;i=15035))') uawidgets.utils - ERROR - The parent node id does not to refer to a valid node.(BadParentNodeIdInvalid)')

Then I tried the older version 1.0 file as stated in the Master Plan under version 0.3:Opc.Ua.Di.NodeSet2.xml and that worked.

With other new nodeset files like from the Robotics I have the same error as stated above: Opc.Ua.Robotics.NodeSet2.xml

I couldn't track down the issue for the moment. Does anyone have some suggestions?
I used the latest relese version as well as the bleeding edge developer version from the master branch.

@flyingToast3r flyingToast3r changed the title can't import new offical nodeset xml can't import new official nodeset xml Jul 31, 2019
@oroulet
Copy link
Member

oroulet commented Aug 7, 2019

that would be really nice to fix. it probably some issues in the xml importer of python-opcua

@zerox1212
Copy link
Collaborator

XML handling is very complex, you will have to spend some time trying to debug it. Maybe you can remove most of the NodeSet2 so that you can look only at the broken node.

@oroulet
Copy link
Member

oroulet commented Mar 25, 2020

OK I found out that a newer version of the standard node definiton is needed, but they seem to have changed a litle the format 👎

@JMayrbaeurl
Copy link

@oroulet We've run into the same issue when trying to open version 1.0.4 of the official Robotics nodesets file. This file seems to be pretty current, since the last change was 6 days ago. What's needed to be able to open the Robotics nodesets file?

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