2023 R2 SP1
- Last UpdatedOct 23, 2024
- 5 minute read
Expectations and Limitations
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 Features and Enhancements
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.
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. |