AVEVA™ Communication Drivers Pack 2023 R2 SP1 Readme

Last revision: 10/29/2024

About this Readme

This Readme contains information on the Communication Drivers Pack 2023 R2 SP1 release.

Important Information

CDP 2023 R2 SP1 can be installed on a clean machine, or a machine that has an earlier version of CDP only.

If you have installed CDP components with a System Platform installer, you can upgrade these components using only the upgraded version of the System Platform installer, not the standalone CDP installer. When you install standalone CDP 2023 R2 SP1, the installer will first scan for Application Server, InTouch, and Historian components on the machine, and if any version of these components are detected, the installation of CDP is not supported.

New in this Release

Communication Drivers Pack

Option to activate all instances of the Communication Driver

If you have multiple instances of a Communication Driver, you can activate all of them together in one go instead of activating each instance individually.

64 tags free license mode

You can use CDP for free with 64 tags or less. Previously, the limit was 32 tags.

Communication Drivers SDK is no longer a part of the CDP installer

The Communication Drivers SDK has been removed from the CDP installer. The standalone SDK installer is available on the AVEVA Global Customer Support (GCS) site.

SuiteLink Security Improvements

The SuiteLink package has been enhanced to restrict the number of connections a SuiteLink client can make to a Communication Driver.

MQTT Communication Driver

Subscribe to quality tags in both integer and string format

The 'quality' parameter in the JSON-VTQ2 format can be represented in both integer and string format. Previously it supported only the integer format.

Gateway - OPC UA Methods

OPC UA method calls support all data types

You can invoke OPC UA Methods that include any of the built-in basic data types either as arguments or return values. Refer to the Gateway Communication Driver documentation for information on the supported data types.

System Requirements

Refer to the Technology Matrix report available on the AVEVA Global Customer Support (GCS) site for information on system requirements, supported controllers, and product compatibility.

For information related to a particular Communication Driver, enter the name of the Communication Driver ("ABCIP", for example) and select the appropriate version number. For information related to the Communication Drivers Pack release in general, enter "Communication Drivers Pack" and select the appropriate version number.

Install 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

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.
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 have read and accept the terms of license agreement(s) and click Agree.
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.
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.
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.

Silent Installation

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

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>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>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>Silent_Install_Setup.bat /install

Uninstallation: C: AVEVA Communication Drivers Pack>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 all the 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.

Modify, Repair, or Uninstall the Communication Drivers Pack

You can change the Communication Drivers Pack components installed on your computer. You can add new components, uninstall modify the existing ones, repair missing or corrupt files, registry keys, or shortcuts.

To modify an installation, you can either :
- Run Setup.exe from the Communication Drivers Pack installation DVD or
- Modify the Communication Drivers Pack program in the Programs and Features section in the Windows Control Panel.
To repair an installation, Repair the Communication Drivers Pack program in the Programs and Features section in the Windows Control Panel.
Note: You must insert the installer DVD in the DVD-ROM drive before you can repair a program.
To uninstall the Communication Drivers Pack, Remove the Communication Drivers program in the Programs and Features section in the Windows Control Panel.
The uninstallation process uninstalls only the Communication Drivers and the dependent components. All the prerequisites and independent components (such as the PCS framework and Licensing components) should be uninstalled manually.

Note: You cannot uninstall the Communication Drivers Pack if the Application Server or InTouch product from SP2020R2SP1 (or above) is installed on the same machine. You have to uninstall the Application Server or InTouch product before uninstalling Communication Drivers Pack.

Resolved Issues

This section contains a list of all the defects and issues that have been resolved in the Communication Drivers Pack in this release.

Issues resolved in the CDP 2023 R2 Patch 01 release have also been included in this release. Refer to the CDP 2023 R2 P01 Readme for the list of resolved issues and other relevant information on the 2023 R2 Patch 01 release.

Note: The list contains only those Communication Drivers that have had updates for this release. Communication Drivers that do not have any updates are not listed.

Communication Drivers Core

Defect ID	Case Number	Description
3326442	960410600	[SuiteLink] InTouch WindowViewer would hang while establishing a SuiteLink connection due to the hardcoded TLS Handshake timeout configuration.
3194606	960394046	[SuiteLink] There was a periodic loss of updates when a SuiteLink client tried connecting to a Communication Driver that was hosted on a a remote computer that was switched off.
3250362	960400710	"Unknown error 0xC0000005" was getting logged during the activation and deactivation of some Communication Drivers.
N/A	AVEVA-2024-007	[SuiteLink] Security Enhancements to protect SuiteLink against volumetric Denial of Service attacks.
3372921 / 3346287 / 3384326	960427120 / 960422504 / 960429788	Communication Drivers would crash due to a code limitation in DASWRAPPER.exe.
3462372	960425723	A memory leak was observed in some Communication Drivers due to a bug where items were not removed during cleanup caused by incorrect item handles.
3451380	960441674	The default PCS Scope Name of a Communication Driver instance would display incorrectly when a remote computer accessed the Communication Driver.

