View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006929 40010-1: Robotics-1: Vertical integrationImplementation Bugpublic2021-05-10 06:222021-08-12 06:02
ReporterAlberto Medina Assigned ToBernd Fiebiger  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Summary0006929: Object has invalid Parent Reference.
Description

Object "ns=1;i=18764" has ParentId "ns=1;i=1022" but the ReferenceType of this relation is "ns=1;i=18181" which is not Hierarchical so it is invalid for parent child reference.

Additional Information

IsConnectedTo Reference must be defined on <MotorIdentifier/GearIdentifier> (GearType and MotorType-objects)
instead of being defined on the MotorType and the GearType . It is only needed to define the symmetric reference on any one of these objects (we will define it on the Motor-Type object)

Specification shall describe in text, that the reference "IsConnectedTo" can be only used to show relationsships of motors and gears in the same powertrain.
(it is not allowed to reference from PowerTrain1.Motor1 to PowerTrain2.Gear1)

TagsNo tags attached.

Activities

Jonas Green

2021-06-02 13:25

reporter   ~0014458

Hi, we ran into this issue while parsing the robotics nodeset. We belive the issue is that the <Motor/GearIdentifier> nodes point out the Motor/GearType nodes as parents. It is correct (according to the specification) that the Motor/GearType nodes reference the <Motor/GearIdentifier> placeholder nodes with IsConnectedTo references. Instances of these types should do the same if there is a relation between a motor and a gear. The <Motor/GearIdentifier> nodes represent placeholders for an instance of a Motor/Gear object and shouldn't have a parent-child relationship with the type, should they?

If we remove the ParentNodeId attribute of the <Motor/GearIdentifier> xml tags nodes we can parse the robotics nodeset properly.

Bernd Fiebiger

2021-06-02 14:13

manager   ~0014459

yes, you are right... we will remove the parent-child relationships with this types,
As it needs a change in the CS we have to release in WG and then enter the release process of OPC F (new Version of CS and new NodeSet etc...

Goetz Goerisch

2021-06-29 09:14

reporter   ~0014597

This pull request: https://github.com/OPCFoundation/UA-Nodeset/pull/84 with references to this mantis issue breaks existing integrations downstream.

The Opc.Ua.Robotics.NodeSet2.bsd and .xsd files were deleted.

Now 2 NodeIds files (NodeIds.csv and Opc.Ua.Robotics.NodeIds.csv) with different content exist.

Bernd Fiebiger

2021-08-10 07:50

manager   ~0014718

Last edited: 2021-08-10 07:51

Fixed with Version:
ModelUri= "http://opcfoundation.org/UA/Robotics/ " Version="1.01.2" PublicationDate="2021-05-20T00:00:00Z"
https://github.com/OPCFoundation/UA-Nodeset/tree/v1.04/Robotics

CS is in overwork

Issue History

Date Modified Username Field Change
2021-05-10 06:22 Alberto Medina New Issue
2021-05-12 06:39 Bernd Fiebiger Assigned To => Bernd Fiebiger
2021-05-12 06:39 Bernd Fiebiger Status new => assigned
2021-05-12 07:05 Bernd Fiebiger Steps to Reproduce Updated
2021-05-12 07:05 Bernd Fiebiger Additional Information Updated
2021-06-02 13:25 Jonas Green Note Added: 0014458
2021-06-02 14:13 Bernd Fiebiger Note Added: 0014459
2021-06-29 09:14 Goetz Goerisch Note Added: 0014597
2021-08-10 07:50 Bernd Fiebiger Status assigned => resolved
2021-08-10 07:50 Bernd Fiebiger Resolution open => fixed
2021-08-10 07:50 Bernd Fiebiger Note Added: 0014718
2021-08-10 07:51 Bernd Fiebiger Note Edited: 0014718
2021-08-12 06:02 Suprateek Banerjee Project 40010: Robotics => 40010-1: Robotics-1: Vertical integration