Install/Upgrade the Communication Drivers Pack

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 the AVEVA Communication Drivers Pack from the Connectivity Hub section of the Global Customer Support.

Note: AVEVA Communication Drivers Pack is not supported on 32-bit operating systems.

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.

Install/Upgrade the AVEVA Communication Drivers Pack

1. Locate the installer file (Setup.exe) in the AVEVA Communication Drivers Pack installation media. Double-click the Setup.exe file or right-click Setup.exe and select Run as administrator.

2. 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.

3. Click OK. The License Agreement window appears.

4. Review the license agreement and agree to the terms stated. Read the License Agreement. If you agree to the stated terms, select the I have read and accept the terms of license agreement(s) and click Agree.

5. If you accept the license agreement, 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.

     • PCS Plug-In: Supports PCS connectivity for Communication Drivers in System Platform. This option cannot be selected on a node that does not have the PCS Framework.

     • Allen-Bradley - ABCIP: Supports the logix platform from Allen-Bradley including ControlLogix, GaurdLogix, CompactLogix, FlexLogix, SoftLogix, and MicroLogix. 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.

     • Beckhoff - TWINCAT: Leverages the TwinCAT ADS communication library for communication and supports any TCP/IP Ethernet Beckoff device compatible with the ADS Library version you install. The TC1000:TC3 Library should be compatible with CX1010, CX1020, CX1030, CX2000, CX5000, CX5100, CX8000, and CX9000 and any other device hosting the TwinCAT runtime 2 and 3.

     • 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.

     • Mitsubishi - MELSEC: Supports the controller families MELSEC-Q, MELSEC-QnA, MELSEC-L, and MELSEC-iQ-R.

     • 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.

     • Schneider-Electric - SOMAC: Supports the Logic Controllers Modicon M241 PLC and Modicon M251 PLC. Also, supports the Motion Controllers PacDrive 3 LMC Eco/ Pro/Pro2.

     • 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 - BACLITE: Supports the BACNet/IP Communication protocol.

     • Standards - CODESYS: Supports connectivity to Codesys-based controllers of versions 20x and 3.x. The following were qualified internally, but the driver can still work suppliers that use the CODESYS.

       - Bosch Rexroth-L40 and L65

       - CODESYS – SP WIN V3.5.1 Control, SP PLCWinNT V2.4.4.0

       - EATON – XC-CPU202 CODESYS V3.5

       - Schneider Electric – 241/M251

       - WAGO- CPU 750-841

     • 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 Subscription and publishing of Sparkplug and JSON-based MQTT payloads based on the MQT 3.1.1 specification.

     • 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.

     • Texas Instruments - TI500: Supports the Control Technology Inc. – CTI2500 (replacing the TI500’s series). Supports the controllers – TI545 / 565 / 575. Supports Serial and Ethernet connectivity.

   • 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 Server Legacy Support: Select this feature to install legacy versions of the license server (that is, versions prior to AVEVA Enterprise Licensing 4.0.) on the node where you are installing the Communication Drivers Pack. If this checkbox is not selected, all client nodes that connect to this License Server would need to be upgraded to version 4.0 or above.

     • 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.

       Note: As part of the System Platform installation, you can install the PCS plug-in for Communication Drivers, along with the supported PCS framework components (PCS Runtime and PCS Service Repository), You cannot install the PCS plug-in during a standalone CDP installation since the PCS framework is not present on the machine.
       

       Select the required Communication Drivers that you want to install and click Next to continue.

6. The list of Prerequisites and selected Products (Communication Drivers and Licensing components) that are going to get installed or upgraded appears. Click Install to continue the install/upgrade.

   The Installation Complete window appears.

   Note: If Application Server, InTouch, Historian, or Historian Client components are installed on the machine, it is recommended to install standalone CDP 2023 R2 SP1 on a clean machine instead. Otherwise, you have to uninstall these components to continue with the standalone installation of CDP 2023 R2 SP1 on the same machine.

7. Click Configure to open the configuration window or close the window to exit the setup.

   Note: On a node with standalone CDP, you cannot configure the System Management Server (SMS), so a secure SuiteLink connection cannot be established with Communication Drivers on this node.

   Note: While upgrading an existing Communication Drivers Pack with unsecure SuiteLink to 2023 or later without configuring SMS, then fallback is disabled. SuiteLink no longer works after upgrade. Make sure the Accept non-encrypted SuiteLink connections (mixed mode) check box in the Advanced window of the Configurator is selected. By default, this option is selected on upgrade. For more information, refer to the Secure SuiteLink Connection section of the AVEVA™ Communication Drivers Pack help.

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

OPC connectivity, DCOM, Windows Firewall, and Anonymous Access

The Communication Drivers Pack 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.