> On Sep 28, 2018, at 7:46 PM, Dirk Hohndel <[email protected]> wrote: > >> >> On Sep 28, 2018, at 7:43 PM, Lubomir I. Ivanov <[email protected]> wrote: >> >> On Sat, 29 Sep 2018 at 05:33, Dirk Hohndel <[email protected]> wrote: >>> >>> >>>> On Sep 28, 2018, at 7:26 PM, Dirk Hohndel <[email protected]> wrote: >>>> >>>> Given the nature of the error message I'm thinking this might be an >>>> unhealthy mix of versions... >>> >>> To test this theory I dug out a Bluetooth dive computer (an original BT-only >>> Shearwater Petrel) and had no problem connecting to it and downloading >>> dives from it. >>> >>> So now I'm no longer sure where the problem might be... >>> >> >> i'm not sure either, but it seems that the OSTC+ works for me using that >> build. >> >> so i guess on your side we have an issue that other users might face as well. >> the device discovery and pairing is problematic on Windows...and i've >> raised that concern before. >> >> i wonder if a restart + removing + adding / pairing the devices would help. >> on my side a restart often helps in cases the device cannot be found. > > So Windows tells me it sees the devices and is paired with both of them. > I tried removing one or the other. Of course they are both very similar. > I'll try another BLE dive computer that I have and see if that will play > along...
I installed Shearwater Cloud on that machine. It immediately connects with both computers. Even while it is scanning, a scan with Subsurface fails /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
