0007946: InputNode: CTT-Tool complains that the InputNode-Field is NULL

ID	Project	Category	View Status	Date Submitted	Last Update

0007946	CTT UA Scripts	1 - Script Issue	public	2022-04-19 10:16	2022-08-25 03:09

Reporter	Hock, Christian	Assigned To	Paul Hunkar
Priority	high	Severity	major	Reproducibility	always
Status	feedback	Resolution	open

Summary	0007946: InputNode: CTT-Tool complains that the InputNode-Field is NULL
Description	InputNode: Part 9 / 5.8.2 AlarmConditionType -> below Table 42 The InputNode Property provides the NodeId of the Variable the Value of which is used as primary input in the calculation of the Alarm state. If this Variable is not in the AddressSpace, a NULL NodeId shall be provided. In some systems, an Alarm may be calculated based on multiple Variables Values; it is up to the system to determine which Variable’s NodeId is used. 1.) If above mentioned Variable is NOT in the AddressSpace still the CTT-Tool complains. 2.) If an already existing underlying alarm system has no knowledge about "which variable(s) fires an alarm/condition" -> how a product can deal with this fact - to be compliant?
Tags	No tags attached.

Files Affected

Date Modified	Username	Field	Change
2022-04-19 10:16	Hock, Christian	New Issue
2022-05-12 16:54	Paul Hunkar	Assigned To	=> Paul Hunkar
2022-05-12 16:54	Paul Hunkar	Status	new => feedback
2022-05-12 16:54	Paul Hunkar	Note Added: 0016709
2022-08-25 03:09	Paul Hunkar	Project	Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts

Paul Hunkar 2022-05-12 16:54 administrator ~0016709	The specification is fairly clear on this topic, if you have a case for alternate behavior then you need to enter a mantis issue on Part 9 (to extend it for alternate behaviors). We don't see any changes in the test based on the current version of the specification (1.05.02)