What's new in QuickOPC 2018.1: Difference between revisions
From OPC Labs Knowledge Base
(→Component Improvements: style) |
|||
| Line 10: | Line 10: | ||
<br> | <br> | ||
== Component Improvements == | == Component Improvements == | ||
* When {{Style=Identifier|EasyUAClient}} receives an OPC UA extension object that it does not recognize, it now returns it (in reads and subscriptions) as an instance of new {{Style=Identifier|UAExtensionObject}} class. This class allows access to the extension object's body (binary or XML), and its data type encoding ID. Conversely, {{Style=Identifier|UAExtensionObject}} instance can be passed in as a value to be written. | * When {{Style=Identifier|EasyUAClient}} receives an OPC UA extension object that it does not recognize, it now returns it (in reads and subscriptions) as an instance of new {{Style=Identifier|UAExtensionObject}} class. This class allows access to the extension object's body (binary or XML), and its data type encoding ID. Conversely, {{Style=Identifier|UAExtensionObject}} instance can be passed in as a value to be written. This feature establishes basic support for OPC UA complex data types. | ||
<br> | <br> | ||
Revision as of 09:40, 11 November 2017
See also: Versions; Previous version: What's new in QuickOPC 2017.2
Internal version number: 5.52
Key changes:
Component Improvements
- When EasyUAClient receives an OPC UA extension object that it does not recognize, it now returns it (in reads and subscriptions) as an instance of new UAExtensionObject class. This class allows access to the extension object's body (binary or XML), and its data type encoding ID. Conversely, UAExtensionObject instance can be passed in as a value to be written. This feature establishes basic support for OPC UA complex data types.
