What's new in QuickOPC 2018.1: Difference between revisions
From OPC Labs Knowledge Base
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
* 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. | * 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. | ||
* All callbacks (including event notifications) originating from the {{Style=Identifier|EasyUAClient}} object are now (by default) sent in a queued manner by a dedicated internal thread, improving resiliency against errors in custom code, and decreasing the possibility of deadlocks. This is similar to what the components for OPC "Classic" were already doing, although the internal implementation is different. This behavior can be turned on or off by the {{Style=Identifier|QueueCallbacks}} property. The idle time before the internal thread executing the queued callbacks is stopped is controlled by the {{Style=Identifier|CallbackQueueIdleTimeToSleep}} property, and the capacity of the callback queue is given by the {{Style=Identifier|CallbackQueueCapacity}} property. | * All callbacks (including event notifications) originating from the {{Style=Identifier|EasyUAClient}} object are now (by default) sent in a queued manner by a dedicated internal thread, improving resiliency against errors in custom code, and decreasing the possibility of deadlocks. This is similar to what the components for OPC "Classic" were already doing, although the internal implementation is different. This behavior can be turned on or off by the {{Style=Identifier|QueueCallbacks}} property. The idle time before the internal thread executing the queued callbacks is stopped is controlled by the {{Style=Identifier|CallbackQueueIdleTimeToSleep}} property, and the capacity of the callback queue is given by the {{Style=Identifier|CallbackQueueCapacity}} property. | ||
== Component Refactorings == | |||
* The {{Style=Identifier|IEasyUAClient}}.{{Style=Identifier|BrowseNodes}} method has been renamed to {{Style=Identifier|Browse}}. | |||
== User Interface == | == User Interface == | ||
Revision as of 18:29, 21 December 2017
See also: Versions; Previous version: What's new in QuickOPC 2017.2
Internal version number: 5.52
Key changes:
OPC Compliance Certification
- In accordance with the fact that version 2017.1 has been re-certified by OPC Foundation Certification Testing Laboratory for OPC UA compliance (by the means of its Connectivity Explorer tool), the billboard in the standalone installer has been updated to reflect the certification status.
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.
- All callbacks (including event notifications) originating from the EasyUAClient object are now (by default) sent in a queued manner by a dedicated internal thread, improving resiliency against errors in custom code, and decreasing the possibility of deadlocks. This is similar to what the components for OPC "Classic" were already doing, although the internal implementation is different. This behavior can be turned on or off by the QueueCallbacks property. The idle time before the internal thread executing the queued callbacks is stopped is controlled by the CallbackQueueIdleTimeToSleep property, and the capacity of the callback queue is given by the CallbackQueueCapacity property.
Component Refactorings
- The IEasyUAClient.BrowseNodes method has been renamed to Browse.
User Interface
- In browsing dialogs and controls that contain the node information pane, the user can now show or hide the pane using the "Node information pane" command on the new Layout drop-down on the toolbar.
- Browsing dialogs that allow multi-selection now show in the status bar the numbers of branches and leaves currently present in the list view.
- The toolstrip buttons now show their associated shortcut key combination in their tooltips.
- Gained more useful screen space in OpcBrowseControl, OpcBrowseDialog, UABrowseControl, UABrowseDialog, in "Browse for Point" dialog, and in Connectivity Explorer (Point Editor) by rearranging control (status bar information moved to the right of the toolbar, and mini-controls over the tree view and list view replaced by context menu items and a Layout drop-down).
Excel Real Time Data
- The name of connectivity configuration file has been changed from ConnectivityConfiguration.xml to ConnectivityConfiguration2.xml, and its format has changed.
Tools
Connectivity Explorer
- The "Any Computer" and "Any Host" nodes have been removed. Is is now possible to add OPC servers and OPC-UA endpoints directly under the "roots" for the OPC-DA and OPC-UA connectivity.
- Added special "command nodes" invoked by double clicking on them. "Add Computer" and "Add Server" command nodes have been added under OPC-DA connectivity node, and "Add OPC-UA Endpoint" and "Add Host" have been added under OPC-UA connectivity node.
- The name of connectivity configuration file has been changed from ConnectivityConfiguration.xml to ConnectivityConfiguration2.xml, and its format has changed.
