> On Sep 30, 2018, at 6:20 PM, Dirk Hohndel <[email protected]> wrote: >> this comes directly from the Windows GATT backend for writing descriptors. >> https://docs.microsoft.com/en-us/windows/desktop/api/bluetoothleapis/nf-bluetoothleapis-bluetoothgattsetdescriptorvalue >> >> ERROR_SEM_TIMEOUT can happen in a case where the service path is >> already opened in another process and this process has acquired an >> exclusive lock on the path. >> for instance, this can happen if i start BLE Explorer, connect to the >> same device and start changing values in a service. then run the >> qt-bt-discovery test app and try to do the same while both apps are >> running. > > OK, I don't have BLE Explorer. I do have the settings app open, though. > And I am not 100% sure if I maybe had Subsurface open as well - but > that shouldn't have been in BLE mode. > > Let me reboot again to make sure nothing else is running and try from there
Rebooted. Nothing else running, just the cmd.exe Same output - semaphore timeout period has expired. /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
