AVEVA™ Communication Drivers Pack 2020 R2.1 Readme

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

About This Release

This document contains important information about the Communication Drivers Core. Carefully review this document for known and resolved issues in this version.

This release of the Communication Drivers Core is an upgrade for consumption with latest version of System Platform release.

Third Party/Open Source Software Disclosure

The Communication Drivers Core incorporates Third Party/Open Source Software components whose licenses and copyright notices can be found at the following folder on the target machine:

On 64-bit operating system: \Program Files(x86)\Wonderware\OSSLicense_CommunicationDriversPack.pdf

New in This Release

Security Improvements in SuiteLink

Enhancements added to improve SuiteLink resilience against malformed packets.

Security Improvements in Auto-Build

You can only view the Auto-Build tab from a GR (Application Server) node. You cannot view the Auto-Build tab from a remote node.

Enhanced User Privileges to Access Auto-Build

The user who launches the SMC must be part of the oiAdministrators group to access the Auto-Build functionality. If the user is not a part of the oiAdministrators group, you must add the user to the oiAdministrators group manually, else the user will not be able to view the Auto-Build tab.

Installing AVEVA Communication Drivers

Installation Checklist

Before installing the Communication Drivers Pack, please ensure the following:

Exit all AVEVA (formerly Wonderware) programs, including executable (.exe) files and services
Disconnect/close all third party OPC clients of existing DAServers/OI Servers/Communication Drivers
Deactivate all DAServers/OI Servers/Communication Drivers

It is also recommended to stop the platform where the Communication Drivers Pack will be installed.

Install/Upgrade Procedure

Download AVEVA Communication Drivers Pack 2020 R2.1 from the Connectivity Hub section of the Global Customer Support.

The GCS Connectivity Hub contains the product downloads, documents, and videos.

Note: The downloaded files could be blocked. Since the Windows regards downloaded files as potentially unsafe, it blocks the file from executing after the downloaded. Check your Downloaded Zip or ISO file to ensure that the downloaded file is not blocked. If it is blocked, you must unblock it before extracting.

To Install/Upgrade the AVEVA Communication Drivers Pack

Locate the installer file (Setup.exe) in the AVEVA Communication Drivers Pack 2020 R2.1 installation media. Double-click the Setup.exe file or right-click Setup.exe and select Run as administrator.
Depending on your computer's security settings, the User Account Control may ask for permission to run the installation program. Click Yes to allow it to run. A dialog box with the list of all the products that will be upgraded appears.
Click OK. The License Agreement window appears.
Review the license agreement and agree to the terms stated. Read the License Agreement. If you agree to the stated terms, select the I read and accept the terms of license agreement(s) and click Agree.
If you accept the license agreement, click Next. The Preview Installation window with the list of Communication Drivers appears. You can find the following options to select:
Note: If you are upgrading, the Communication Drivers that are already present will be selected and grayed out. You cannot unselect them. The Core Communication Drivers and the other Communication Drivers that are already present will be upgraded. The previous configuration will be retained after the upgrade.
- AVEVA Communication Drivers Pack - Includes all the supervisory Communication Drivers as well as the necessary components for the individual configuration, management, runtime, licensing, and diagnostics for each driver. If you select this checkbox, all the below drivers gets selected. You can select or unselect the below drivers as per your requirements.
  - Allen-Bradley - ABCIP: Supports the logix platform from Allen-Bradley including ControlLogix, GaurdLogix, CompactLogix, FlexLogix, SoftLogix, and MicroLigix. Supports legacy SLC 500 Ethernet controllers. Supports bridge connectivity to legacy PLC5 and SCL 500 via DH+ and ControlNet networks. Supports AutoBuild for Logix controllers.
  - Allen-Bradley - ABTCP: Support for Allen-Bradley legacy platforms including PLC-5 and SLC5-500 controllers.
  - General Electric - GESRTP: Supports Series 90-30, Series 90-70, Versamax, Versamax Micro, Versamax Nano, and PACSystems (RX3i, RX7i) controller families.
  - Internal - SIM: Supports simulation of Discrete, Integer, Real (Float/Double Float), and String data types through OPC or SuiteLink. It has advanced data simulation capabilities for setpoint, noise, and process value tracking.
  - Modicon - MBTCP: Supports generic Modbus TCP, Modicon family of controllers including TSX Quantum, TSX Momentum, TSX Premium, and also supports Modbus Bridge.
  - Omron - OMRONFINS: Supports for Omron Ethernet-based controllers supporting the FINS network protocol including CJ1, CJ2, CS1, CP1, CV, CVM1 series.
  - Siemens - SIDIRECT: Supports Siemens S7-1200, S7-1500 platform in both legacy and symbolic modes. Supports Siemens S7-300, S7-400 controllers. Supports AutoBuild for S7-1200 and S7-1500 controllers.
  - Standards - GATEWAY: Allows connectivity to SuiteLink, OPC DA, OPC UA, InTouch, and Application Data sources. Then exposes data via SuiteLink and OPC DA to software clients.
  - Standards - MQTT: Supports traditional JSON-based simple and nested MQTT payloads based on MQTT 3.1.1 specification. Supports for Eclipse foundation Allen-Bradley MQTT Industrial Specification 1.0 B (Sparkplug-B).
  - Standards - SNMP: Supports SNMP versions V1, V2C, V3.
  - Standards - WEBSVC: Supports communications with client web services over an HTTP/S network using: Simple Object Access Protocol (SOAP) (XML payload format only), Representational State Transfer (REST) (XML, JSON format supported). Secured connectivity limited to REST-based web servers.
