On 10 June 2018 at 03:26, Dirk Hohndel <d...@hohndel.org> wrote: > >> On Jun 9, 2018, at 4:59 PM, Linus Torvalds <torva...@linux-foundation.org> >> wrote: > > IIRC that depends on how Qt is built. Since Lubomir builds his own > Qt for this purpose, we should be able to adjust this behavior > >> I wonder if we should just add data debugging to our >> characteristcStateChanged() and characteristicWritten() functions, >> just so that we'd get that packet output even when Qt doesn't do it. > > I think that would be smart especially for new BLE devices >
so by enabling debug output for the read(), write(), characteristicWritten() and characteristcStateChanged() and i get this: <snip> Found uuid: "{53544d54-4552-494f-5345-525631303030}" Found service "{53544d54-4552-494f-5345-525631303030}" .. done discovering services .. discovering details .. enabling notifications BLE write completed BLE write completed characteristicWritten "{00000003-0000-1000-8000-008025000000}" "ff" INFO: dc_device_open error value of 0 write "\xBB" [14.768589] ERROR: Failed to receive the echo. [in hw_ostc3.c:295 (hw_ostc3_transfer)] [14.769031] ERROR: Failed to send the command. [in hw_ostc3.c:455 (hw_ostc3_device_init_download)] Deleting BLE object Finishing the thread Dive data import error dives downloaded 0 uploading updated version. the OSTC+ itself says "Download mode enabled" right after the "Download button" is pressed. lubomir -- _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface