View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005052Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2019-09-18 11:342020-04-17 15:45
ReporterMarvin Schmidt Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.03.341.389 
Summary0005052: ProgramStateMachineType component 'ProgramDiagnostic' is declared optional by spec but required in test
Description

In a project created with version 1.03.341.390 of CTT the expectation for the 'ProgramDiagnostic' component
in "library\Information\NodeSet2.xml\UaNodeSetFileV103.js" sets the "Required" attribute to "true" although
version 1.04 of the specification states that it's optional (Part 10, section 5.2.1, table 5)

I stumbled upon this because the test
Base Information/Base Info Core Structure/001.js
failed due problem described in Issue 4736

TagsNo tags attached.
Files Affected

Relationships

duplicate of 0004736 closedAlexander Allmendinger ProgramDiagnostics has been changed to ProgramDiagnostic 

Activities

Paul Hunkar

2019-09-27 14:55

administrator   ~0011020

This should be updated to be optional

Bernd Edlinger

2019-09-30 09:26

reporter   ~0011025

Coincidentally the following commit in the UA-Nodeset
git https://github.com/OPCFoundation/UA-Nodeset

commit 8160a5bdad46462e4ad440a0ffd5eb6a5f5fdbc5
Author: Randy Armstrong <git@opcfoundation.org>
Date: Mon Nov 26 14:22:01 2018 -0800

Fixed various mantis issues.

changed the name of ProgramStateMachineType::ProgramDiagnostic(s):
-#define OpcUaId_ProgramStateMachineType_ProgramDiagnostics 2399
+#define OpcUaId_ProgramStateMachineType_ProgramDiagnostic 2399

So the test fails if the new name is used, but succeeds when the old name is used.

Alexander Allmendinger

2020-02-14 14:14

developer   ~0011610

The "required"-attribute does indicate whether a field is required in the type system. Whether a field is optional or required in an instance of the type is being defined in the ModellingRule, which in this case already is correctly set to "Optional"

Paul Hunkar

2020-04-17 15:45

administrator   ~0011943

reviewed in CMP meeting

Issue History

Date Modified Username Field Change
2019-09-18 11:34 Marvin Schmidt New Issue
2019-09-27 14:55 Paul Hunkar Assigned To => Alexander Allmendinger
2019-09-27 14:55 Paul Hunkar Status new => assigned
2019-09-27 14:55 Paul Hunkar Note Added: 0011020
2019-09-30 09:26 Bernd Edlinger Note Added: 0011025
2019-11-14 16:16 Paul Hunkar Relationship added duplicate of 0004736
2020-02-14 14:14 Alexander Allmendinger Status assigned => resolved
2020-02-14 14:14 Alexander Allmendinger Resolution open => no change required
2020-02-14 14:14 Alexander Allmendinger Note Added: 0011610
2020-04-17 15:45 Paul Hunkar Status resolved => closed
2020-04-17 15:45 Paul Hunkar Note Added: 0011943