View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000180610000-004: Servicespublic2011-12-03 02:062012-02-09 22:48
ReporterToshio Ono Assigned ToMatthias Damm  
PrioritynormalSeveritytextReproducibilityalways
Status closedResolutionfixed 
Product Version1.01 
Fixed in Version1.02 
Summary0001806: Description of Bad_TypeMismatch isn't clear
Description

The document describes cause of the error as the following.

A Server shall return a Bad_TypeMismatch error if the data type of value is not the same as or a subtype of datatype for the Attribute.
<<<

The "subtype" on the bullet should be defined clearly to ensure interoperability.

OPC Classic(DA) defines similar error and defines valid combination of data types for data conversion. Please look at "4.2.12 VARIANT Data Types and Interoperability" in DA3.0.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0001852 closedNathan Pocock Compliance Test Tool (CTT) Unified Architecture Description of Bad_TypeMismatch isn't clear 

Activities

Matthias Damm

2012-01-09 22:19

developer   ~0003151

Updated Text
(a) Synchronized with description in Table 166
(b) Added clarification for value attribute
(c) Added clarification for subtype

New Text:
A Server shall return a Bad_TypeMismatch error if the data type of the written value is not the same type or subtype as the Attribute’s DataType. Based on the DataType hierarchy, subtypes of the Attribute DataType shall be accepted by the Server. For the Value Attribute the DataType is defined through the DataType Attribute.

Changed in document version OPC UA Part 4 - Services 1.02.11 Draft.doc

Jim Luth

2012-01-10 15:01

administrator   ~0003152

Reviewed and closed in Boca meeting.

Issue History

Date Modified Username Field Change
2011-12-03 02:06 Toshio Ono New Issue
2011-12-06 18:15 Matthias Damm Status new => assigned
2011-12-06 18:15 Matthias Damm Assigned To => Matthias Damm
2012-01-09 22:19 Matthias Damm Status assigned => resolved
2012-01-09 22:19 Matthias Damm Resolution open => fixed
2012-01-09 22:19 Matthias Damm Note Added: 0003151
2012-01-10 15:01 Jim Luth Status resolved => closed
2012-01-10 15:01 Jim Luth Note Added: 0003152
2012-01-24 15:14 Jim Luth Issue cloned: 0001852
2012-01-24 15:14 Jim Luth Relationship added related to 0001852
2012-02-09 22:48 Jim Luth Fixed in Version => 1.02