[TEST REQUEST] Windows Bluetooth LE build

[Lubomir I. Ivanov]

On Sun, 30 Sep 2018 at 08:56, Dirk Hohndel <dirk at hohndel.org> wrote:
>
> Latest test binary:
>
> http://subsurface-divelog.org/downloads/test/WINBLE-subsurface-4.8.3-12-g2952cd818617.exe
>
>
>
> This basically removes all the Q_OS_WIN code and uses the Linux path for Windows:
>
>

my assumption is that this installer has the QBluetoothDiscoveryAgent
for Windows, patch applied?
perhaps more testing for this is needed by others, but i would suggest
we merge such a patch in master too.

>
> Emit:  "DB:3B:75:83:D8:6E"
>
> Starting download from  BT
>
> qt_ble_open( DB:3B:75:83:D8:6E )
>
> connected to the controller for device DB:3B:75:83:D8:6E
>
>   .. discovering services
>
> Found uuid: "{00001800-0000-1000-8000-00805f9b34fb}"
>
> Found service "{00001800-0000-1000-8000-00805f9b34fb}"
>
> .. created service object QLowEnergyService(0x777bf90)
>
> Found uuid: "{00001801-0000-1000-8000-00805f9b34fb}"
>
> Found service "{00001801-0000-1000-8000-00805f9b34fb}"
>
> .. created service object QLowEnergyService(0x777bee8)
>
> Found uuid: "{fe25c237-0ece-443c-b0aa-e02033e7029d}"
>
> Found service "{fe25c237-0ece-443c-b0aa-e02033e7029d}"
>
> .. created service object QLowEnergyService(0x777bde0)
>
> .. done discovering services
>
> Found service "{00001800-0000-1000-8000-00805f9b34fb}" "Generic Access"
>
> Found service "{00001801-0000-1000-8000-00805f9b34fb}" "Generic Attribute"
>
> Found service "{fe25c237-0ece-443c-b0aa-e02033e7029d}" "Unknown Service"
>
>    c: "{27b7570b-359e-45a3-91bb-cf7e70049bd2}"
>
>         d: "{00002902-0000-1000-8000-00805f9b34fb}"
>
>         d: "{00002901-0000-1000-8000-00805f9b34fb}"
>
> Using service "{fe25c237-0ece-443c-b0aa-e02033e7029d}" as preferred service
>
> .. enabling notifications
>
> Using read characteristic "{27b7570b-359e-45a3-91bb-cf7e70049bd2}"
>
> now writing "0x0100" to the descriptor "{00002902-0000-1000-8000-00805f9b34fb}"
>
> QTime("22:52:48.325") packet SEND "0100ff010400228010c0"
>
> QTime("22:52:48.325") packet WAIT
>
> QTime("22:53:00.326") packet SEND "0100ff0105002e902000c0"
>
> Deleting BLE object
>
> Finishing download thread: "Dive data import error"
>
>
>
>
>
> Looks great discovering services and stuff, but then we time out waiting for a response (and the Teric stays in “CMD WAIT” state).
>
> But we find the device and clearly SOME communication is happening.
>
>

i'm not sure why that is happening.
given the OSTC+ download works i'm going to assume it's our code is
not accommodated to the Teric in the case of the Qt win32 stack.

questions:
- what is the state of Petrel with the the new discovery code
(QBluetoothDiscoveryAgent under Windows)?
- does Teric work on Linux?

>
> Subsurface asks us to pair and if we try to pair that fails (the code was hacked to still allow us to save that address). So my guess is that is where we still have problems (and yes, the Windows 10 Bluetooth manager lists the Teric as paired).
>

i must admit i'm a bit confused. i'm not sure why Subsurface asks to
pair - can you show a screenshot? on Windows the pairing should only
happen via the Control Panel...
the earlier test we did with the small app that tries to connect
worked for the Teric and it connected, means the device is correctly
paired in Control Planel.

at this point, after we discover the address of the device we can just
connect to it and then discover it's services.
address hacks should not be needed.

lubomir
--