View Issue Details

IDProjectCategoryView StatusLast Update
000140010000-004: Servicespublic2012-02-09 22:41
ReporterMatthias Damm Assigned ToMatthias Damm  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0001400: Use of timestamp in DataValue for bad status is inconsistent
Description

7.19.2 DataChangeNotification parameter
Table 148 -> value
If the StatusCode indicates an error then the value and timestamp(s) are to be
ignored.

7.7 DataValue
Definition SourceTimestamp / ServerTimestamp:
In the case of a bad or uncertain status, serverTimestamp is used to reflect the time that the Server received the status or that the Server last tried to recover from the bad or uncertain status.

It makes no sense to define a special behaviour for the DataChangeNotification and it makes sense to use at least the server timestamp

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0001825 closedMatthias Damm Table 122 - DataValue: Bad StatusCode should mean to NOT use the Value? 

Activities

Matthias Damm

2011-03-12 14:33

developer   ~0002382

Changed DataValue description regarding timestamps in DataChangeNotification definition to be consistent with DataValue structure definition. The source timestamp is valid for bad or uncertain status.

Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.02 Body.doc"

Randy Armstrong

2011-05-24 08:54

administrator   ~0002758

Discussed in Walldorf

Issue History

Date Modified Username Field Change
2010-10-14 12:42 Matthias Damm New Issue
2011-02-14 06:21 Randy Armstrong Status new => assigned
2011-02-14 06:21 Randy Armstrong Assigned To => Matthias Damm
2011-03-12 14:33 Matthias Damm Status assigned => resolved
2011-03-12 14:33 Matthias Damm Resolution open => fixed
2011-03-12 14:33 Matthias Damm Note Added: 0002382
2011-05-24 08:54 Randy Armstrong Status resolved => closed
2011-05-24 08:54 Randy Armstrong Note Added: 0002758
2012-01-06 20:05 Nathan Pocock Relationship added related to 0001825
2012-02-09 22:41 Jim Luth Fixed in Version => 1.02