-
Notifications
You must be signed in to change notification settings - Fork 88
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
Comments
that would be really nice to fix. it probably some issues in the xml importer of python-opcua |
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. |
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 👎 |
@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? |
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.
The text was updated successfully, but these errors were encountered: