View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000094110000-008: Data Accesspublic2010-01-15 17:092010-02-16 18:57
ReporterNathan PocockAssigned ToKarl Deiretsbacher  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0000941: PercentDeadband acceptable input for deadband value (0-100)
Description

A potential interoperability problem exists with regards Server behavior for the acceptable input of a PercentDeadband deadband value. For example, what is the "correct" behavior if a Client requested a deadband value of:

125%

While there are convincing arguments both FOR and AGAINST this value, the problem is that the spec does not acknowledge/address this problem currently.

The suggestion here is to revise the description of the PercentDeadband to say that the ONLY acceptable deadband value is any numeric value where the value is:

=0 && <=100

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

user2

2010-01-19 17:59

  ~0001494

Agreed to clarify. Need to decide on a specific error when a client requests a value outside the allowed range.

Karl Deiretsbacher

2010-01-22 09:42

developer   ~0001501

The range of the Deadband is from 0.0 to 100.0 Percent.
Values outside this range will be rejected with Bad_InvalidArgument.

Karl Deiretsbacher

2010-01-22 09:46

developer   ~0001502

Clarified that Deadband values can be between 0.0 and 100.0.
Values outside this range will be rejected with Bad_InvalidArgument.

Fixed in version : OPC UA Part 8 - Data Access Draft 1.02.doc

user2

2010-02-16 18:57

  ~0001548

Last edited: 2010-02-17 13:40

Reviewed and agreed, but changed the associated error code. Final edits will be in 1.02.03

Issue History

Date Modified Username Field Change
2010-01-15 17:09 Nathan Pocock New Issue
2010-01-19 17:59 user2 Note Added: 0001494
2010-01-19 17:59 user2 Status new => assigned
2010-01-19 17:59 user2 Assigned To => Karl Deiretsbacher
2010-01-22 09:42 Karl Deiretsbacher Note Added: 0001501
2010-01-22 09:46 Karl Deiretsbacher Status assigned => resolved
2010-01-22 09:46 Karl Deiretsbacher Fixed in Version => 1.02
2010-01-22 09:46 Karl Deiretsbacher Resolution open => fixed
2010-01-22 09:46 Karl Deiretsbacher Note Added: 0001502
2010-02-16 18:57 user2 Status resolved => closed
2010-02-16 18:57 user2 Note Added: 0001548
2010-02-17 13:40 user2 Note Edited: 0001548