GPS-mouse once again

[Ingo_2]

Dear all,

I know that we are having several threads about this or that GPS-system working better/not working with Windows 10.
As I am having 3 different mouses (in fact 4 but 2 of same type) and experimented with different versions of OPENCPN I think it is time to start a new thread again as some results are quite strange.

Let me share my experience before I publish detailed VDR-streams.
As some of you might know I started with and still like the Navilock mouse with Ublox-8 chip. Due to U-Center its working and precision is transparent and manageable if needed. Therefore, it is my preferred basic mouse. But:
- With OpenCPN 4.8 and a Microsoft Com-port driver it is absolute stable (tested 24/7 over 3 weeks). Anchor watch is working perfect.
- The same mouse with the same driver is unstable with OPENCPN 5.2.4. Anchor watch is creating an alarm every seconds to minutes. OPENCPN displays regular disruption of information (red GPS symbol)
- The same mouse is working perfect with Google Earth (claiming to use NMEA and com-port as well).

- A Kendau-Mouse M220 with prolific-driver is working in all conditions (4.8, 5.2.4 and Google Earth)

- A mouse named AdoptSkyTraq Venus 8 with silicon lab driver is not working with OPENCPN but with Google Earth.

In summary Google Earth is working with all mouses but OPENCPN is much more sensitive and in its older version more stable as in the new version.

My feeling is that this is not about the NMEA signal but more about the implementation how to catch the virtual com port.

If someone is willing to investigate this I can offer my support with testing with different mouses.

In order to support the investigation I try to upload the different VDR-records in the following posts.

Regards,
Ingo

[Ingo_2]

Any idea how to share the VDRs as all VDRs despite the empty AdoptSky-version are exceeding the limit of the forum?

[Tehani]

Do you have a Lenovo ?. Some series have problems with the USB ports.

[burgoynebc]

Have a look at device manager for "unknown device" and "serial ball mouse" often the gps puck will show up as a serial ball mouse because the driver is recognized incorrectly. Also download and run "usbdeview" as administrator. It is a free small prog that will show all usb devices that have been registered on windows. You can select all and delete all - on reboot only active devices should show. If your gps units then work, it means it is a driver problem

[Ingo_2]

Originally Posted by burgoynebc

Have a look at device manager for "unknown device" and "serial ball mouse" often the gps puck will show up as a serial ball mouse because the driver is recognized incorrectly. Also download and run "usbdeview" as administrator. It is a free small prog that will show all usb devices that have been registered on windows. You can select all and delete all - on reboot only active devices should show. If your gps units then work, it means it is a driver problem

Hello,
maybe I have not been clear enough. I installed a lot of drivers and what I did not mention is that I used a totally different laptop as well for some cross checks. So, I can ensure it is not about the installation of the driver (however, yes it is about the driver as obviously the different drivers make differences). However, as Google Earth is working in all cases the mouses are working and their drivers are working. So, my conclusion is that the way OPENCPN is picking the data stream of the virtual com port is making a major difference. And 4.8 is different in that respect to 5.2.4 according to the result.

Unfortunately, I have no clue what Google Earth is doing precisely in terms of catching the data stream.

Regards,
Ingo

[wingssail]

Well, I'd turn on the NMEA Debug window on OpenCPN and see if I could catch any anomalies.

I've been using OpenCPN on Windows 10 for a few years and with a variety of devices I have not see any issues. 5.2 seems to work the same as 4.8.

The only problem I've had is when the operating system thinks my GPS is a serial mouse, in which case I have to disable that "mouse" in Device manager, and then the com port signal feeds OpenCPN fine.

[RaymondR]

I had a problem with a BU353 mouse using OpenCPN and after a lot of research found that they had changed the comms chip and had to dig around and find the manufacturer for the new chip version and go to their web site for an updated driver which fixed the problem.