View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000182510000-004: Servicespublic2012-01-06 20:052012-01-17 18:33
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Summary0001825: Table 122 - DataValue: Bad StatusCode should mean to NOT use the Value?
Description

In mantis 0001400 the solution was to state (in DataChangeNotification) that a client should not use the Value of the StatusCode was Bad. Should that also apply to Table 122 - DataValue? This same rule for ignoring bad values would then apply to Read.

(OPC UA Part 4 - Services 1.02.09 Draft.doc)

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0001400 closedMatthias Damm Use of timestamp in DataValue for bad status is inconsistent 

Activities

Matthias Damm

2012-01-08 22:45

developer   ~0003144

Both tables contain the same sentence:
Table 122 - DataValue
If the StatusCode indicates an error then the value is to be ignored and the Server shall set it to null.
Table 148 - DataChangeNotification - parameter Value
If the StatusCode indicates an error then the value is to be ignored.

The requested text is already there.

Jim Luth

2012-01-17 18:33

administrator   ~0003208

agreed to no fix in telecon.

Issue History

Date Modified Username Field Change
2012-01-06 20:05 Nathan Pocock New Issue
2012-01-06 20:05 Nathan Pocock Status new => assigned
2012-01-06 20:05 Nathan Pocock Assigned To => Matthias Damm
2012-01-06 20:05 Nathan Pocock Relationship added related to 0001400
2012-01-08 22:45 Matthias Damm Status assigned => resolved
2012-01-08 22:45 Matthias Damm Resolution open => won't fix
2012-01-08 22:45 Matthias Damm Note Added: 0003144
2012-01-17 18:33 Jim Luth Status resolved => closed
2012-01-17 18:33 Jim Luth Note Added: 0003208