subsurface Digest, Vol 107, Issue 22

[Jef Driesen]

On 31/10/2020 17:56, Dirk Hohndel via subsurface wrote:
>> On Oct 31, 2020, at 3:35 AM, Matthias Heinrichs via subsurface <subsurface at subsurface-divelog.org> wrote:
>> BT LE however fails repeatedly with this error:
>>
>> Subsurface: v4.9.7-223-gbd0d7bd0faa1, built with libdivecomputer v0.7.0-devel-Subsurface-NG (3a300a6a8ff81665463e0172e3fc5e0bcc92ec65)
>> [52.768160] INFO: Discover: address=947BE7B0D9F8, name=OSTC4 26
>> [52.768192] INFO: Discover: address=008025E056BD, name=OSTCs 00001
>> [52.768212] INFO: Open: address=008025E056BD, port=0
>> [57.897396] ERROR: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat (10060) [in /__w/subsurface/libdivecomputer/src/socket.c:149 (dc_socket_connect)]
> 
> BLE on Windows is always a pain.
> I assume you went through the 'delete from the OS, reboot, pair again, try again' cycle that is sadly always the first suggestion to fix that?
> I don't have a working BLE based OSTC anymore, so I cannot test with the same hardware, but I will double check one of my Shearwater or Suunto BLE dive computers, again, using the Win64 build.
> I thought I tested that, but there have been so many iterations, I'm no longer 100% sure and this is of course a very important feature...

The above log is from an BT classic (rfcomm) download, and not BLE. Of course 
that doesn't change the fact that it failed, but it's not BLE related. The 
windows error code 10060 is WSAETIMEDOUT.

Jef