Gateway

Defect ID	Case Number	Description
2972728	960328609	Gateway topics would disconnect after multiple network disconnections, but the disconnected topics would not return online after the network connection was re-established.
3349533	960419570	An unnecessary warning message would appear when items were dynamically assigned via a script in an ArchestrA object.
3504044	960441742	The Gateway Communication Driver was unable to browse tags in a third-party OPC UA server due to a character length limitation in one of the function calls in the UA SDK.
3449321	960444198	Some special characters were not supported in the Alias name of the OPC UA namespace.
3510871	960450903	OPC UA redundancy fail-over based on the Service Level was not working.
3531287	960466563	Instances in the Gateway Communication Driver would take up to three minutes to activate due to slow searching of items during subscription.
3494536	960448345	There was a quality x0020 issue related to a hotfix that was provided for the previous release of CDP.
3429793	960440113	Unknown error 0xC0000005 would appear in the log during activation and deactivation.

GESRTP

Defect ID	Case Number	Description
3434491	960423176	Some items in the GESRTP Communication Driver were not getting updated. This issue was affecting random items at random times.

MBTCP

Defect ID	Case Number	Description
3322932	960415073	The MBTCP Communication Driver would crash after the PLC was switched off.

MQTT

Defect ID	Case Number	Description
3370721	N/A	[Enhancement] The MQTT Communication Driver has been enhanced to recognize incoming payload in the JSON-VTQ2 format to have its Quality specified either as an integer or a string. Previously the format supported only integers.
3510936	960441616	I/O fields were not getting updated, resulting in loss of field connections.

SIDIRECT

Defect ID

Case Number

Description

3514476

960426548

The following error would appear in the Logger for Symbolic Protocol after upgrading to 2023 R2 - "Exception caught in SIDirectS7CP_Plus::ProcessPollMessage resolved items."

WEBSVC

Defect ID	Case Number	Description
3379089	960427245	A "401" error code would appear in the runtime application even though results were successfully retrieved in the Web Service Communication Driver.

Known Issues

The following table lists the known issues in this release of the Communication Drivers Pack:

Component	Defect ID	SR/Case Number	Description
Core	(Internal)	(Internal)	Issue: While upgrading from System Platform 2023 R2 P01 to 2023 R2 SP1, a warning message associated with the GDIWebServer component is logged. Message: Unable to find the file System.Runtime. Please check the installation. This is due to the sequence in which individual components are installed. The GDIWebServer component is installed by the AutoBuild installer package, which is installed after the main Setup installer package. After the installation of AutoBuild.msi, the service starts without any issue. The warning does not affect the functioning of the product and can be ignored in the context of this upgrade scenario.
Core	(Internal)	(Internal)	Issue: While upgrading from System Platform 2023 to 2023 R2 SP1, a warning message associated with the OIMigrationUtil component is logged. Message: Exception - Access to the path 'C:\ProgramData\Wonderware\OI-Server\TempOI.dat' is denied. The warning does not affect the functioning of the product and can be ignored in the context of this upgrade scenario. The trigger for the warning will be analyzed and rectified in future releases.
Core	(Internal)	(Internal)	Issue: Items subscribed using PCS communication have incorrect values in Historian after performing Store and Forward. Workaround: Subscribe to items using SuiteLink or OPC-DA communication channels.

Documentation and Learning

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

AVEVA™ Communication Drivers Pack Help. This documentation describes the runtime Configuration, Diagnostics, and Activation/Deactivation aspects of a Communication Driver.
Note: In the OCMC, under the Help menu, if you click the Help Topics option, you may not be able to view the CHM help in some operating systems. Alternately you can open the online help by right-clicking on the respective communication driver node and selecting the Help option.
Operations Control Logger. This guide provides information about the Logger and the Log Viewer snap-in to the Operations Control Management Console.
AVEVA Enterprise License Manager Help This guide describes how to use the License Manager to activate and acquire licenses.

New! Access Docs Online

The product documentation is now available on the AVEVA documentation portal. To comply with the portal guidelines, the style and tone of the documentation content has been modified. Hence, the content available on the portal may differ slightly from the documentation delivered with the product release.

HMI SCADA YouTube channel

Our YouTube channel contains instructional and promotional videos on our various product lines. Please follow the link below:

HMI SCADA Channel Main Page

https://www.youtube.com/user/wonderwarehmi

eLearning Training Courses

You can now access hundreds of training courses that cover simple and complex topics with all the products that you use in our Operations Control portfolio. Access to the eLearning modules is free!

https://sw.aveva.com/training