- License: Select this option to install both the AVEVA Enterprise License Server and AVEVA Enterprise License Manager.
  - AVEVA Enterprise License Server: Select this feature if you want to install the license locally in the node where you are installing the Communication Drivers Pack, thus requiring that node to act as a license server. If you want to install the license server in another node, this feature is not required. Use the Configurator utility to select the License Server upon installation.
  - AVEVA Enterprise License Manager: Select this feature if you want to install the License Manager locally in the node where you are installing the Communication Drivers Pack, thus requiring that node to act as a License Manager. Use the Configurator utility to select the License Server upon installation.
Select the required Communication Drivers that you want to install and click Next to continue.
The list of Communication Drivers that are going to install or upgrade appears. Click Next to continue the install/upgrade. The Installation Complete window appears.
Click Configure to open the configuration window or close the window to exit the setup.

A reboot may be required to complete the installation process. After the installation, you can see only one component (AVEVA Communication Drivers Pack 2020 R2) in the Control Panel. The user interface in the SMC remains the same.

OPC connectivity, DCOM, Windows Firewall, and Anonymous Access

Our software no longer supports Anonymous Login setting in DCOM configuration for OPC connections. In order to ensure proper communication between both nodes, you need to ensure DCOM, Windows Firewall, and user credential settings are configured properly. For additional details, refer to the section OPC connectivity, DCOM, Windows Firewall, and Anonymous Access in the Communication Drivers Core Help.

Modify, Repair, or Remove the AVEVA Communication Drivers Pack

Modifying an Installation

You can change the Communication Drivers Pack components installed on your computer. You can add new components or remove the existing ones. You must have the installation DVD inserted in the DVD-ROM drive before you can modify a program.

To modify an installation

Open the Modify, Repair or Remove Installation dialog box by doing either of the following:
- Run Setup.exe from the Communication Drivers Pack installation DVD.
- Navigate to Uninstall or Change a Program in the Windows Control Panel.
Right-click AVEVA Communication Drivers Pack and select Uninstall/Change.

Note: The name of the Uninstall/Change option may vary depending on which Windows operating system is installed on your computer.
Click the Modify option, and then click Next. The list of Communication drivers Pack components appears.
Select or clear the components that you want to add or remove, and then click Next.
The Select Modify to confirm feature changes window appears. You can see the list of Communication Drivers that will be added newly in the Adding these features box and the list of Communication Drivers that will be removed in the Removing these features box. Click Modify.
Review the license agreement and agree to the terms stated. Read the License Agreement. If you agree to the stated terms, select the I read and accept the terms of license agreement(s) and click Agree.
The selected components are added or removed. If the added components require configuration, the Configurator opens. If not, the complete modification dialog box appears.
Click Finish.

Repairing an Installation

You can repair the installation of any Communication Drivers Pack component to fix missing or corrupt files, registry keys or shortcuts. You can also reset the registry key to the default value.

Note: You must insert the installer DVD in the DVD-ROM drive before you can repair a program.

To repair an installation

Click the Uninstall or Change a Program option in Windows Control Panel. The list of software installed on your computer appears.
Right-click AVEVA Communication Drivers Pack and select Uninstall/Change. The Modify Repair or Remove Installation dialog box appears.
Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.
Click the Repair option, and then click Next. The Confirm Repair dialog box appears.
Click Repair. The complete repair dialog box appears.
Click Finish.

Uninstall the Communication Drivers Pack

The uninstallation process uninstalls only the Communication Drivers and the dependent components. All the prerequisites and independent components should be uninstalled manually. The following Communication Drivers are uninstalled along with the Communication Drivers Core:

