View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008655CTT UA Scripts1 - Script Issuepublic2023-01-26 17:352024-01-20 20:07
ReporterPaul Hunkar Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0008655: Base Info Core Structure/001.js is now too strict
Description

Observed with Compliance Test Tool V1.04.11-01.00.501

Base Info Core Structure/001.js reports missing nodes, when Fully Exposed Type System is not checked
e.g. OperationLimitType -> MaxNodesPerHistoryReadData ==> [NOT FOUND] REQUIRED

But also when the Fully Exposed Type System is available, e.g. because of Embedded Server Profile,
the test fails, because our server implements the Node Set Version 1.04.9, and some additional nodes would be available in 1.04.11,

Note: we have a variable ns=0:i=15959
OpcUaId_OPCUANamespaceMetadata_NamespaceVersion
which could be read, and which should return the string "1.04.9"
Our expectation would be that the script gives only some kind of warnig for items that were added in later versions.

TagsNo tags attached.
Files Affected

Relationships

related to 0008463 closedAlexander Allmendinger CTT UA Test Case Base Info Core Structure/001.js is now too strict 

Activities

Bernd Edlinger

2023-01-26 17:35

reporter   ~0018597

Note: If the Fully Exüpsed type system is selected there is an additioinal message, probably related to the nodeset version:

Error: Unable to find the TypeDefinition for 'i=24148' in the TypeSystem of the Server even though the 'Server Test/Fully Exposed Type System' is set.

Paul Hunkar

2023-01-26 17:35

administrator   ~0018598

In CMP Call - discussed this issue - need to add a test case that is run early - that checks the Nodeset version vs what the test is using designed for - generating an error is the CTT namespace version is newer then what the server is exposing in the NamespaceVersion - indicating that there is a miss match and that error might result.

Christoffer Lind

2024-01-18 13:10

reporter   ~0020657

What happened to the first part of this issue?

"Base Info Core Structure/001.js reports missing nodes, when Fully Exposed Type System is not checked
e.g. OperationLimitType -> MaxNodesPerHistoryReadData ==> [NOT FOUND] REQUIRED"

Is there a plan to resolve this or is it not considered an issue?

Alexander Allmendinger

2024-01-20 20:07

developer   ~0020668

The first part of the issue sounds like an issue in the server application.
Types are not allowed to omit elements, no matter whether they are mandatory or optional. The types are always required to follow 100% the definition of the specification.

Issue History

Date Modified Username Field Change
2023-01-26 17:35 Paul Hunkar New Issue
2023-01-26 17:35 Paul Hunkar Issue generated from: 0008463
2023-01-26 17:35 Paul Hunkar Note Added: 0018597
2023-01-26 17:35 Paul Hunkar Note Added: 0018598
2023-01-26 17:35 Paul Hunkar Relationship added related to 0008463
2023-01-26 17:35 Paul Hunkar Project Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts
2023-01-26 17:37 Paul Hunkar Assigned To => Alexander Allmendinger
2023-01-26 17:37 Paul Hunkar Status new => assigned
2024-01-18 13:10 Christoffer Lind Note Added: 0020657
2024-01-20 20:07 Alexander Allmendinger Note Added: 0020668