Rif.: Serial COM slow in Win10

[prugno]

I mention the FTDI driver because we need the Virtual COM port driver included in it

[prugno · Accepted solution]

The issue is finally NOT with the serial port, but with a TCP part of the program.
It was nonetheless very difficult to find the source of the problem, again because the program always worked on older PCs. The data from the detectors appeared to be cut at regular intervals.
Please delete the topic if needed.

But thanks to everybody for your time!

[Eric1977]

As I suspected, LabVIEW was not the cause.

Next time, upload an example VI (NOT A IMAGE) of the issue your having if you can't give us your entire code. We we were all trying to give answers and hoping to make them stick.

[prugno]

Indeed it probably is Kaspersky' s fault; I have to wait for the IT guys to proceed and confirm it.
PS i know posting a VI is the first thing to do, but it is strictly forbidden to release any kind of code here: we risk of being fired, too!

Again, thanks everyone

[PTH-POS]

Could you give any updates on this? Did your IT solve the issue? What was the real issue?

I have the same problem, but my IT refuses to believe that windows update 20h2 is the reason...

[prugno]

As far as I remember, the issue was due to the fact that the serial data was streamed via TCP to another Labview application. Now, Windows10 enables (or disables) the Nagle algorithm, and i was overriding it, creating packet lossese.

Good luck!