View Issue Details

IDProjectCategoryView StatusLast Update
000169410000-004: Servicespublic2012-02-09 22:51
ReporterThomas Merk Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.01 
Fixed in Version1.02 
Summary0001694: Inconsitent information regarding TimestampsToReturn
Description

In Part 11 - RC 1.02.03 (chapter 4.3) a sentence was added that the source timestamps are used to determine the values to be returned.

In Part 4 - RC 1.02.05 (chapter 7.34) is still stated that the server timestamps have to be used in case of "SERVER_1".

I assume that the information in Part 4 needs to be updated.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0001720 closedRod Stein 10000-011: Historical Access Inconsitent information regarding TimestampsToReturn 

Activities

Randy Armstrong

2011-08-23 17:44

administrator   ~0002849

Last edited: 2011-08-23 17:55

The text describing HistoryRead behavoir should be removed for Server, Source and Both. Neither is invalid for HistoryRead.

In the HistoryRead service description additional text should say that if Server selected for TimestampsToReturn and the Server does not support Server timestamps then the error should be Bad_TimestampsToReturnInvalid.

If you select Both you get back DateTime.MinValue for Server timestamps if the timestamp is not available.

Matthias Damm

2011-09-06 15:53

developer   ~0002896

Removed HistoryRead behaviour desription in TimestampToReturn description for Server, Source and Both. The behaviour is described in Part 11.

Changed in document version OPC UA Part 4 - Services 1.02.06 Draft.doc

Should we also add text to HistoryRead like described by Randy?

Randy Armstrong

2011-09-06 16:53

administrator   ~0002899

Discussed in telecon.

Issue History

Date Modified Username Field Change
2011-08-03 14:57 Thomas Merk New Issue
2011-08-23 17:44 Randy Armstrong Note Added: 0002849
2011-08-23 17:55 Randy Armstrong Note Edited: 0002849
2011-08-23 17:55 Randy Armstrong Status new => assigned
2011-08-23 17:55 Randy Armstrong Assigned To => Matthias Damm
2011-09-06 15:53 Matthias Damm Status assigned => resolved
2011-09-06 15:53 Matthias Damm Resolution open => fixed
2011-09-06 15:53 Matthias Damm Note Added: 0002896
2011-09-06 16:52 Randy Armstrong Issue cloned: 0001720
2011-09-06 16:52 Randy Armstrong Relationship added related to 0001720
2011-09-06 16:53 Randy Armstrong Status resolved => closed
2011-09-06 16:53 Randy Armstrong Note Added: 0002899
2012-02-09 22:51 Jim Luth Fixed in Version => 1.02