2023 R2 SP2 release notes
- Last UpdatedSep 10, 2026
- 4 minute read
Expectations and Limitations
-
CDP 2023 R2 SP2 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 SP2, 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.
-
The minimum version from which you can upgrade to CDP 2023 R2 SP2 is CDP 2023. You cannot upgrade to CDP 2023 R2 SP2 from a version that was released before CDP 2023.
New Features and Enhancements
-
Critical security fixes.
-
Upgraded from .NET8 to .NET10.
Resolved Issues
This section contains a list of all the defects and issues that have been resolved in a Communication Driver in the Communication Drivers Pack 2023 R2 SP2 release.
Core
|
Defect ID |
Case Number |
Description |
|
4550428
|
962742430 |
An error message "- /Unknown opcode in FixupOperand()" was appearing when upgrading InTouch to the 2023R2 SP1 P04 version, due to a reentrancy issue when UI events are dispatched from SLSOpen. |
|
4680190 |
962776378 |
[SuiteLink] The Engine hosting a DDE SuiteLink object would take a long time to respond when the DDE suiteLink object reconnects to an unavailable Communication Driver. |
|
4915697
|
962875938 |
When the value of a tag was updated in InTouch, it would flicker between the old value and new value a few times before stabilizing. |
|
4947744 |
962822766 |
[SuiteLink] There were SuiteLink hardening and stability issue that were causing permanent stall in data transmission or reception. |
ABCIP
|
Defect ID |
Case Number |
Description |
|
4758082 |
962819815 |
The ABCIP Communication Driver was intermittently failing due to a deadlock issue. |
|
4841219
|
962853001 |
The ABCIP Communication Driver was erratically freezing, which resulted in communication issues during runtime. |
Gateway
|
Defect ID |
Case Number |
Description |
|
4696498 |
962769259 |
[MQTT] The "retain" flag for the MQTT Connection in the Gateway Communication Driver was not working as expected. |
|
4876988
|
962861624 |
[OPC UA] OCMC was automatically getting closed after you select the 'Test' button to get the OPC UA Namespace. |
|
4688264
|
962735049 |
[MQTT] Malformed MQTT packets were generated when publishing topics that contained a dot (.). Upon receiving a malformed packet, the broker would disconnect from the client, which resulted in a continuous disconnect/reconnect cycle. |
|
4846514
|
962854296 |
[OPC UA] The OPC UA server was holding item subscriptions as active even after they were unsubscribed. |
|
4922038 |
962886257 |
The Gateway Communication Driver was crashing due to a race condition during system item updates. |
|
4924551
|
962880641 |
[OPC UA] Trace files were automatically getting generated whenever an OPC UA connection was established. |
MBTCP
|
Defect ID |
Case Number |
Description |
|
4320949, 4663434 |
960592688, 962697991 |
The MBTCP Communication Driver was not restoring the connection to the PLC after the PLC comes online. |
MELSEC
|
Defect ID |
Case Number |
Description |
|
4453788 |
962703850 |
A catastrophic failure was observed in the MELSEC Communication Driver during the data conversion process. |
|
4681785
|
962779819 |
If the MELSEC Communication Driver faced a communication issue with one PLC (connection timeout or read timeout), it caused the other PLCs that were configured in the same driver instance to stop responding, or show stale diagnostics data |
MQTT
|
Defect ID |
Case Number |
Description |
|
4378187 |
962653399 |
The MQTT Communication Driver was posting redundant values to the client upon receiving late data. |
|
4474699 |
962677875 |
If an MQTT instance that is configured as the Primary Host Application disconnects from the broker, it would not send an ONLINE message after reconnecting to the broker. |
|
4425795 |
962664302 |
The MQTT Publisher and Browser were empty when SMS was configured with an IT Certificate. |
|
4424919
|
962679743 |
There was a controller memory error in the MQTT publisher due to an issue in handling he memory mapped file when browsing a large galaxy. |
SIDirect
|
Defect ID |
Case Number |
Description |
|
4544429
|
962724099 |
The SIDirect Communication Driver was reporting a "catastrophic failure" when poking large volumes of data to the PLC. |
SNMP
|
Defect ID |
Case Number |
Description |
|
4220162
|
960657526 |
Item values of the string data type displayed uncertain quality after disconnecting and reconnecting to an SNMP device. |
|
4791231 |
962792795 |
The SNMP Communication Driver was incorrectly updating the initial value after a disconnection and reconnection.r |
SOMAC
|
Defect ID |
Case Number |
Description |
|
4330571 |
962614343 |
ENUM Variables were getting displayed as "BAD" values in the SOMAC Communication Driver logs. |
TI500
|
Defect ID |
Case Number |
Description |
|
4325297 |
962615000 |
The TI500 Communication Driver Diagnostics would display decimal points correctly, but decimal points were not shown in clients. |
WEBSVC
|
Defect ID |
Case Number |
Description |
|
4469716 |
962704448 |
New JSON Web Tokens were getting created each time the WEBSVC Communication Driver sends a payload, even if the original token was still valid. |
|
4888868 |
962872016 |
Requesting an access token was returning a connection failed error. |
Known Issues
There are no known issues in this release of the Communication Drivers Pack.