View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000195910000-004: Servicespublic2012-03-28 19:102012-04-23 15:37
ReporterNathan PocockAssigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0001959: 5.10.2.4 StatusCodes (Read) - Bad_DataEncodingInvalid vs. Bad_DataEncodingUnsupported
Description

As a Server, how would I distinguish the difference between an encoding request that is unsupported versus one that is invalid?

Encodings are requested via a QualifiedName so there's a namespaceIndex and a name.

How can the server distinguish from the qualified name that a request is invalid vs. unsupported.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2012-04-03 17:44

administrator   ~0003465

Ask Randy for clarification on this.

Matthias Damm

2012-04-10 21:03

developer   ~0003503

Added the following clarifications

Bad_DataEncodingInvalid
This result is used if no dataEncoding can be applied because another Attribute than Value was requested or the DataType of the Value Attribute is not a subtype of the Structure DataType.

Bad_DataEncodingUnsupported
This result is used if a dataEncoding can be applied but the passed data encoding is not known to the Server.

Added in document "OPC UA Part 4 - Services RC 1.02.15 Specification.doc"

Jim Luth

2012-04-23 15:37

administrator   ~0003600

Made final edits in meeting and agreed to changes.

Issue History

Date Modified Username Field Change
2012-03-28 19:10 Nathan Pocock New Issue
2012-04-03 17:44 Jim Luth Note Added: 0003465
2012-04-03 17:44 Jim Luth Status new => assigned
2012-04-03 17:44 Jim Luth Assigned To => Matthias Damm
2012-04-10 21:03 Matthias Damm Status assigned => resolved
2012-04-10 21:03 Matthias Damm Resolution open => fixed
2012-04-10 21:03 Matthias Damm Note Added: 0003503
2012-04-23 15:37 Jim Luth Status resolved => closed
2012-04-23 15:37 Jim Luth Note Added: 0003600
2012-04-23 15:37 Jim Luth Fixed in Version => 1.02