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

Robotics/Opc.Ua.Robotics.NodeSet2.xml - namespace version & PublicationDate not updated in the Server / Namespaces section #99

Open
plamenk opened this issue Sep 27, 2023 · 9 comments

Comments

@plamenk
Copy link

plamenk commented Sep 27, 2023

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

@BFrKUKA
Copy link

BFrKUKA commented Oct 9, 2023

Can you please describe the two corrections by naming the line number or copying the changed corrections?
Because until now there have not been problems to use the nodeset with SDKs used by several companies.
Thanks

@plamenk
Copy link
Author

plamenk commented Oct 9, 2023

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

@BFrKUKA
Copy link

BFrKUKA commented Oct 9, 2023

sorry - now i am confused - here the linkt to the latest robotics nodeset:
https://github.com/OPCFoundation/UA-Nodeset/blob/latest/Robotics/Opc.Ua.Robotics.NodeSet2.xml

The version and PublicationDate is as you mentioned in your modified nodeset:
Model ModelUri="http://opcfoundation.org/UA/Robotics/" Version="1.01.2" PublicationDate="2021-05-20T00:00:00Z"

What is the topic about ns=1;i=15011?

What is meant by @@ xxx - xxx @@?

@plamenk
Copy link
Author

plamenk commented Oct 9, 2023

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:

`



NamespaceVersion

i=68
ns=1;i=15011


1.01



NamespacePublicationDate

i=68
ns=1;i=15011


2020-05-20T00:00:00Z

`

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

@BFrKUKA
Copy link

BFrKUKA commented Oct 10, 2023

so this issue can be closed, because the Python software does not work well and the Robotics nodeset has is ok?

@plamenk
Copy link
Author

plamenk commented Oct 10, 2023

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.
PS: Check this: FreeOpcUa/opcua-asyncio#1464

@BFrKUKA
Copy link

BFrKUKA commented Oct 10, 2023

So in the latest Robotics nodeset it is ok. Because the version and date are correct:
https://github.com/OPCFoundation/UA-Nodeset/blob/latest/Robotics/Opc.Ua.Robotics.NodeSet2.xml
Model ModelUri="http://opcfoundation.org/UA/Robotics/" Version="1.01.2" PublicationDate="2021-05-20T00:00:00Z"

You created a new issue for the Python Server : FreeOpcUa/opcua-asyncio#1464.
I think it is the needed to fix it there - so this issue (to change the Robotics nodeset) can be closed?

@plamenk
Copy link
Author

plamenk commented Oct 10, 2023

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?

@BFrKUKA
Copy link

BFrKUKA commented Oct 10, 2023

Thanks - now I have seen it - ich forked and changed the lines... and started a pull request to get it final

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

2 participants