question
Bluetooth BTHUSB error ID (3,5,18 or 34) crash dongle and/or USB ports
Hi!
After working for several hours, we will get an BTHUSB ID5 (or other error) from the Bluetooth driver. Sometimes the Bluetooth can recover, other times it freezes and only a REBOOT of the PC will get the usb working again. Neither Devcon reset/disable, nor physically removing the dongle and inserting it back in allows the usb ports to work. furthermore, any USB device inserted after the error will not work until a reboot is performed.
I’m attaching windows logs, event viewer logs as well as a simple CS file where we scan for BLE advertisements, read services and characteristics, then disconnect. Run this example for a few hours with several peripherals and you will crash as well.
Were using inter NUCs, windows 10. latest BIOS and BLE drivers. This happens with different BLE dongles, with different chipsets, so I don’t think the dongle is the cause.
We use Windows.Devices.Bluetooth under UWP and are having many issues related to the BLE drivers.
Here is a link to logs, event viewer errors and a simple C# program which if you run vs more than 1 peripheral, will produce the issue within a few hours.
https://drive.google.com/drive/folders/1SOlwDnTWeap6HyG7g6ZbPqGKazF3Z0O0?usp=sharing
Could share uwp sample, and could tell more detail about under UWP and are having many issues related to the BLE drivers?
Hi NicoZhu, thank you for responding and sorry for my delay!
We’re developing a product where one or more ‘centrals’ communicate with a few dozen ‘peripherals’ over bluetooth BLE protocol. Most connections very little info is passed (
200 bytes), but rarely more info is passed between them (
5000 bytes). Between communications the peripherals ‘Sleep’ (i.e they are in very low power consumption and are not advertising). The centrals run constantly. We use PCs and Nucs running our software and using BLE dongles from different manufacturers with different chipsets to provide us with BLE capability.
On all devices we run, different errors are generated from the BLE drivers at different times. BTHUSB errors (IDs 3,5,18 and 34 so far) cause the Bluettoth communication to stop until a system reboot is performed. Other errors include invalid RSSI value reads (-127 or high positive values like +80), but this issue is less important.
Any pointers will be greatly appreciated!
Thanks!
Thanks for your info, I will check above that and test it.
Scrap 2nd.
Header
Scrap 2nd.
en[EVENT34] Cancel power saving setting of power management of Bluetooth HID device
Event ID 34, BTHUSB warning log was recorded.
This is a warning related to power management of Bluetooth HID devices.
If your Bluetooth mouse disconnects frequently, following the steps described may help.
However, logging may not stop.
Event Log
| message | Local adapter does not support critical low energy controller states to support ambient mode. The minimum required state mask supported is 0x491f7fffff, but I got 0x1fffffff. The low energy peripheral roll feature is disabled. |
| The name of the log | system |
| Source | BTHUSB |
| Event id | 34 |
| level | warning |
| user | N /A |
Steps to change Bluetooth HID device settings
Open the power management options under Bluetooth HID Devices and turn off power saving settings.
Do not mistake the device to be set
Multiple Bluetooth devices are displayed.
This article applies to the following devices:
| 〇 | Human Interface Device> Bluetooth HID Device |
| × | Bluetooth |
