Dual XGPS150A unit and Windows 10

[NWSail]

I purchased a Dual XGPS150A unit for use with OpenCPN running on Windows 10. I purchased this unit because it was listed on the OpenCPN hardware page (second row from the bottom). However, I have been unable to get the unit to show a position in OpenCPN. Windows 10 indicates that it is paired with the unit, the unit appears up under Bluetooth devices and also shows com ports assigned for both input and output. But the XGPS150 unit's blue Bluetooth light flashes at 1 second intervals indicating that it does not think it is connected. Dual has not been very helpful so far in solving this problem. There is documentation telling how to set this device up with earlier versions of Windows but not Windows 10. Those directions are not applicable to Win 10. I'm hoping that there is someone who has an understanding of Bluetooth to OpenCPN protocols might be able to troubleshoot this problem. I have attached a picture of screen shots of Windows 10 settings.

[wdkester]

Your thumbnails aren't legible. Try uploading 1 at a time instead of combining.

[NWSail]

wdkester, thanks for being willing to take a look. Attached are hopefully legible images. Let me know if there is a problem with them.

Ken

[wdkester]

Have you gone to Options>Connections and added a connection for com8 and com9 at the proper baud rate?

[bcn]

And what does the Windows Device Manager say under "COM Ports"?

[NWSail]

Thanks wdkester and bcn for helping to troubleshoot this. To answer your questions:

Windows 10 does not appear to display the baud rate for connected devices. I have spend a lot of time browsing through all the options and properties in Bluetooth settings. The XGPS150 is using com ports 15 (outgoing) and 16 (incoming). It was using lower numbered com ports at first but I have connected and disconnected the unit a few times while trying to get it to connect. As my previous screen shots showed, when I go to Bluetooth settings and select the XGPS device, it says "this device is working properly." However, if I then click Properties under the Events tab there is a message that says "...further installation required." but it gives no clue as to exactly how to accomplish that. I have attached a screen shot of this message. However, I'm not convinced that this is the source of the problem.

Any help you can give me would be very much appreciated!

[CarCode]

Yes, I know, even the latest Windows10 is not able to handle Bluetooth devices correct. I just fired up my virtual Windows10 maschine and saw the desaster. Why the heck these Redmond people are so stupid. Like Windows95 there are still 2 serial ports shown while for this SPP only one is correct. Look a little bit at my pictures. Sadly I only have a german virtual Windows10 maschine but you will understand the pictures. I have connected 2 Bluetooth devices here, one is an AIS receiver (the RO4800 VHF) and the other is a BT GPS device. Both work as expected.
However I guess you have not paired your device correctly. So it will not send any data.

Gerhard

[wdkester]

If they didn't include a test program, you might try something like GPSInfo.

My bluetooth gps runs at 35400 baud.

[CarCode]

Originally Posted by wdkester

If they didn't include a test program, you might try something like GPSInfo.

My bluetooth gps runs at 35400 baud.

Although it doesn't hurt for a Bluetooth connection, the usual baud rate steps are: 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400, 460800 and 921600 but not 35400.

Gerhard

[wdkester]

Originally Posted by wdkester

If they didn't include a test program, you might try something like GPSInfo.

My bluetooth gps runs at 35400 baud.

ooops make that 38400

[wdkester]

NWsail

I haven't tried my BT589 in (my guess) 3-4 months. So I gave it a try and it didn't work on 2 W7 and 1 W8 systems. I went to the little Bluetooth icon in the taskbar and deleted the old BT589. (1) I paired it again with no pass code. It appeared in the BT device display but no com port appeared. So (2) I deleted it and paired it again with the pass code. I don't remember if there was a com port but I thinks so; but no joy again. (3) So I did exactly the same thing as try 2 and it worked.

I read that Windows and BT don't play well together. This would also be my experience. For my use, I will only count on it for a third level backup device.

Do you have it working yet?

[CarCode]

Originally Posted by wdkester

I read that Windows and BT don't play well together. This would also be my experience.

Windows does not play well together with any external device wether BT or USB. You will always have driver problems.

Gerhard

[Three Sisters]

Originally Posted by NWSail

I purchased a Dual XGPS150A unit for use with OpenCPN running on Windows 10. I purchased this unit because it was listed on the OpenCPN hardware page (second row from the bottom). However, I have been unable to get the unit to show a position in OpenCPN. Windows 10 indicates that it is paired with the unit, the unit appears up under Bluetooth devices and also shows com ports assigned for both input and output. But the XGPS150 unit's blue Bluetooth light flashes at 1 second intervals indicating that it does not think it is connected. Dual has not been very helpful so far in solving this problem. There is documentation telling how to set this device up with earlier versions of Windows but not Windows 10. Those directions are not applicable to Win 10. I'm hoping that there is someone who has an understanding of Bluetooth to OpenCPN protocols might be able to troubleshoot this problem. I have attached a picture of screen shots of Windows 10 settings.

Might be your firmware is out of date on the Dual

[champ8242]

I would contact Customer support

cs@dualav.com

Bart

[Tupaia]

Originally Posted by Three Sisters

Might be your firmware is out of date on the Dual

More likely to be a problem with Win 10. Is it an OEM or MS version? I have just chucked a new HP laptop running Win 10 because of poor driver support.

You need to check the BT drivers from both Microsoft and the hardware manufacturer.