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.
Patch Installation
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.
Resolved Issues
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.
Communication Drivers Core
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. |
ABCIP Communication Driver
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. |
Gateway Communication Driver
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. |
MQTT Communication Driver
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. |
OMRONFINS Communication Driver
Resolved issues in 2023 R2
Defect ID |
Case Number |
Description |
2451505 |
960291657 |
Poking bits was not working to HR registers. |
SIDirect Communication Driver
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. |
SNMP Communication Driver
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. |
WEBSVC Communication Driver
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. |
Known Issues
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. |