Last revision: 11/20/2020
IMPORTANT: If you are upgrading from a previous version, and are using secured OPC UA connections, you must update the trust relationship with the OPC UA server. For more information, see Trusting the Gateway Communication Driver OPC UA Certificates with the OPC UA Server.
Note: The MQTT plug-in within the Gateway has been superseded with a 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 standalone MQTT Communication Driver instead.
Our 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 AVEVA Gateway Communication Driver. Review this document for known issues and changes to Gateway Communication Driver.
Enhanced OPC UA Client
The OPC UA Namespace section of the OPC UA editor now has a new column - Tag Prefix. It helps to specify a common prefix for an item so that it can reduce the item name length when subscribed by the client.
OpenSSL 1.1.1g support for OPCUA
Now OPCUA supports OpenSSL 1.1.1g framework for secure communication.
The Gateway Communication Driver can be installed with AVEVA Communication Drivers Pack 2020 R2, as well as bundled in the installation of the System Platform (SP). You can select the appropriate options install Gateway Communication Driver during SP installation.
Prior to installing a newer version of Gateway Communication Driver on any previous versions of SP, it is recommended to refer to the Technology Matrix section of the Global Customer Support (GCS).
When using a secured connection to the OPC UA Server, the OI Gateway node must be trusted by the OPC UA Server. Follow the steps below to trust the OI Gateway node.
A new OI Gateway OPC UA certificate is automatically copied to the OPC UA Server.
Note:
- If you are upgrading from a version older than 5.2, you must trust the certificate again as explained above.
- Connection to OPCUA server with unencrypted passwords is no longer supported by UA SDK v1.7.0. If User Name and password is configured for connection with OPCUA Server, then the security policy cannot be NONE. You have to configure the appropriate security policy (Basic128Rsa15, Basic256, Basic256Sha256).
The following issues are resolved in this release of Gateway Communication Driver.
Defect ID |
SR/Case Number |
Description |
CR-L00157917 |
SR-63511882 |
MQTT data precision - data changed from 2.4563E + 15 to 2.4563 |
CR-L00157082 CR-L00156996 CR-L00156997 |
SR-63913263
|
Wonderware Sending Buffer data instead of string ( JSON FORMAT)
|
CR-L00158502 |
SR-51316575
|
OI-Gateway did not update active (9) Item after 20-50 min from a local running OPC UA Server. |
CR-L00158899 CR-L00158218 |
- |
OI Gateway 3.0 stopped updating some tag values
|
CR-L00158215 CR-L00157191 |
SR-81810551 |
DEMAND READ and DEMAND WRITE Timing out when one of the connected Topics(PLC) is shutdown. |
CR-L00159843 |
IMS-0001867110 |
Items were not updated correctly. |
The following table lists known issues at the time of release.
Defect ID |
Description |
TFS-1355437 |
If a standalone Gateway Communication Driver (v4.0-v6.0) is installed on a machine and if you try to upgrade the system using System Platform 2020 R2, then the Gateway Communication Driver gets uninstalled. Workaround: Use Modify install option in the System Platform 2020 R2 and select Standards - Gateway to install on the machine. Note:
|
TFS-1360928 |
Gateway Communication Driver OPC Client cannot connect to OPC Server on the remote node when Gateway Communication Driver is running under the SYSTEM account. Workaround: Change Gateway Communication Driver DCOM Identity settings to use a domain administrator account or login machine with a domain administrator account and run Gateway Communication Driver in desktop mode. To change the DCOM settings, follow the below steps:
|
The AVEVA Gateway 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.
© 2020 AVEVA Group plc and its subsidiaries. All rights reserved. | Contact Us |