View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000845210000-004: ServicesSpecpublic2022-11-21 14:412023-02-21 16:29
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.01 
Target Version1.05.03 RC1Fixed in Version1.05.03 RC1 
Summary0008452: TimestampsToReturn related status codes for HistoryRead inconsistent
Description

Part 4:

Table 56 – HistoryRead Service Parameters
timestampsToReturn
Specifying a TimestampsToReturn of NEITHER is not valid. A Server shall return a Bad_InvalidTimestampArgument StatusCode in this case.
OPC 10000-11 defines exceptions where this parameter shall be ignored.

Table 57 – HistoryRead Service Result Codes
Only Bad_TimestampsToReturnInvalid is listed as Service Result Code

Table 58 – HistoryRead Operation Level Result Codes
Bad_InvalidTimestampArgument is listed as operation level code

Part 11:

4.3 Timestamps
A HistoryRead with invalid settings will be rejected with
Bad_TimestampsToReturnInvalid (see OPC 10000-4).

Additional Information

Only Bad_TimestampsToReturnInvalid is listed as service level code and it is also the only status code that is referenced in Part 11.

Bad_InvalidTimestampArgument is listed as operation level code but it is not clear where it is used since all error scenarios described in Part 11 refer to Bad_TimestampsToReturnInvalid.

There is one possible operation level error scenario described in Part 11 but this case also refers to Bad_TimestampsToReturnInvalid.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008453 closedPaul Hunkar 10000-011: Historical Access Timestamps related error handling needs clarification 
related to 0008675 assignedPaul Hunkar Compliance Test Tool (CTT) Unified Architecture Historical Read raw, timestampsToReturn Neither, must return Bad_InvalidTimestampArgument at service level 

Activities

Jim Luth

2022-11-22 17:13

administrator   ~0018179

Assigned to Paul to fix first so Part 11 and Part 4 are consistent.

Paul Hunkar

2023-02-16 03:46

developer   ~0018722

Part 11 has been fixed (see related issue)

"Table 56 – HistoryRead Service Parameters
timestampsToReturn
Specifying a TimestampsToReturn of NEITHER is not valid. A Server shall return a Bad_InvalidTimestampArgument StatusCode in this case.
OPC 10000-11 defines exceptions where this parameter shall be ignored"

The error code should be changed to Bad_TimestampsToReturnInvalid (it is in table 57 which is correct)

Bad_ TimestampNotSupported - should be added to the Operation Level results (table 58) and also to service level results (table 57) - since this can be returned as either at the service level or operation level - it is explained in part 11, but return if server timestamp requested but only source supported

.

Matthias Damm

2023-02-20 21:15

developer   ~0018774

Change status code in Table 56 from Bad_InvalidTimestampArgument to Bad_TimestampsToReturnInvalid

Table 56 – HistoryRead Service Parameters
timestampsToReturn
Specifying a TimestampsToReturn of NEITHER is not valid. A Server shall return a Bad_TimestampsToReturnInvalid StatusCode in this case.
OPC 10000-11 defines exceptions where this parameter shall be ignored.

Jim Luth

2023-02-21 16:29

administrator   ~0018787

Agreed to changes edited in telecon.

Issue History

Date Modified Username Field Change
2022-11-21 14:41 Matthias Damm New Issue
2022-11-21 14:48 Matthias Damm Relationship added related to 0008453
2022-11-22 17:13 Jim Luth Note Added: 0018179
2022-11-22 17:13 Jim Luth Assigned To => Paul Hunkar
2022-11-22 17:13 Jim Luth Status new => assigned
2023-02-15 16:46 Paul Hunkar Assigned To Paul Hunkar => Matthias Damm
2023-02-16 03:46 Paul Hunkar Note Added: 0018722
2023-02-20 21:15 Matthias Damm Status assigned => resolved
2023-02-20 21:15 Matthias Damm Resolution open => fixed
2023-02-20 21:15 Matthias Damm Note Added: 0018774
2023-02-20 21:16 Matthias Damm Relationship added related to 0008675
2023-02-21 16:29 Jim Luth Status resolved => closed
2023-02-21 16:29 Jim Luth Fixed in Version => 1.05.03 RC1
2023-02-21 16:29 Jim Luth Note Added: 0018787