View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000089110000-004: Servicespublic2009-10-08 19:502012-02-09 22:33
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0000891: Enhance description of error "Bad_IndexRangeInvalid"
Description

In table 0000166 on page 146 is the following description for error "Bad_IndexRangeInvalid":

"The syntax of the index range parameter is invalid."

The Compliance Working Group has determined that this particular error return code could be used when specifying an IndexRange on a type that is NOT an array, i.e. bool, int16 etc.

The description might be changed to something like this proposal:

"The syntax of the index range parameter is invalid, or is invalid for the Type of the node it is being used with".

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

user2

2010-01-12 18:55

  ~0001484

Last edited: 2010-01-12 18:55

Agreed that clarification is necessary, but rejected the proposed change.

Bad_IndexRangeInvalid is only used for invalid syntax. All other invalid index range requests with a valid syntax shall result in Bad_IndexRangeNoData.

The clarificaiton should go the the numeric range definition.

Matthias Damm

2011-03-13 21:17

developer   ~0002396

Added clarificaiton that Bad_IndexRangeInvalid is only used for invalid syntax. All other invalid index range requests with a valid syntax shall result in Bad_IndexRangeNoData.

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

Randy Armstrong

2011-03-23 06:22

administrator   ~0002517

Reviewed in telco on March 23, 2011
The final changes are included in the document revision OPC UA Part 4 - Services 1.02.04 Draft.doc

Issue History

Date Modified Username Field Change
2009-10-08 19:50 Nathan Pocock New Issue
2010-01-12 18:55 user2 Note Added: 0001484
2010-01-12 18:55 user2 Note Edited: 0001484
2010-01-12 18:56 user2 Status new => assigned
2010-01-12 18:56 user2 Assigned To => Matthias Damm
2011-03-13 21:17 Matthias Damm Status assigned => resolved
2011-03-13 21:17 Matthias Damm Resolution open => fixed
2011-03-13 21:17 Matthias Damm Note Added: 0002396
2011-03-23 06:22 Randy Armstrong Status resolved => closed
2011-03-23 06:22 Randy Armstrong Note Added: 0002517
2012-02-09 22:33 Jim Luth Fixed in Version => 1.02