friissoren
commented
1 year ago The log trace you copied seems okay.
Are you using sudo when starting the transmission?
I just tried with two USB Bluetooth modules that I had lying here. The tiny one on the left side gives the following dmesg trace when plugging it in:
[ 584.179072] usb 1-7: new full-speed USB device number 38 using xhci_hcd
[ 584.328345] usb 1-7: New USB device found, idVendor=0bda, idProduct=8771, bcdDevice= 2.00
[ 584.328357] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 584.328362] usb 1-7: Product: Bluetooth Radio
[ 584.328365] usb 1-7: Manufacturer: Realtek
[ 584.328368] usb 1-7: SerialNumber: 00E04C239987
[ 584.333049] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 584.334015] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 584.334028] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 584.334142] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 584.334191] Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814
[ 584.474026] Bluetooth: hci0: RTL: fw version 0x09a98a6bAnd the other one gives this:
[ 903.559374] usb 1-7: new full-speed USB device number 39 using xhci_hcd
[ 903.708687] usb 1-7: New USB device found, idVendor=0bda, idProduct=8771, bcdDevice= 2.00
[ 903.708699] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 903.708703] usb 1-7: Product: Bluetooth Radio
[ 903.708707] usb 1-7: Manufacturer: Realtek
[ 903.708710] usb 1-7: SerialNumber: 00E04C239987
[ 903.713057] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 903.713988] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 903.714005] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 903.714129] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 903.714185] Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814
[ 903.854059] Bluetooth: hci0: RTL: fw version 0x09a98a6bI.e. the same. They must have the same chip internally.
Both of these were able to get data through to a Samsung Galaxy S10 phone, using the sudo ./transmit 5 p command (and sudo ./transmit l). However, I did notice that doing sudo ./transmit 5 did not work for some reason. I am not sure but I seem to have a recollection that this last command did work with the Bluetooth chipset that was built into the Z490 motherboard I had some time ago.
They are both ordered from China/AliExpress. The tiny one didn't have any packaging when it arrived.
That ONVIAN dongle with the chipset RTL8761B, that is mentioned, was something that one other user tried. I don't have that exact HW myself. However, based on his comment, I ordered those two other dongles, since they seemed to match the chipset.
MichiganBroadband
gabrielcox
cospan
In summary BT5 long range test does not work or show up in android remoteID apps that I am testing. It transmits something And it does show up in NRF Connect app on my Android phone.
Phone is a Samsung S23ultra.
OpendroneID app says it is supporting Coded Phy and Extended Advertising.
But nothing shows up in the APP when "I transmit 5 p". When testing transmit, NRF Connect APP on phone shows MAC, signal, Device type:(unknown), Advertising type: Bluetooth Advertising Extension, Data status: Complete, Primary PHY:LE Coded, Secondary PHY: LE Coded, AdvertisingSet ID:0 So it seems to be "working" transmitting something but not showing up in the remoteid android apps that I have tested. Transmitter is using "A BT5 USB adapter/dongle of the brand ONVIAN and with the chipset RTL8761B" As is mentioned in the Readme here.
While transmitting displayed is: ./transmit 5 p Supported Low Energy Bluetooth features: Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Supported Low Energy Bluetooth features: Features: 0xbd 0x5f 0x66 0x00 0x00 0x00 0x00 0x00 LE Encryption Extended Reject Indication Slave-initiated Features Exchange LE Ping LE Data Packet Length Extension Extended Scanner Filter Policies LE 2M PHY Stable Modulation Index - Transmitter Stable Modulation Index - Receiver LE Coded PHY LE Extended Advertising Channel Selection Algorithm #2 Connection CTE Request Connection CTE Response Antenna Switching During CTE Transmission (AoD) Antenna Switching During CTE Reception (AoA) Supported Low Energy Bluetooth features: Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 The transmit power is set to 0 dBm
I also sent Gabriel an email that I am interested in participating here. My email to him contained some additional (and repeated) details as follows:
I was able to get the Linux transmitter to work.
It works on Bluetooth 4,
but is not working on bluetooth5 Long Range + Extended Advertising Which is of course what I am most interested in.
I can tell that the Bluetooth radio is actually transmitting something when I "transmit 5 p" or "transmit 5" As I have a spectrum analyzer and microwave audible power envelope detector nearby.
I am using the Android OPenDroneID 3.4.3 app on a Samsung S23 And also using DroneScanner (dronetag) v1.5.2
Both apps decode/display properly when I "transmit l"
I am using a common/popular Realtek USB BT5 adaptor.
A RTL8761B as is mentioned worked in the documentation for Linux Transmitter.
I am looking to participate and may need a little help on software matters.
Right now I'm not sure why the BT5 functions are not working as expected.
If you have access to- or try this hardware on your end there is a current bug in Debian that requires you to switch firmware files. But it seems to work fine after you do this.
See: https://bugs.kali.org/view.php?id=8216
Also I believe I am testing with identical hardware that is referenced as working at : https://github.com/opendroneid/transmitter-linux
"A BT5 USB adapter/dongle of the brand ONVIAN and with the chipset RTL8761B has been tested on a PC with Ubuntu 20.04 and proven to be able to successfully transmit in Long Range mode."
Mine is the same and even same brand.