Last revision: Monday, November 8, 2021
Our HMI SCADA YouTube channel contains instructional and promotional videos on our various product lines. Please follow the links below:
Platform Connectivity and Device Integration Playlist
https://www.youtube.com/playlist?list=PLJq4rR8tWINwTpCnlHqjUUlysBClU-YqU
HMI SCADA Channel Main Page
https://www.youtube.com/user/wonderwarehmi
You can now access hundreds of training courses that cover simple and complex topics with all the products that you use in our Monitoring and Control portfolio. Access to the eLearning modules is free!
https://sw.aveva.com/training/wonderware
This document contains important information about MQTT Communication Driver. Review this document for known issues and changes to MQTT.
Message Queuing Telemetry Transport (MQTT), is a publish/subscribe messaging protocol for use over TCP/IP. MQTT is designed to ensure that devices can communicate with each other while minimizing power and bandwidth requirements. It is a simple messaging protocol that is well-suited for use with devices that rely on slow or unreliable networks.
The MQTT protocol is an application layer specification, and has been published as standard ISO/IEC 20922. MQTT uses a Publish-Subscribe mechanism which requires a mediating broker.
In this release, as a subscriber, the MQTT Communication Driver will subscribe MQTT payload of Sparkplug, JSON, and/or plain text format. As a publisher, the MQTT Communication Driver will publish data in JSON format.
Note:The MQTT subscriber plug-in within the Gateway Communication Driver has been superseded with this standalone MQTT Communication Driver. The MQTT Gateway plug-in will be phased out in the next major release of the Communication Drivers. We recommend you to modify your configuration to start using the new standalone MQTT Communication Driver instead.
Note: You cannot use Gateway or the 2020R2 release of MQTT Communication Drivers to subscribe to the JSON payload published by this release (AVEVA Communication Drivers Pack 2020.3) of MQTT Communication Driver. To subscribe MQTT payload published by this release of MQTT Communication Driver, please upgrade the installation of any previous installations of MQTT Communication Driver to this release. MQTT payload published by the Gateway Communication Driver will continue to be recognized by the MQTT Communication Driver.
Introducing MQTT Publisher for publishing Application Server data
The MQTT Communication Driver Publisher enables you to publish data from the Application Server to the MQTT broker. You can publish payloads encoded in JSON format using the MQTT publisher.
OpenSSL 1.1.1l Support
MQTT Communication Driver now uses OpenSSL 1.1.1l for secure communication with the MQTT Broker.
The MQTT Communication Driver will always be compatible with the latest release of System Platform.
For a list of supported operating systems for the communication drivers, refer to the Technology Matrix, available at the Global Customer Support (GCS) Site:
The Technology Matrix is a searchable database that contains the latest product information. Enter the product name in the search bar, then select the release to view:
Product Interoperability/Compatibility: list of products that can operate together and communicate with each other through a common message protocol.
To run a Communication Driver, the following hardware configurations are the minimum recommended:
Note: For every additional 5 connections (Up to 10,000 I/O @ 1000 ms each), add 1 GB RAM and 1 Cores.
There are no new resolved issues in this release of MQTT Communication Driver.
Following are known issues in this release.
Defect ID |
SR/Case Number |
Description |
IMS-1512234
|
(Internal) |
Issue: "HTTP Error 503. The service is unavailable" after changing to SMS or pointing to another SMS Node Work-around: Restart the AVEVA Communications Backend Service in the Services console of your machine. If you make any changes to the configuration of the System Management Server (SMS), you must restart the AVEVA Communications Backend Service in the Services console of your machine. In the Advanced Configuration of the System Management Server (SMS), if you change the HTTP Port or the HTTPS Port then you must run the following command as an administrator in the command prompt: If you change the HTTP Port field netsh http add urlacl url=http://localhost:<http port configured in SMS>/oi/ user="NT SERVICE\GDIWebServer" If you change the HTTPS Port field netsh http add urlacl url=https://localhost:<https port configured in SMS>/oi/ user="NT SERVICE\GDIWebServer" If you do not run the above commands after changing the ports and try to access the MQTT browser or the MQTT publisher functionality, you will get an HTTP 503 error saying the service is unavailable. |
IMS-1582911 |
(Internal) |
Issue: If you add a new broker hierarchy followed by a publisher hierarchy in the SMC while the MQTT Communication Driver is running, a red line may show up in the logger "MQTT Publishing is stopped -- unable to load configuration from GDIDB with key OI.MQTT_{..... } due to invalid configuration". Work-around: If the MQTT Communication Driver is running when you are adding a broker hierarchy, click the Save icon before creating the publisher hierarchy. |
The MQTT Communication Driver documentation set includes the following guides. These documents can be accessed from the Help menu in the SMC.
Note: The AVEVA Enterprise License Manager Help can be accessed through the License Manager application (available only for the new license framework). For earlier versions of the license framework, see License Utility Guide.
|
© 2021 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |