View Issue Details

IDProjectCategoryView StatusLast Update
0009230UAFX NodesetImplementation Bugpublic2023-11-10 14:27
ReporterReid Jun Li Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.00.02 
Summary0009230: opc.ua.fx.cm.nodeset2.xml have some nodeid with the same 'BrowseName' in the same path of UAFX-1.00.00-2022-10-15
Description

got the file from https://github.com/OPCFoundation/UA-Nodeset/tree/latest/UAFX, last Last commit message is UAFX-1.00.00-2022-10-15

For example, both 6029 and 6060 have the same 'BrowseName' and 'ParentNodeId'
<UAVariable NodeId="ns=1;i=6029" BrowseName="1:FunctionalEntityNode" ParentNodeId="ns=1;i=5052" DataType="PortableNodeIdentifier" AccessLevel="3"> <DisplayName>FunctionalEntityNode</DisplayName> <References> <Reference ReferenceType="HasModellingRule">i=78</Reference> <Reference ReferenceType="HasTypeDefinition">i=16309</Reference> <Reference ReferenceType="HasComponent" IsForward="false">ns=1;i=5052</Reference> <Reference ReferenceType="HasProperty">ns=1;i=6030</Reference> </References> </UAVariable>
and
<UAVariable NodeId="ns=1;i=6060" BrowseName="1:FunctionalEntityNode" ParentNodeId="ns=1;i=5052" DataType="PortableNodeIdentifier" AccessLevel="3"> <DisplayName>FunctionalEntityNode</DisplayName> <References> <Reference ReferenceType="HasModellingRule">i=78</Reference> <Reference ReferenceType="HasTypeDefinition">i=16309</Reference> <Reference ReferenceType="HasComponent" IsForward="false">ns=1;i=5052</Reference> <Reference ReferenceType="HasProperty">ns=1;i=6061</Reference> </References> </UAVariable>

Another pair is 6030 and 6061

If build with Unified Automation SDK, it will report a lot of node id redefinition warning since it use the browse path to represent the node id.

TagsNo tags attached.

Activities

Paul Hunkar

2023-11-10 06:02

manager   ~0020322

The issue has been taken care of in the 1.00.02 nodeset

Paul Hunkar

2023-11-10 14:27

manager   ~0020330

Reviewed changes in call, agree and closed issue

Issue History

Date Modified Username Field Change
2023-11-03 06:19 Reid Jun Li New Issue
2023-11-03 13:15 Paul Hunkar Assigned To => Paul Hunkar
2023-11-03 13:15 Paul Hunkar Status new => assigned
2023-11-10 06:02 Paul Hunkar Status assigned => resolved
2023-11-10 06:02 Paul Hunkar Resolution open => fixed
2023-11-10 06:02 Paul Hunkar Fixed in Version => 1.00.02
2023-11-10 06:02 Paul Hunkar Note Added: 0020322
2023-11-10 14:27 Paul Hunkar Status resolved => closed
2023-11-10 14:27 Paul Hunkar Note Added: 0020330