Allen-Bradley - ABCIP
Allen-Bradley - ABTCP
Beckhoff - TWINCAT
General Electric - GESRTP
Internal - SIM
Mitsubishi - MELSEC
Modicon - MBTCP
Omron - OMRONFINS
Schneider-Electric - SOMAC
Siemens - SIDIRECT
Standards - BACLITE
Standards - CODESYS
Standards - GATEWAY
Standards - MQTT
Standards - SNMP
Standards - WEBSVC
Texas Instruments - TI500
Note: To uninstall a component of the Communication Drivers Pack, use Modify option. For more information refer to Modifying an Installation section above.

To uninstall Communication Drivers Pack

Click the Uninstall or Change a Program option in Windows Control Panel. The list of software installed on your computer appears.
Right-click AVEVA Communication Drivers Pack, and select Uninstall/Change button. The Modify, Repair or Remove Installation dialog box appears.
Click the Remove option, and then click Next. The confirmation dialog box appears.
Click Uninstall. The AVEVA Communication Drivers Pack is uninstalled and the complete uninstallation dialog box appears.
Click Finish.

Silent Installation of Communication Drivers Pack

The Communication Drivers Pack supports silent (command line) installation. The prerequisite products that are installed during the silent installation includes:

Archestra Data Store (ADS)
Activation-based Licensing components
- AVEVA Enterprise Licensing
- AVEVA Enterprise License Manager
- AVEVA Enterprise License Server

Before initiating the silent installation of Drivers Pack, it is strongly recommended that you stop all the DAServers, OI Servers, and Communication Drivers.

Silent Installation Syntax

The basic syntax of the silent installation command consists of the full path to the Silent_Install_Setup.bat file (typically the DVD drive designation on your local computer), and the command line switch.

<DVD>: AVEVA Communication Drivers Pack 2020 R2.1>Silent_Install_Setup.bat /<argument>

The usage instructions can be retrieved by the following command line. It returns the supported operations - install and uninstall.

<DVD>: AVEVA Communication Drivers Pack 2020 R2.1>Silent_Install_Setup.bat /?

To install/uninstall the Communication Drivers Pack

Open a command prompt using Run as administrator
Run the batch file set up with the /install or /uninstall switch respectively.
Installation: C: AVEVA Communication Drivers Pack 2020 R2.1>Silent_Install_Setup.bat /install

Uninstallation: C: AVEVA Communication Drivers Pack 2020 R2.1>Silent_Install_Setup.bat /uninstall
Wait for the system to display the confirmation message - Silent installation completed successfully or Silent uninstallation completed successfully

The silent installation process installs Communication Drivers along with the prerequisite products. However, the uninstallation process uninstalls only the Communication Drivers and the dependent components. All the prerequisites and independent components should be uninstalled manually. The following Communication Drivers are installed along with the Communication Drivers Core:

Allen-Bradley - ABCIP
Allen-Bradley - ABTCP
General Electric - GESRTP
Internal - SIM
Modicon - MBTCP
Omron - OMRONFINS
Siemens - SIDIRECT
Standards - GATEWAY
Standards - MQTT
Standards - SNMP
Standards - WEBSVC

Resolved Issues

The are no new resolved issues in this release for the Communication Drivers Core. Individual driver resolved issues are listed in the respective driver readme files.

Known Issues

There are no known issues at the time of release for the Communication Drivers Core. Individual driver known issues are listed in the respective driver readme files.

AVEVA™ Communication Drivers Core Documentation

The AVEVA™ Communication Drivers Core documentation set includes the following guides. These documents can be accessed from the Help menu in the SMC.

AVEVA™ Communication Drivers Core Help. This documentation describes the runtime Configuration, Diagnostics, and Activation/Deactivation aspects of a Communication Driver.
Log Viewer Help. This guide provides information about the Logger™ and the Log Viewer snap-in to the System Management Console.
LogFlag Editor User's Guide. This documentation describes the user interface and functions of the LogFlag Editor utility. This utility can be opened only from the Log Viewer, a part of the System Management Console suite of utilities.
AVEVA Enterprise License Manager Help This guide describes how to use the License Manager to activate and acquire licenses.
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.

Viewing PDF Documentation

The documentation describing how to use this product are included on the CD in PDF format. Viewing these guides requires the installation of Adobe's Acrobat Reader. This utility is not included on this CD, but it can be downloaded for free from the Adobe's Web site at the following Web address:

www.adobe.com/products/acrobat/readstep2.html

After downloading the file from Adobe, you must run the executable to install it on your computer. Follow the typical installation routine. After installation, you can either open the Acrobat Reader and select a user's guide from the File menu, or double-click a user's guide on the CD in Windows Explorer.