Windows 10 sensor model & GPS

[Auspicious]

Originally Posted by CarCode

Any Bluetooth GPS is a better solution than a receiver with cable especially when you have a laptop. No driver needed and Bluetooth is supported by any OS.
I have tried the Hamlet also but found it very poor in receiving quality and its other specs. I use now the XGPS 160 SkyPro Bluetooth GPS Receiver from Dual Electronics.

I'm a fan of Bluetooth GPS also. I'm particularly fond of the Bad Elf Pro - it will run plugged in to power and support up to five simultaneous clients. That is a big deal for cruisers that may have a boat computer, a couple of tablets, and guests.



In this instance I was helping someone who was invested in a particular, much less expensive path. It works for a marginal cost of €10. He's happy. Rick (@rgleason) is happy because he has a new victim *ahem* volunteer to help with documentation. I'm happy because I'm learning.

[rgleason]

Dave,
Have you had a chance to revisit this and rewrite our section?

Or alternatively, do you have any suggestions for changes to this section?

Originally Posted by Auspicious
Hi Rick. I'll do the draft you can review it. It's only a couple of pages. The hard work is organization of the material, not writing it.

My customer called me twice today. He is so happy. Impressed with OpenCPN, happy to get the Globalsat GPS puck working, happy that it is working with other software on his laptop. Just happy. *grin*

Still not a fan of Win10 but it is a reality. *grump*


Oh - I developed a relationship with Globalsat tech support who are very aware of OpenCPN and will send them the solution as well. I'll reach out to the GPSReverse people as well. Information is power when shared.

[Auspicious]

Hi Rick,


I emailed you the rewrite. Did you not get it? I can try again.



dave

[rgleason]

Perhaps I did, but could you send it again? I might have missed it, or forgotten. I get a lot of email....

Thanks

Originally Posted by Auspicious

Hi Rick,
I emailed you the rewrite. Did you not get it? I can try again.
dave

[Auspicious]

Resent.

[Argyle38]

Is the current wiki updated on using a Windows 10 usb sensor in Win10x64 system?

Specifically, I just picked up a BU-353W10. As Dave observed, it shows up as a sensor in device manager on a Win10 laptop (purchased as Win10, i.e. not updated). I can get location using the Maps app, but I have no idea if the app is using an internal signal, along with network data, or the external.

Using OpenCPN 5.0. No connect to any position data.

Just wondering if there is any reason on this front to update to 5.2. Didn't see anything obvious regarding Win10 GPS connectivity.

If 5.2 doesn't address the new Windows handeling of GPS devices, do I follow the directions in the Wiki under the "Win8/10 GNSS" protocol?

Has anyone else successfully implemented the new 353W10 with OpenCPN?

-Thanks

[rgleason]

Beware the GPS is captured hostage by any program using it. After verifying the GPS is working, exit the program using it and then get it working with Opencpn.


This was last updated by a document sent by Auspicious 3/2019
https://opencpn.org/wiki/dokuwiki/do..._and_notebooks


If anything has changed, please let us know.

[Argyle38]

Sorry I forgot to get back about this but yes, the instructions in the wiki did work just fine. The instructions on Petr Simons page were sparse, but accurate.

When you follow the instructions for the GeolocationTCP, you just enter the IP address and data port listed and then you're done. You don't touch any other controls in the 'Add Connection' dialog.
I did have to close down CPN and open it back up after setting up the connection, then it worked fine.

Oh and
"Beware the GPS is captured hostage by any program using it."

Yeah, I saw someone mention that on a previous page. Another "WTF Microsoft" moment!

Thanks!

-Argyle