What's new in QuickOPC 2022.2: Difference between revisions
From OPC Labs Knowledge Base
| Line 29: | Line 29: | ||
== OPC UA PubSub == | == 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]]. | * 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. | |||
<!-- | <!-- | ||
== COM Components == | == COM Components == | ||
Revision as of 12:30, 22 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.
