Log In
Home
05/31/2023
Offline
Please understand that I'm new to OPC UA and still learning, so I apologize if my question seems obvious.
I'm working on updating a Python tool that generates a subset of nodes from the NodeSet2 list(s). However, I've encountered a problem with it. Previously, the tool would read multiple files from the older NodeSet2 XML files (such as Opc.Ua.NodeSet2.Part3.xml, Opc.Ua.NodeSet2.Part4.xml, etc.). It would then merge them into a single large XML file and filter out individual nodes that are not needed.
Now, it seems that in the newer versions, there is only one big file called Opc.Ua.NodeSet2.xml (here). To my understanding, this file already contains all the nodes from all the parts merged into one 'mega' file. However, I only need a specific subset of those parts, not all of them.
So my question is: Is there any way to identify which nodes belong to which original XML (specification) part so that I can filter them accordingly?
I haven't been able to find a solution for this, so any explanation or guidance would be greatly appreciated.
05/30/2017
Offline
There is a tool under development that will allow people to select the profiles they want to support and it with produce a NodeSet with the nodes needed to implement those profiles. A prototyping exists and should be live later this year.
In the meantime you have to take the whole NodeSet.
How are you using it? There are other strategies you can use to reduce the resource consumption.
05/31/2023
Offline
I am new to this project and not really familiar with all the inner workings.
But basically we filter it because the standard requires us to only provide nodes that we actually support, not because of resource constraints.
Now we will try to bridge the gap until the tool is released (we have a few ideas to try), but worst case scenario we will just have to postpone until the tool is available.
Thanks for your help.
05/24/2022
Offline
Are there any news on this toppic?
We at the Technical Univeristy of Munich are developing standardized OPC UA information models for machines of the food and beverage industry and probably have a similiar problem or requirement.
At the moment we are struggeling to implement our information model because we have in total far more than 1000 Nodes (just for the TypeSystem) because we are use many other CSs and our own information model also brings 900 Nodes. I know there is the possibility to create a reduced NamespaceSubset of all required Namespaces with only the needed types for the instance. But is there a helpful tool to do this in an automated way instead then deleting the types manually?
Thanks a lot for your support!
Romy
05/30/2017
Offline
The tool is in an alpha state and not useful for end users.
1 Guest(s)
Usage Policy