View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005648Compliance Test Tool (CTT) Unified Architecture5 - General Problempublic2020-05-14 11:462020-06-03 17:23
ReporterMatti Siponen Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.04.09.394 
Fixed in Version1.03.341.396 
Summary0005648: Monitor MinQueueSize_02 / 009.js and Subscription Basic / 040.js incompatibility with Enumeration DataType
Description

Monitored Item Services / Monitor MinQueueSize_02 / 009.js writes multiple Values to MonitoredItems expecting this to activate Overflow bit in DataChange Notifications. Similarly, Subscription Services / Subscription Basic / 040.js writes Values to MonitoredItems expecting this to generate DataChange Notifications.

However, when tested with Enumeration DataType, these test scripts write a WriteValue without a Value multiple times to the Node with Enumeration DataType, which will not cause the Overflow bit to be activated or generate DataChange Notifications for this MonitoredItem, which these tests scripts interpret as errors.

TagsNo tags attached.
Files Affected

Activities

Alexander Allmendinger

2020-06-02 13:28

developer   ~0012154

Problem was caused because an instance of the Enumeration DataType was configured, but the CTT expects to have a Subtype of the Enumeration DataType configured. After updating the vendors server config the test works as intended.
Anyway, in order to be more precise the text for the CTT setting has been updated to:

The NodeId of a Node of a subtype of the type: ENUMERATION Access: Read/Write
Note: Configuring direct instances of the abstract Enumeration DataType will cause scripts to fail.

Paul Hunkar

2020-06-03 17:22

administrator   ~0012169

No scripts required fixing but the configuration screen needed updated text.

Paul Hunkar

2020-06-03 17:23

administrator   ~0012170

reviewed in CMP - changed status to indicate that no script fix as needed, but a documentation change was triggered (configuration screen)

Issue History

Date Modified Username Field Change
2020-05-14 11:46 Matti Siponen New Issue
2020-05-15 17:45 Paul Hunkar Assigned To => Alexander Allmendinger
2020-05-15 17:45 Paul Hunkar Status new => assigned
2020-06-02 13:28 Alexander Allmendinger Status assigned => resolved
2020-06-02 13:28 Alexander Allmendinger Resolution open => no change required
2020-06-02 13:28 Alexander Allmendinger Fixed in Version => 1.03.341.396
2020-06-02 13:28 Alexander Allmendinger Note Added: 0012154
2020-06-03 17:22 Paul Hunkar Resolution no change required => fixed
2020-06-03 17:22 Paul Hunkar Category 1 - Script Issue => 5 - General Problem
2020-06-03 17:22 Paul Hunkar Note Added: 0012169
2020-06-03 17:23 Paul Hunkar Status resolved => closed
2020-06-03 17:23 Paul Hunkar Note Added: 0012170