Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Communication Drivers

2023 R2 SP1 P01

  • Last UpdatedMar 24, 2025
  • 2 minute read

Patch Installation

Communication Drivers Pack 2023 R2 SP1 Patch 01 is a component of the System Platform 2023 R2 SP1 Patch 01 release. CDP 2023 R2 SP1 P01 can be installed only on nodes that have CDP 2023 R2 SP1.

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 SP1 Setup.exe.

Important: The Communication Drivers Pack online help files and AVEVA Help Viewer will not be included or supported in future releases. All product documentation will continue to be available in PDF format on the installation media and on the web at docs.aveva.com.

Resolved Issues

Communication Drivers Core

Defect ID

Case Number

Description

3503632

960536398

[DASEngine][DASTKRuntime] When an unknown data type appeared in a row, its data type was locked as a string. When the Communication Driver received the correct data type, it could not be changed.

3622861

960495004

[PCS] In Communications Driver Pack 2023 R2 SP1, late values were incorrect or duplicated when using the PCS connection.

Gateway

Defect ID

Case Number

Description

3490616 / 3630050

960423556 / 960497069

[OPC UA] Watchdog tags were rejecting pokes to read-only tags.

3580220

960476860

[OPC UA][Enhancement] Improved Gateway OPC UA client failover performance by adding an option to trigger bad quality during watchdog timeout.

3489426

960453501

[OPC UA] OCMC would crash with Exception code: 0xc0000005 when executing a TestConnection within the OPC UA Server configuration editor. This was due to an incorrectly formed browse reference received from the OPC UA server.

3676422

960328609

During a network failure, Gateway topics would disconnect and not return online even after the network connection is reestablished.

MQTT

Defect ID

Case Number

Description

3569358 / 3666001

960455477 / 960513421

OCMC would crash while configuring MQTT, specifically while browsing for CA files.

OMRONFINS

Defect ID

Case Number

Description

3625466

960493961

[DASWrapper] The OMRONFINS driver would stop communicating due to a logic issue when handling write for array tags in DASWrapper.

WEBSVC

Defect ID

Case Number

Description

3454770 / 3611264

960443892 / 960482344

Access tokens would not get generated when using the OAuth 2.0 authentication type.

3647923

960502212

Requests with invalid tokens were getting through without errors or warning messages.

Known Issues

There are no known issues in this release of the Communication Drivers Pack.

Workaround: Right-click the Configuration node and select the Use Another Configuration Set option to load the desired configuration set.

In This Topic
Related Links
TitleResults for “How to create a CRG?”Also Available in