View Issue Details

IDProjectCategoryView StatusLast Update
0010054CTT UA Test Case1 - Script Issuepublic2025-07-03 15:16
ReporterParker Mackenzie Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionno change required 
Product Version1.04.11.504 
Summary0010054: Base Information - Base Info Type System - ReferenceTypesValidation.js
Description

ReferenceTypesValidation.js consistently fails with the following error:
IsAbstract=Y; Symmetric=Y; so inverseName should be unavailable, but it is.NodeId: i=31;Browse Path: ReferenceTypes;UA Part 3 section 5.3.2

Steps To Reproduce

Run the test against the OPC Reference Server

Additional Information

Environment:
CTT: v1.04.11-01.00.508.exe-20240608
Reference Server: 1_4_371_96

The fails when run directly against the OPC-UA Reference Server. Analysis of the network communication shows that a read of the attributes associated with the References Node complies with specification; however, the test case interprets a read result indicating that it does not have a value as a valid value but null.

Summary of network analysis:
CTT-->REF 08:25:32.931 ReadRequest RequestHandle:29 NodesToRead:{ArraySize:22
[7]:{NodeId:31, AttributeId:IsAbstract}
[8]:{NodeId:31, AttributeId:Symmetric}
[9]:{NodeId:31, AttributeId:InverseName}}
CTT<--REF 08:25:32.932 ReadResponse RequestHandle:29 Results:{ArraySize:22
[7]:DataValue {HasValue:True, Variant:Type Boolean, Boolean:True}
[8]:DataValue {HasValue:True, Variant:Type Boolean, Boolean:True}
[9]:DataValue {HasValue:False}}

This complies with 1.04 Part 3 Section 5.3.2 of the specification : "If the ReferenceType is non-symmetric and not abstract, the InverseName Attribute shall be
set. "

TagsNo tags attached.
Attached Files
image.png (1,980 bytes)   
image.png (1,980 bytes)   
image-2.png (8,086 bytes)   
image-2.png (8,086 bytes)   
image-3.png (14,395 bytes)   
image-3.png (14,395 bytes)   
Files Affected

Activities

Sebastian Allmendinger

2025-06-25 09:20

developer   ~0023031

Just as an information what is currently expected by the test script:
"Bad_AttributeIdInvalid" for the InverseName and not a null value (value field set to false in the DataValue structure) because the attribute is treated as not supported for this node.

Paul Hunkar

2025-07-03 15:16

administrator   ~0023073

The specification clearly states that a "If a ReferenceType is symmetric, the InverseName Attribute shall be omitted." (see part 3 Attributes of reference types). This mean that the attribute is invalid (Bad_AttributeIdInvalid), not that the Attribute can be null.

Issue History

Date Modified Username Field Change
2024-12-04 14:35 Parker Mackenzie New Issue
2024-12-04 14:35 Parker Mackenzie File Added: image.png
2024-12-04 14:35 Parker Mackenzie File Added: image-2.png
2024-12-04 14:35 Parker Mackenzie File Added: image-3.png
2025-06-25 09:20 Sebastian Allmendinger Note Added: 0023031
2025-07-03 15:16 Paul Hunkar Assigned To => Paul Hunkar
2025-07-03 15:16 Paul Hunkar Status new => resolved
2025-07-03 15:16 Paul Hunkar Resolution open => no change required
2025-07-03 15:16 Paul Hunkar Note Added: 0023073