0010379: Init for the History Read Raw CUs tries to read data from "start of time"

ID	Project	Category	View Status	Date Submitted	Last Update

0010379	Compliance Test Tool (CTT) Unified Architecture	1 - Script Issue	public	2025-06-23 10:58	2025-06-23 13:32

Reporter	Matthew Bowden	Assigned To	Sebastian Allmendinger
Priority	high	Severity	major	Reproducibility	always
Status	assigned	Resolution	open
Platform	PC	OS	Windows Server 2022 Standard	OS Version	21H2
Product Version	1.04.11-01.00.508

Summary	0010379: Init for the History Read Raw CUs tries to read data from "start of time"
Description	When running CUs "History/Historical Access Read Raw" the initialisation routine tries to read data starting at "1601-01-01" (e.g. a default null start time) This is out of range for our OPC UA Server which rejects the read request. As a result no data is read and the subsequent tests find no data. If I update our server code to map an early start date to a more reasonable one (start of year 2000 being the earliest user data we would expect to see) the CTT reports "HistoryRead() status: BadEncodingLimitsExceeded. See attached screenshot.
Steps To Reproduce	Run the CUs!
Tags	No tags attached.
Attached Files	image.png (58,619 bytes) image.png (58,619 bytes)

Files Affected

Date Modified	Username	Field	Change
2025-06-23 10:58	Matthew Bowden	New Issue
2025-06-23 10:58	Matthew Bowden	File Added: image.png
2025-06-23 12:59	Paul Hunkar	Assigned To	=> Sebastian Allmendinger
2025-06-23 12:59	Paul Hunkar	Status	new => assigned
2025-06-23 13:32	Paul Hunkar	Note Added: 0023025

Paul Hunkar 2025-06-23 13:32 administrator ~0023025	After discussion it was determined that there should be a configuration entry in the CTT for "Beginning of History" (time stamp) This will allow the test to have knowledge of when history start in the device under test The script would be updated to use this configuraiton setting