Difference between revisions of "What's new in QuickOPC 2022.2"
Jump to navigation
Jump to search
| Line 30: | Line 30: | ||
* With MQTT transport protocol mapping, it is no longer necessary to specify whether UADP or JSON will be used as message mapping. QuickOPC will automatically recognize the message mapping, and is able to receive both UADP and JSON messages on the same connection. For more information, see [[OPC UA PubSub Automatic Message Mapping Recognition]] and [[OPC UA PubSub Transport Profiles]]. | * With MQTT transport protocol mapping, it is no longer necessary to specify whether UADP or JSON will be used as message mapping. QuickOPC will automatically recognize the message mapping, and is able to receive both UADP and JSON messages on the same connection. For more information, see [[OPC UA PubSub Automatic Message Mapping Recognition]] and [[OPC UA PubSub Transport Profiles]]. | ||
* The JSON message mapping now also accepts transport messages that are (incorrectly) formatted as an array of network messages, in order to better cope with buggy publishers. | * The JSON message mapping now also accepts transport messages that are (incorrectly) formatted as an array of network messages, in order to better cope with buggy publishers. | ||
| + | * Added {{Style=Identifier|MessageMappingName}} property to the {{Style=Identifier|UADataSetHeader}} class. Contains the name of the message mapping ("Json" or "Uadp"), if known. | ||
* The {{Style=Identifier|UAPublisherId}} and {{Style=Identifier|UADataSetHeader}} classes now implement the {{Style=Identifier|IComparable<>}} interface. | * The {{Style=Identifier|UAPublisherId}} and {{Style=Identifier|UADataSetHeader}} classes now implement the {{Style=Identifier|IComparable<>}} interface. | ||
<!-- | <!-- | ||
| Line 61: | Line 62: | ||
--> | --> | ||
| + | |||
== OpcCmd Utility == | == OpcCmd Utility == | ||
* The table of dataset header counts, displayed at the end of '''uaSubscriber subscribeDataSet''' command execution, is now ordered by publisher Id, writer group dataset writer Id&name, dataset class Id, and origin. | * The table of dataset header counts, displayed at the end of '''uaSubscriber subscribeDataSet''' command execution, is now ordered by publisher Id, writer group dataset writer Id&name, dataset class Id, and origin. | ||
Revision as of 19:03, 23 March 2022
See also: Versions; Previous version: What's new in QuickOPC 2022.1
Internal version number: 5.64
Key changes:
Component Improvements
OPC UA PubSub
- With MQTT transport protocol mapping, it is no longer necessary to specify whether UADP or JSON will be used as message mapping. QuickOPC will automatically recognize the message mapping, and is able to receive both UADP and JSON messages on the same connection. For more information, see OPC UA PubSub Automatic Message Mapping Recognition and OPC UA PubSub Transport Profiles.
- The JSON message mapping now also accepts transport messages that are (incorrectly) formatted as an array of network messages, in order to better cope with buggy publishers.
- Added MessageMappingName property to the UADataSetHeader class. Contains the name of the message mapping ("Json" or "Uadp"), if known.
- The UAPublisherId and UADataSetHeader classes now implement the IComparable<> interface.
OpcCmd Utility
- The table of dataset header counts, displayed at the end of uaSubscriber subscribeDataSet command execution, is now ordered by publisher Id, writer group dataset writer Id&name, dataset class Id, and origin.
- Added --distinctHeadersOnly|-dho option to the uaSubscriber subscribeDataSet command. The options changes the command output so that only dataset header information is displayed, and only when a dataset with a new, distinct header is received. With this option, you can easily collect information about "who is publishing" over a period of time.
