Force LE with the same bluetooth dongle works fine on Linux Mint 19.3. I was a bit worried by el cheapo no-name dongle might not support Bluetooth LE but this proves it does.

JB

On 22/06/2020 18:49, Jason Bramwell wrote:

These might be useful.

This is a download when set to Auto, then a download when set to Force LE then a download when set to Force Classic.

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

*From: *Jason Bramwell <mailto:[email protected]>
*Sent: *22 June 2020 18:35
*To: *Dirk Hohndel <mailto:[email protected]>
*Cc: *Subsurface Mailing List <mailto:[email protected]>
*Subject: *RE: Request for testers

I don’t have the same luck, Force LE gives me

Putting it back to Auto for Force Classic immediately restored functionality.

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

*From: *Dirk Hohndel <mailto:[email protected]>
*Sent: *22 June 2020 17:28
*To: *Jason Bramwell <mailto:[email protected]>
*Cc: *Subsurface Mailing List <mailto:[email protected]>
*Subject: *Re: Request for testers

BTW, Lubomir was able to test and responded on the GitHub PR that for him this works. So I have high hopes that this will work for you as well.

If you have the time, I would REALLY appreciate a second test, though.

/D

    On Jun 22, 2020, at 9:23 AM, Dirk Hohndel via subsurface
    <[email protected]
    <mailto:[email protected]>> wrote:

    Now comes the important question. If you try the OSTCs again, but
    in the Download UI select the "BLE only" option, does it still
    work? The way to do this is to switch "Bluetooth mode" in the
    "Remove Bluetooth device selection" dialog to "Force LE".

    IIRC the OSTCs are both dual stack BT & BLE dive computers. And
    it's the BLE part that failed for me when I tested this here :-(

    /D

        On Jun 22, 2020, at 6:28 AM, Jason Bramwell via subsurface
        <[email protected]
        <mailto:[email protected]>> wrote:

        Petrel has Bluetooth connectivity and it’s downloading
        information but it says error parsing the header for each of
        the dives. This has not been used for a very long time and has
        had firmware updated multiple times since it was last used so
        this is possible a red herring.

        OSTC Plus-Sport didn’t want to connect initially but after I
        removed the pairing I had on the computer from previously it
        paired up and downloaded fine.

        OSTC Plus-Tech paired up and downloaded fine (this is newer
        than the OSTS Plus with sport firmware so it hadn’t been
        paired previously).

        Upon retrying the download from both the OSTC’s they download
        straight away without having to mess about at all.

        JB

_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to