Hello.

This is to let you know that the version with enhanced tracing is in works, but it is not available yet. It will might be ready next week.

Regards
 

Hello,

it is of course unfortunate that new issues have emerged. We will proceed by extending the tracing/logging as planned, now also with extra focus put on the areas that can be related to these new issues. Please allow some days before we give you the new version and instructions.

Regards
 

Additional notes：

After switching to version 5.84, four machines were unable to subscribe normally, while the others were functioning normally;
```
opc.tcp://10.10.100.121:4840
opc.tcp://10.10.100.120:4840
opc.tcp://10.10.100.113:4840
opc.tcp://10.10.100.112:4840   
```
After rolling back to version 5.83, all machines can subscribe normally

Simon.Yu 
vskysoft.com
2026.5.12 17:29

Hi ,support:

today deploy and found Problem :
(1) use ver 5.84.192(2026.1) ,cann't subscrible tags,but OPC_Srv_ConditionChanged.log display "connected" ;
(2) use ver 5.83 ,can subscrible tags and received valueChanged;（But sometimes the machine fails to reconnect)

**Attachment document ： Bug.zip ** include log files

Simon.Yu
vskysoft.com
2026.5.12 17:24

There were no significant changes to the logging/tracing.
We will go that route if you keep having issues.

Best regards
 

Hi ,support:

    What changes have been made to the output of the log layer in the recent update? Can more details be traced through log control?

I have updated and referenced the latest package source from Nuget, compiled and released it to the customer; 

EasyUAClientOnLogEntry-Trace.log :

$Collector' -> Name: "BaseLib", Version: "5.84.192.1".
Time' -> UtcNow: 05/12/2026 03:33:35, Now: 05/12/2026 11:33:35, TickCount: 592744265.
AssemblyAttributes' -> AssemblyConfiguration: "Release".
ExecutingAssembly' -> FullName: "OpcLabs.BaseLibPrimitives, Version=5.84.192.1, Culture=
AppDomain' -> FriendlyName: "DataCollect.Client", Id: 1.
SystemAssembly' -> FullName: "System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, 
Clr' -> ClrVersion: "8.0.26", PtrSize: 8.

Simon.Yu
2026.5.12 
 

Hello.

We have just released QuickOPC 2026.1. And, it has a relevant change in the reconnection algorithm, related to the issue you reported.
So, the plan is as follows:

1. Rebuild your projects with QuickOPC 2026.1.
2. Retest.
3. If the issue persists, we will proceed as indicated earlier, i.e. giving you individualized instructions/software builds for better diagnostics (tracing etc.).

Best regards
 

Hi,Support :
  Can there be any progress recently?

Look forward to your reply

Simon.Yu
2026.5.6

OK, we will proceed as I have described, i.e. by enhancing the tracing inside QuickOPC. However, be prepared that it will not be ready soon. The preliminary plan is to implement these changes into the release of version 2026.1, for which we are targeting April 2026, or is a subsequent revision.

Regarding the changes you are making, be aware of the following: If your code currently uses EasyUAClient in such a way that each instance is only used to perform operations on one server (endpoint), then setting Isolated = true has, by itself, no effect whatsoever. Setting Isolated = true only has effect on how different EasyUAClient instances access the same endpoint.Regards

At present, the program has been updated and an isolation mechanism has been adopted, with Isolated=true enabled. At the same time, each IP corresponds to a dedicated EasyUaClient instance to check and determine specific high-frequency disconnection anomalies. A timer checks all IP disconnection situations every 5 minutes. If a high-frequency disconnection is found, the EasyUaClient corresponding to the target IP cancels the subscription, releases the object, and then re creates the isolated object and re subscribes;
At present, it seems that there are signs of something taking effect. I will keep updating the progress of these situations until this point, hoping to completely resolve them

Simon.Yu
vskysoft.com
2026.3.11 09:29