-
Notifications
You must be signed in to change notification settings - Fork 149
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
Robotics/Opc.Ua.Robotics.NodeSet2.xml - namespace version & PublicationDate not updated in the Server / Namespaces section #99
Comments
Can you please describe the two corrections by naming the line number or copying the changed corrections? |
Here the changes from my repo commit: @@ -111,7 +111,7 @@ ns=1;i=15011 1.01 1.01.2 @@ -121,7 +121,7 @@ ns=1;i=15011 2020-05-20T00:00:00Z 2021-05-20T00:00:00Z |
sorry - now i am confused - here the linkt to the latest robotics nodeset: The version and PublicationDate is as you mentioned in your modified nodeset: What is the topic about ns=1;i=15011? What is meant by @@ xxx - xxx @@? |
I am sorry for the confusion. The above extract was the comparison of the two versions after my correction. The two problematic places are the Version and PublicationDate from the Server -> Namespaces section, marked below from the current Robotics nodeset: ` ` They do not match the correct ones, 1.0.1.2 and 2021-05-20T00:00:00Z respectively, of the nodeset. After debugging the OPC UA Python server opcua-asyncio, I realized that the actual version and dates are taken from there. I hope that this is clear now. Plamen |
so this issue can be closed, because the Python software does not work well and the Robotics nodeset has is ok? |
as you formulate it as a question, here my answer: it could be that the opcua-asyncio server has an unusual interpretation of the namespace dependencies, nevertheless, only the Robotics nodeset shows this difference between NamespacePublicationDate / NamespaceVersion respectively PublicationDate / Version tags. I would fix it. |
So in the latest Robotics nodeset it is ok. Because the version and date are correct: You created a new issue for the Python Server : FreeOpcUa/opcua-asyncio#1464. |
I don’t think so. Where is the problem to bring the Namespace* tags from lines 114 and 124 in sync with line 37 in the modeste file? |
Thanks - now I have seen it - ich forked and changed the lines... and started a pull request to get it final |
This causes problems with loading into some OPC UA server. Concrete example: the Python one, https://github.com/FreeOpcUa/opcua-asyncio. Attached the modified file with the two corrections.
Plamen
Opc.Ua.Robotics.NodeSet2_mod.zip
The text was updated successfully, but these errors were encountered: