High CPU usage - u-blox virtual COM port

[H29.5Upgrade]

u-blox M8 High CPU usage with OpenCPN
Hello, I have a u-blox 8 GPS built into my laptop and have the u-blox virtual COM port running. When I connect using OpenCPN, my laptops CPU usage goes up to 35% and stays there (draining batteries very fast). The issue seems to be the way the data is gathered from the Virtual COMM port. I have tried other readers such as PuTTY and Terminal and a reader from Panasonic. PuTTY has the same issue as OpenCPN: CPU usage is 35%. Terminal and the Panasonic program use less than 1% CPU. A have tested two versions of the Virtual COMM port driver from u-blox (ver: 2.0.1.3 and ver: 3.10.0.0) the latter is worse, it's less CPU usage on OpenCPN but extremely high CPU usage on Windows Driver Foundation process... I had the same problem in January and got it fixed by a technician at Panasonic, then Windows decided it needed to update it self again... Please help if you can, Thank you, John
My PC Info:

Windown 10: version 21H1 (OS Build 19043.1081)

COM 3, u-blox Virtual COM Port (COM3)
Driver Provider: u-blox AG
Driver Date: 2/12/2013
Driver Version: 2.1.0.3

Sensor u-blox GNSS Sensor
Divice Type: Sensors
Manufacturer: u-blox
Location: Port_#0009.Hun_#0001

[champ8242]

To start with, I dont have a W10 system with a build-in GPS receiver. I do have multiple u-blox GPS/GNSS receivers around. All with a USB connection and I see no significant increase in the CPU usage when using a GPS receiver.
I do not have any u-blox (virtual port) driver installed. They run out of the b(l)ox

The problem you might have is the "build-in GPS receiver" together with the u-blox virtual driver.

Microsoft changed its vision years ago on comm ports and GPS receivers. They see them now as sensors and specifically with the GPS receiver becoming a "location sensor". This sensor is completely integrated within the OS.

What you might try to do is:
Replacing the u-blox USB-to-COM port driver by the Microsoft USB Serial Device driver. This modification will disable the Windows Location service, as the complete u-blox driver set is no longer able to participate.

This could be a solution, not sure.

Bart

[mgrouch]

If it is ublox and you are using it in binary mode try switching it into NMEA mode. I’ve noticed lower CPU usages in NMEA mode.