View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000877230040: AutomationMLImplementation Bugpublic2023-04-03 15:392023-04-27 09:23
ReporterHerbert Oppmann Assigned Tomiriamschleipen  
PrioritynormalSeveritymajorReproducibilityalways
Status feedbackResolutionopen 
Product Version1.00.00 
Summary0008772: [AutomationML] NodeSet has missing Namespace index in BrowseNames
Description

Opc.Ua.AMLLibraries.NodeSet2.xml:

Some BrowseNames are missing a namespace index, which means the default of 0 takes effect. As the nodes are instances of types defined in AMLBase, they must use the same namespace index so that they are detected as members of that type.

Children of node i=338 (AutomationMLLibs.aml): Version, InstanceHierarchies, InterfaceClassLibs, RoleClassLibs and SystemUnitClassLibs.
Children of node i=122 (ConnectionPoint): ID and Version.

Steps To Reproduce

Open SiOME (Siemens OPC UA Modeling Editor), import Opc.Ua.AMLBaseTypes.NodeSet2.xml and Opc.Ua.AMLLibraries.NodeSet2.xml, validate.

TagsNo tags attached.

Activities

miriamschleipen

2023-04-20 07:46

manager   ~0019226

Can you send us a text snippet of that issue? Do you mean e.g. the ID variable (i=123) of ConnectionPoint (i=122).
<UAVariable NodeId="ns=2;i=123" BrowseName="2:ID" DataType="String" ParentNodeId="ns=2;i=122">
Is this correct the node you are mentioning?

miriamschleipen

2023-04-20 10:57

manager   ~0019227

Can you send us a text snippet of that issue? Do you mean e.g. the ID variable (i=123) of ConnectionPoint (i=122).
<UAVariable NodeId="ns=2;i=123" BrowseName="2:ID" DataType="String" ParentNodeId="ns=2;i=122">
Is this correct the node you are mentioning?

Herbert Oppmann

2023-04-25 11:04

reporter   ~0019238

Yes, that is one of them. The BrowseName consists of Namespace (index) and Name (string), and both must be same for overriding a member in type derivation and for creating an instance of a type.

List of nodes in Opc.Ua.AMLLibraries.NodeSet2.xml, and conflicting Nodes in Opc.Ua.BaseTypes.NodeSet2.xml:
below ConnectionPoint (ns=2;i=122):
Version (ns=2;i=124) versus 1:Version (ns=1;i=6001)
ID (ns=2;i=123) versus 1:ID (ns=1;i=6002)
[Note: Version (ns=2;i=30) and ID (ns=2;i=29) and ID (ns=2;i=23) do not override these - NamespaceIndex 1 probably also missing in BrowseNames of these nodes.]
below AutomationMLLibs.aml (ns=2;i=338)
Version (ns=2;i=339) versus 1:Version (ns=1;i=6001)
InstanceHierarchies (ns=2;i=342) versus 1:InstanceHierarchies (ns=1;i=5001)
InterfaceClassLibs (ns=2;i=345) versus 1:InterfaceClassLibs (ns=1;i=5002)
RoleClassLibs (ns=2;i=344) versus 1:RoleClassLibs (ns=1;i=5003)
SystemUnitClassLibs (ns=2;i=343) versus 1:SystemUnitClassLibs (ns=1;i=5004)

miriamschleipen

2023-04-27 09:21

manager   ~0019242

Last edited: 2023-04-27 09:23

1) Can you send us one specfic example with the original and intended/corrected version of one of the nodes?
2) Is this recommended or mandatory? Does it refer to the following part of the specification: https://reference.opcfoundation.org/v104/Core/docs/Part3/5.2.4/?

Issue History

Date Modified Username Field Change
2023-04-03 15:39 Herbert Oppmann New Issue
2023-04-04 05:19 miriamschleipen Assigned To => miriamschleipen
2023-04-04 05:19 miriamschleipen Status new => acknowledged
2023-04-20 07:46 miriamschleipen Status acknowledged => feedback
2023-04-20 07:46 miriamschleipen Note Added: 0019226
2023-04-20 10:56 miriamschleipen Status feedback => acknowledged
2023-04-20 10:56 miriamschleipen Assigned To miriamschleipen =>
2023-04-20 10:56 miriamschleipen Status acknowledged => assigned
2023-04-20 10:57 miriamschleipen Status assigned => feedback
2023-04-20 10:57 miriamschleipen Note Added: 0019227
2023-04-25 11:04 Herbert Oppmann Note Added: 0019238
2023-04-25 11:04 Herbert Oppmann Status feedback => new
2023-04-27 09:21 miriamschleipen Assigned To => miriamschleipen
2023-04-27 09:21 miriamschleipen Status new => feedback
2023-04-27 09:21 miriamschleipen Note Added: 0019242
2023-04-27 09:23 miriamschleipen Note Edited: 0019242