Last revision: 6/14/2024
This Readme file contains information on the Communication Drivers Pack 2023 R2 Patch 01 release. The 2023 R2 Communication Drivers Core Readme is also included in this document for essential information on the Communication Drivers Pack 2023 R2 release. For information specific to other Communication Drivers, refer to the 2023 R2 Readme file of the Communication Driver.
All issues that have been resolved in a Communication Driver in the CDP 2023 R2 and CDP 2023 R2 Patch 01 releases have been consolidated under the Resolved Issues section under the respective Communication Driver topic. The Known Issues section lists all the current and previous known issues in any of the Communication Drivers that are part of the Communication Drivers Pack.
Note: If a particular Communication Driver has not been listed, it is because there has been no update in the Communication Driver in the CDP 2023 R2 or CDP 2023 R2 Patch 01 release.
Communication Drivers Pack 2023 R2 Patch 01 is a component of the System Platform 2023 R2 Patch 01 release. CDP 2023 R2 P01 can be installed only on nodes that have CDP 2023 R2.
For more information on installing the patch, refer to the System Platform Patch Install readme.
Note: To install additional Communication Drivers on a machine after installing the System Platform patch, select the Communication Drivers Pack program in the control panel and modify the CDP installation. You cannot add additional CDP components after installing the patch by launching the System Platform 2023 R2 Setup.exe.
This section contains a list of all the defects and issues that have been resolved in a Communication Driver in the CDP 2023 R2 Patch 01 and CDP 2023 R2 releases.
Resolved Issues in CDP 2023 R2 Patch 01
Defect ID |
Case Number |
Description |
2620090 |
960302613 |
InTouch App objects and Device Integration objects would lose data after redeploying the app objects. |
3192130 |
960394102 |
'Wrong 2 ! 0x0000000D' warning was appearing in the logger related to licensing. |
3319770
|
960417184 |
A Communication Driver would provide incorrect data if the 'Synchronous IO / CACHE' option was configured in an OPC client. |
3298490
|
960410755 |
There was a bug in the PlugInOPC.dll released with CDP 2023 R2. |
Resolved Issues in CDP 2023 R2
Defect ID |
Case Number |
Description |
2519933 |
960277171 |
Some values would turn to bad quality when switching symbols in WindowViewer. |
2543057 / 2616406
|
960311100 / 960330161 |
An unknown error 0xC0000005 would appear due to an issue in the SuiteLink data type when creating an item. |
2584245 |
960303129 |
Incorrect Update Time would appear in some Device Group configurations due to an issue with the MaxUpdateInterval system item. |
Resolved issues in 2023 R2 Patch 01
Defect ID |
Case Number |
Description |
2550600 / 3217022
|
960300652 / 960389957 |
A communication loss would occur between the ABCIP Communication Driver and a PLC after executing many windows switches in InTouch. |
2938892 |
960153759 |
ABCIP performance was degrading due to increase in message count in which some of the messages were empty. |
Resolved Issues in 2023 R2 Patch 01
Defect ID |
Case Number |
Description |
2642313 |
960329269 |
Gateway memory usage would increase till 1.8 GB and then crash. |
2885585 |
960335352 |
Gateway crash issue. |
2905776 |
960329570 |
The memory of Gateway Communication Driver instances was growing, causing a memory leakage. |
2866745 / 2997235 |
960311194 |
RDI (Redundant Device Integration) active sources would continuously switch to DI. |
2809963 |
960332749 |
There would be a memory leak in the Gateway Communication Driver when a client calls an OPC sync read operation. |
3022654 |
960302467 |
OCMC would respond slowly, when accessing multiple Gateway instances, to clients sending continuous write requests on few tags when the end device is down. |
2972670 |
960350480 |
Slow moving tags would appear as quality 0x20 due to the incorrect referencing count of items when there were multiple connections to the Gateway Communication Driver referencing the same items. |
2971810 / 3243433 |
960366459 / 960400713 |
Tags would get stuck in quality 0x20. |
3079309 |
960388248 |
Automation objects would get stuck in initializing after object deployment. |
2904369 |
960284829 |
Random SuiteLink tags would switch to quality 0x0018 after one minute. |
3238047 |
960395335 |
Gateway crash issue. |
Resolved Issues in 2023 R2
Defect ID |
Case Number |
Description |
2515701
|
960307191 |
OPC servers were not shutting down when the Gateway Communication Driver was not connected to it. |
2516854 |
960296496 |
When a client subscribed to a tag and immediately wrote i, the write would be rejected with the following warning line in logger: “GATEWAY\OPCUA: Rejecting poke value to read-only tag MY_TAG.” The tag property was set to read-write, unlike what is mentioned in the warning line. This issue occurred when connecting to a OPC UA data source. |
2494821 / 2494952 |
960302467 / 960292902 |
OCMC would hang when a reset was performed on OPC UA groups. |
2607648 |
960328609 |
Some Access Names/Topics configured in the Gateway Communication Driver would get disconnected during a short network failure, and did not return online after connection was re-established. |
2503825 |
960274585 |
Memory leak was observed due to continuous async read/write operations on mixture of good and bad items. |
2579602 |
960321616 |
Memory leak was observed during reset operations. |
2404041 |
960280496 |
Data freezing issues were observed in normal connections with values lagging by 1 day on certain devices, not all devices. |
2490136 |
960193194
|
Issues in the connection between the Gateway Communication Driver and a third-party MQTT broker were observed. |
2595777 |
960324672 |
Object attributes were getting stuck in initializing quality in app objects that connected to an OPCUA server.The OPCClient object quality was 01C0. |
Resolved Issues in 2023 R2 Patch 01
Defect ID |
Case Number |
Description |
2727714 |
960329211 |
Data sources were not appearing in the central configuration pane in the MQTT publisher. |
2906366 / 3040450
|
960352679 / 960382671 |
MQTT Publisher would display only the basic scope (bad/good/uncertain) but not the exact payload quality of an Application Server attribute. |
3302594 |
960392442 |
The MQTT Communication Driver would remove slashes from the group ID during reconnection due to a parsing error. |
3306768 |
960411620 |
The MQTT Communication Driver did not send an 'OFFLINE' message when the broker was disabled, resulting in data loss. |
Resolved Issues in 2023 R2
Defect ID |
Case Number |
Description |
2537039
|
960291080 |
Bad item references (not adhering to case sensitivity) were getting stuck in the MQTT Communication Driver, even after the name was fixed and item was redeployed. |
2538979 |
960312223 |
Values were stuck in "Initializing" until the MQTT Communication Driver received an NData message from the broker. |
2506012
|
960304223 |
The MQTT Communication Driver was crashing repeatedly due to out of range values from a third party publisher. |
2509627
|
960301994 |
Connections to the broker were failing when source tags had a value of NaN for float tags. |
2888486
|
960340462 |
MQTT Subscriber did not correctly parse data in the JSON-VTQ1 format. |
Resolved issues in 2023 R2
Defect ID |
Case Number |
Description |
2451505 |
960291657 |
Poking bits was not working to HR registers. |
Resolved Issues in 2023 R2 Patch 01
Defect ID |
Case Number |
Description |
2994121 |
960370779 |
Issue in RDO failover when the primary and secondary PLCs were Siemens S7-400H series. |
Resolved issues in 2023 R2
Defect ID |
Case Number |
Description |
2335335
|
<Internal> |
The whole Group reading would fail if one or more invalid OIDs were defined in the worksheet body in SNMP driver version 1.3. |
2445853 |
960285873 |
The whole Group reading would fail if one or more invalid OIDs were defined in the worksheet body in SNMP driver version 1.3. Many errors and BAD quality tags would appear. |
Resolved issues in 2023 R2 Patch 01
Defect ID |
Case Number |
Description |
2972216 |
960366708 |
The lower part of the configuration pane was not invisible in the Japanese OS. |
2969607 |
960365688 |
The WEBSVC driver would ignore part of Authorization header and body saved during the configuration for REST API. |
2921003
|
960332272 |
The WEBSVC Communication driver would periodically lose connection and then reconnect while using the SOAP protocol. |
This section contains a list of known issues in all the Communication Drivers in the 2023 R2 Patch 01 and the 2023 R2 releases.
Known Issues in 2023 R2 P01
Communication Driver |
Defect ID |
SR/Case Number |
Description |
Core |
(Internal) |
(Internal) |
Issue: After installing CDP 2023 R2 Patch 01 on a machine that has standalone CDP 2023 R2, the notification to reboot the machine may not appear. Without a reboot, some components may not function properly. Note: This error occurs only when there is an upgrade on standalone CDP 2023 R2, not System Platform 2023 R2. Work-around: Manually reboot the machine to avoid any performance issues.
|
Known Issues in 2023 R2
Communication Driver |
Defect ID |
SR/Case Number |
Description |
Core |
2629730 |
(Internal) |
Issue: While upgrading from SP 2023 to SP 2023 R2, a warning message related to the "OIMigrationUtil" component appears, although there is no functional impact in the Communication Driver. This error will not appear in future upgrade scenarios post SP 2023 R2. |
Core |
(Internal) |
(Internal) |
Issue: Old CHM help files may appear in the Microsoft Management Console when you upgrade to CDP 2023 R2 on a machine with a version of System Platform older than SP 2023. Work-around: CHM help files have been deprecated. You can access the latest AVEVA Communication Drivers web help in any of the following ways:
|
MELSEC, OMRONFINS |
(Internal) |
(Internal) |
32-bit supported data types may not operate with precision. |
Last revision: 11/14/2023
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
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 the Communication Drivers Pack 2023 R2 version that has been released along with System Platform 2023 R2. Carefully review this document for issues that have been resolved in this release, and some known issues you may encounter while using the Communication Drivers Pack 2023 R2.
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:
Program Files(x86)\Wonderware\OSSLicense_CommunicationDriversPack.pdf
OpenSSL version upgrade
The Communication Drivers Pack now ships OpenSSL version 3.0 along with the existing version 1.1.
OPC UA Methods Support
Client applications can now call methods in an OPC UA server through the OPC UA client in the Gateway Communication Driver.
The Communication Drivers Pack 2023 R2 release is compatible with the following releases:
For detailed information on product and platform compatibility, refer to the Technology Matrix section of the Global Customer Support (GCS) Site.
The Communication Drivers Pack 2023 R2 release is supported on the following Windows client and server operating systems (64-bit only).
Semi-Annual Channel Releases:
Long Term Service Channel Releases:
Refer to the Technology Matrix, available at the Global Customer Support (GCS) site, for the latest information.
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:
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.
Installation Checklist
Before installing the Communication Drivers Pack, please ensure the following:
It is also recommended to stop the platform where the Communication Drivers Pack will be installed.
Install/Upgrade Procedure
Download AVEVA Communication Drivers Pack 2023 R2 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.
To Install/Upgrade the AVEVA Communication Drivers Pack
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.
- 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
Note: As part of the CDP installation, you can install the PCS plug-in for Communication Drivers, along with the PCS framework components (PCS Runtime and PCS Service Repository), only if the PCS framework is installed on the same machine. The PCS Framework is installed along with System Platform.
If no version of the PCS Framework is present on the machine, the PCS plug-in and PCS framework components cannot be installed during the CDP installation.
Select the required Communication Drivers that you want to install and click Next to continue.
The Installation Complete window appears.
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 2023 R2) 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.
Modifying an Installation
You can change the Communication Drivers Pack components installed on your computer. You can add new components or modify the existing ones. Download the AVEVA Communication Drivers Pack 2023.1 Patch 02 from the Connectivity Hub section of the Global Customer Support before you can modify a program.
To modify an installation
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.
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
Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.
Uninstall the Communication Drivers Pack
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. The following Communication Drivers are uninstalled along with the Communication Drivers Pack:
To uninstall Communication Drivers Pack
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.
The Communication Drivers Pack supports silent (command line) installation.
Before initiating the silent installation of the Communication 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 2023 R2>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 2023 R2>Silent_Install_Setup.bat /?
To install/uninstall the Communication Drivers Pack
Installation: C: AVEVA Communication Drivers Pack 2023 R2>Silent_Install_Setup.bat /install
Uninstallation: C: AVEVA Communication Drivers Pack 2023 R2>Silent_Install_Setup.bat /uninstall
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:
The AVEVA™ Communication Drivers Pack documentation set includes the following guides. These documents can be accessed from the Help menu in the OCMC.
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.
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.
|
© 2015-2024 AVEVA Group Limited or its subsidiaries. All rights reserved. | Contact Us |