View Issue Details

IDProjectCategoryView StatusLast Update
0003352Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2019-07-25 15:06
ReporterMartin Lang Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Target Version1.03Fixed in Version1.03.341.383 
Summary0003352: Data Access/Data Access AnalogItemType/020.js will be skipped, if no node from 'Byte' until 'UInt64' offers InstrumentRange
Description

used CTT version 1.2.336.256

If within the project settings 'Server Test/NodeIds/DA Profile/Analog Type' the Nodes for 'Byte' until 'UInt64' are not offer the property 'InstrumentRange', the script will be skipped.
This is based on the initialize.js script.
code snippet:
...
// get an array of MonitoredItem objects, these will be used by all scripts in this Conformance Unit
var AnalogItems = MonitoredItem.fromSettings( Settings.ServerTest.NodeIds.Static.DAProfile.AnalogType.NumericSettings );
...

Through the last parameter 'NumericSettings' the project settings 'NodeIdWithEngineeringUnits' and 'NodeIdWithInstrumentRange' will not copied to 'var AnalogItems'.
Based on this script 020.js will be skipped by line 17.
Code Snippet:
...
if( !isDefined( item1 ) ) {
addSkipped( "Unable to find a node of type AnalogItemType featuring an InstrumentRange property, which is an OPTIONAL property." );
return( false );
}
...

Steps To Reproduce
  • configure CTT project as shown in the attached picture
    -> the Nodes from 'Byte' until 'UInt64' should not offer a property 'InstrumentRange'
  • run script 'Data Access/Data Access AnalogItemType/020.js'
Additional Information

Possible fix:
initialize.js, line 18:
Current implementation:
var AnalogItems = MonitoredItem.fromSettings( Settings.ServerTest.NodeIds.Static.DAProfile.AnalogType.NumericSettings );

Fix:
var AnalogItems = MonitoredItem.fromSettings( Settings.ServerTest.NodeIds.Static.DAProfile.AnalogType.Settings );

TagsNo tags attached.
Attached Files
CTT_Setting.png (38,136 bytes)   
CTT_Setting.png (38,136 bytes)   
Files Affected

Activities

Nathan Pocock

2016-08-05 14:29

viewer   ~0007128

I have incorporated the change into source control so the fix will be in the next patch release. Will close issue on release.

Alexander Allmendinger

2018-12-19 09:38

developer   ~0009736

Initialize script is now using .Settings instead of .NumbericSettings

Paul Hunkar

2019-07-25 15:06

administrator   ~0010601

reviewed in CMP call

Issue History

Date Modified Username Field Change
2016-03-02 14:12 Martin Lang New Issue
2016-03-02 14:12 Martin Lang File Added: CTT_Setting.png
2016-08-05 14:29 Nathan Pocock Note Added: 0007128
2016-08-05 14:29 Nathan Pocock Status new => resolved
2016-08-05 14:29 Nathan Pocock Resolution open => fixed
2016-08-05 14:29 Nathan Pocock Assigned To => Nathan Pocock
2018-11-19 20:47 Paul Hunkar Assigned To Nathan Pocock => Alexander Allmendinger
2018-11-19 20:47 Paul Hunkar Status resolved => assigned
2018-12-19 09:38 Alexander Allmendinger Note Added: 0009736
2018-12-19 09:38 Alexander Allmendinger Status assigned => resolved
2018-12-19 09:38 Alexander Allmendinger Fixed in Version => 1.03.341.383
2019-07-25 15:06 Paul Hunkar Category Implementation Bug => 1 - Script Issue
2019-07-25 15:06 Paul Hunkar Target Version => 1.03
2019-07-25 15:06 Paul Hunkar Status resolved => closed
2019-07-25 15:06 Paul Hunkar Note Added: 0010601