Hi,
My name is Steve and I am located in Ann Arbor Michigan USA.
I am new bluetooth LE and lately am obsessed with Bluetooth LE beacons and trying them out.
I have read article after article and page after page about how people have setup up beacons with USB BT 4.0 interfaces
as well as serial bluetooth boards.
I am currently experimenting with a beacon running on a Raspberry Pi-B and using an external USB Bluetooth 4.0 class 1 dongle.
My frustration is that I have not been able to find any useful information in how to change the Transmitter power level when in
LE mode.
The dongle appears to be working at default level below zero dbm.
The whole point of building your own beacon this way is to be able to customize it and setting the power level is an important key item
that should be easily accessible yet I find that NOBODY ever even mentions it let alone do they explain or provide a way to set the power.
Every text that I have found that details beacon setups from command line never bother to mention setting beacon TX power.
All the pages I have found seem to copy each other and repeat the same information over & over
But never get around to even mentioning or discussing setting the power output level of the blutooth dongle.
sudo hcitool -i hci0 cmd 0x08 0x0008 1E 02 01 1A 1A FF 4C 00 02 15 [ 92 77 83 0A B2 EB 49 0F A1 DD 7F E3 8C 49 2E DE ] [ 00 00 ] [ 00 00 ] C5 00
The byte just left of the last one is the "reported" TX level that you are transmitting at.
Which means you're supposed to know (or guess?) what dbm level you are actually transmitting at and set it here to display to the world what your transmitter level is set to so they can range (guess or estimate distance from TX).
This value does not influence or reflect actual transmit power.
Please help!!
Could use any pointers.
I'm a hardware guy as well so not very experienced in software/programming but I'm willing to try anything to get control of this.
Been at this for over a week and have some working beacons but no control of transmit power level.
Am using Trendnet USB dongles which appear to use a Cambridge Chip. But I'm not exactly sure which chip.
:~# lsusb
Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
root@raspberrypi:~# hciconfig hci0
hci0:?? Type: BR/EDR? Bus: USB
??????? BD Address: 00:15:83:EA:0A:B9? ACL MTU: 310:10? SCO MTU: 64:8
??????? UP RUNNING
??????? RX bytes:780 acl:0 sco:0 events:50 errors:0
??????? TX bytes:1110 acl:0 sco:0 commands:50 errors:0
VGhhbmtzLCAgDQpJIHdhcyBob3BpbmcgdGhlcmUgd2FzIGFuIGVhc2llciB3YXkgYW5kIHNvbWVo
b3cgYXQgdGhlIGNvbW1hbmQgbGluZSBidXQgSSdsbCBkbyB3aGF0IEkgbmVlZCB0byBkbyBhbmQg
ZmlndXJlIGl0IG91dCBzb21laG93LiAgDQpJIHVzdWFsbHkgZW5kIHVwIG9uIDEwIG90aGVyIHJh
YmJpdCB0cmFpbHMgd2hlbiBpdCBjb21lcyB0byBoYXZpbmcgdG8gcmVjb21waWxlIGFueXRoaW5n
IGJlY2F1c2UgaXQgdXN1YWxseSBqdXN0IGZhaWxzIGZvciBtZSBhbmQgSSdtIA0Kbm90IHlldCB3
ZWxsIHZlcnNlZCBpbiB0cm91Ymxlc2hvb3Rpbmcgd2hlbiB0aGluZ3Mgd29uJ3QgY29tcGlsZSBz
dWNjZXNzZnVsbHkgYXNpZGUgZnJvbSB3aGF0IEkgY2FuIGVhc2lseSBnb29nbGUuICANCg0KSSBh
bHNvIHRoaW5rIGl0J3MgYSBsaXR0bGUgbW9yZSBjb21wbGljYXRlZCB0aGFuIGp1c3Qgc2V0dGlu
ZyB0aGUgcG93ZXIuICANCkkgaGF2ZSBnYXRoZXJlZCBhdCBsZWFzdCB3aXQgaHRoZSBDU1IgY2hp
cHNldCB0aGF0IHRoZXJlIGFyZSBhdCBsZWFzdCAzIHNlcGFyYXRlIHBvd2VyIHNldHRpbmdzIHRo
YXQgY2FuIGJlIGFkanVzdGVkIGFuZCBub3QgYW55IG92ZXJhbGwgcG93ZXIgc2V0dGluZy4gIA0K
U28gdGhlIHZhcmlvdXMgbW9kdWxhdGlvbiBtb2RlcyAoaW5jbHVkaW5nIEdGU0sgLUxFIGFkdmVy
dGlzaW5nLSkgbmVlZCB0byBiZSBhZGRyZXNzZWQgYW5kIHNldCBpbmRpdmlkdWFsbHkuICANClRo
ZXJlJ3Mgbm90IGEgbWFzdGVyIHRyYW5zbWl0IGxldmVsIHRoYXQgc2V0cyB0aGVtIGFsbC4NCiAg
DQoNClN0ZXZlIEdsYWRkZW4NCsKgDQpNaWNoaWdhbiBCcm9hZGJhbmQgU3lzdGVtcw0KQ29ubmVj
dGluZyBZb3VyIEJ1c2luZXNzIQ0KDQoNCg0KKzEgNzM0LjUyNy43MTUwIERpcmVjdA0KKzEgMjQ4
LjMyNy40Mzg5IEZheA0Kc3RldmVAbWljaGlnYW5icm9hZGJhbmQuY29tDQp3d3cubWljaGlnYW5i
cm9hZGJhbmQuY29tDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBIaWV1IExl
IFttYWlsdG86aGlldS5sZUB2ZXJpa3N5c3RlbXMuY29tXSANClNlbnQ6IFdlZG5lc2RheSwgT2N0
b2JlciAxMiwgMjAxNiAxOjAwIEFNDQpUbzogU3RldmUgR2xhZGRlbg0KQ2M6IEJhcnJ5IEJ5Zm9y
ZDsgbGludXgtYmx1ZXRvb3RoQHZnZXIua2VybmVsLm9yZw0KU3ViamVjdDogUmU6IEhvdyBjYW4g
eW91IHNldCBUcmFuc21pdCBwb3dlciBsZXZlbCBpbiBCbHVldG9vdGggTEUgbW9kZSBmb3IgYW4g
TEUgYmVhY29uPw0KDQpIaSwNCg0KSW4gbXkgb3BpbmlvbiwgdGhlIG9ubHkgd2F5IEkgY2FuIGZp
bmQgdG8gaW5jcmVhc2UgdGhlIHR4X3Bvd2VyIGlzIHRvIHJlY29tcGlsZSB0aGUgbGludXgga2Vy
bmVsLiBUaGVyZSBtYXkgYmUgYSBiZXR0ZXIgd2F5DQoNCkl0IHNlZW1zIHRoYXQgYmx1ZXRvb3Ro
IHN0YWNrIHdpdGhpbiBrZXJuZWwgc2VwYXJhdGVkIGludG8gdHdvIGNsYXNzZXM6DQoxLiBJbnF1
aXJ5IFR4X3Bvd2VyLg0KMi4gQWR2ZXJ0aXNlIFR4X3Bvd2VyLg0KDQpBbmQgdGhlIGRlZmF1bHQg
dmFsdWUgaXMgMC4NCg0KWW91IGNhbiB0YWtlIGEgbG9vayBhdDoNCipoY2lfYWxsb2NfZGV2KHZv
aWQpICBmdW5jdGlvbiB3aXRoaW4gbmV0L2JsdWV0b290aC9oY2lfY29yZS5jIGZpbGUNCmhkZXYt
PmlucV90eF9wb3dlciA9IEhDSV9UWF9QT1dFUl9JTlZBTElEOyBhZHZfdHhfcG93ZXIgPSANCmhk
ZXYtPkhDSV9UWF9QT1dFUl9JTlZBTElEOw0KDQpIb3BlIGl0IHdpbGwgYmUgaGVscGZ1bCB0byB5
b3UuDQoNClJlZ2FyZHMsDQpIaWV1Lg0KDQpPbiBXZWQsIE9jdCAxMiwgMjAxNiBhdCAxMjo1MiBB
TSwgU3RldmUgR2xhZGRlbiA8c3RldmVAbWljaGlnYW5icm9hZGJhbmQuY29tPiB3cm90ZToNCj4g
VGhhbmtzISENCj4gWWVzIGl0J3MgbmljZSB0byBoZWFyIGZyb20gc29tZWJvZHkuDQo+DQo+IEkn
dmUgYmVlbiBzY291cmluZyB0aGUgd2ViIHNvIGZhciB0byBubyBhdmFpbCBvbiB3aGF0IEkgdGhp
bmsgc2hvdWxkIGJlIGEgc2ltcGxlIGFuZCBhY2Nlc3NpYmxlIHNldHRpbmcuDQo+IEl0J3Mgb2J2
aW91cyBmcm9tIHRoZSBzcGVjcyB0aGF0IG1vc3QgY2hpcHMgaGF2ZSBhIHByb2dyYW1tYWJsZSAo
c2V0dGFibGUpIHRyYW5zbWl0dGVyIHBvd2VyLg0KPiBBbmQgd2l0aCBiZWFjb25zIGl0IGlzIHZl
cnkgaW1wb3J0YW50IGFuZCBleHBlY3RlZCB0aGF0IG9uZSBzaG91bGQgYmUgYWJsZSB0byBhZGp1
c3QgdGhlIHRyYW5zbWl0dGVyIGxldmVsLg0KPiBBbGwgb2YgdGhlIHNlcmlhbCBib2FyZHMgZG8g
aXQgd2l0aCBzaW1wbGUgQVQgY29tbWFuZHMuDQo+DQo+IEkganVzdCBkb24ndCBnZXQgd2h5IHRo
ZXJlJ3Mgbm8gZG9jdW1lbnRhdGlvbiBvbiBob3cgdG8gZG8gaXQgd2l0aCBhIFVTQiBkZXZpY2Uh
IQ0KPg0KPiBUaGV5IHNlbGwgY2xhc3MgMSBibHVldG9vdGggdXNiIGRvbmdsZXMgZm9yIGFwcGxp
Y2F0aW9ucyB0aGF0IHJlcXVpcmUgbW9yZSByYW5nZSAoMTAwbSkgaXMgcXVvdGVkIG9uIG1vc3Qg
Y2xhc3MgMSBwcm9kdWN0cy4NCj4NCj4gSSdkIGV4cGVjdCB0aGVyZSBzaG91bGQgYmUgYSBzdHJh
aWdodCBmb3J3YXJkIGVhc3kgdG8gc2V0IHBvd2VyIGluIExFIG1vZGUgdG8gZ2V0IG1vcmUgcmFu
Z2Ugb3Igc2F2ZSBwb3dlciBhbmQgbGltaXQgcmFuZ2Ugd2hlbiB3YW50ZWQuDQo+DQo+IEJ1dCBJ
J20gcmVhbGx5IG5vdCBmaW5kaW5nIHRoaXMgaW5mb3JtYXRpb24gb3V0IHRoZXJlIQ0KPg0KPiBJ
IGRvbjt0IHVuZGVyc3RhbmQgd2hhdCBJIGFtIGRvaW5nIHdyb25nIG9yIHdoeSB0aGlzIGlzIHNv
IGRpZmZpY3VsdCANCj4gdG8gZmluZC4gIDopDQo+DQo+DQo+DQo+DQo+DQo+DQo+DQo+IE9uIDEx
IE9jdG9iZXIgMjAxNiBhdCAxNzo1MCwgU3RldmUgR2xhZGRlbiA8c3RldmVAbWljaGlnYW5icm9h
ZGJhbmQuY29tPiB3cm90ZToNCj4+IElzIHRoaXMgdGhpcyBsaXN0IGp1c3Qgc29tZSBraW5kIG9m
IGF1dG9tYXRlZCBwYXRjaCBhbm5vdW5jZW1lbnQgbG9nIGFuZCBub3QgYW4gYWN0dWFsIG1haWxp
bmcgbGlzdCB3aGVyZSB5b3UgY2FuIGFzayBhbnl0aGluZyBhYm91dCBibHVldG9vdGguDQo+PiBU
aGlzIGlzIGFsbCBJIGhhdmUgc2VlbiBoZXJlIGZvciB0aGUgcGFzdCBmZXcgZGF5cz8NCj4+IFdo
ZXJlIGNhbiBJIGFzayBhbiBhY3R1YWwgcXVlc3Rpb24gYWJvdXQgYmx1ZXRvb3RoPw0KPg0KPiBU
aGVyZSBhcmUgc29tZSByZWFsIGh1bWFucyBoZXJlIHRvbyEgIDotKQ0KPg0KPiBJZiB5b3UgbG9v
ayBiYWNrIG9uIHRoZSBhcmNoaXZlIG9mIHRoaXMgbGlzdCB5b3Ugd2lsbCBzZWUgYSBtaXh0dXJl
IG9mIA0KPiBxdWVzdGlvbnMgYW5kIHBhdGNoIHJlcXVlc3RzLg0KPiBtYXJjLmluZm8vP2w9bGlu
dXgtYmx1ZXRvb3RoDQo+DQo+IEkndmUga2VwdCBxdWlldCBhcyBJJ20gbm90IHN1cmUgSSBjYW4g
YW5zd2VyIHF1ZXN0aW9ucy4gVG8gb2ZmZXIgc29tZSANCj4gc2hhcmVkIGV4cGVyaWVuY2UsIEkg
Y2FuIHNheSB0aGF0IEkndmUgYmVlbiBleHBlcmltZW50aW5nIHdpdGgNCj4gKEVkZHlzdG9uZSkg
YmVhY29ucyBvbiBMaW51eCBzaW5nbGUgYm9hcmQgY29tcHV0ZXJzIGFjY2Vzc2luZyBCbHVlWiAN
Cj4gdGhyb3VnaCB0aGUgREJ1cyBBUEkgdXNpbmcgUHl0aG9uLiBJIGFsc28gaGF2ZSBub3QgZm91
bmQgYSB3YXkgdG8gDQo+IGNoYW5nZSB0aGUgcG93ZXIgbGV2ZWwgb2YgYWR2ZXJ0aXNlbWVudHMg
ZWl0aGVyLiBGb3Igd2hhdCBJJ20gZG9pbmcsIA0KPiBqdXN0IG1ha2luZyBzdXJlIHRoZSBUWCBw
b3dlciBpbiB0aGUgRWRkeXN0b25lIGFkdmVydCBtYXRjaGVzIHdoYXQgdGhlIA0KPiBkb25nbGUg
aXMgYWN0dWFsbHkgYnJvYWRjYXN0aW5nIGhhcyBiZWVuIGdvb2QgZW5vdWdoLg0KPg0KPiBTb3Jy
eSBJIGNvdWxkbid0IGJlIG9mIG1vcmUgaGVscC4NCj4NCj4gUmVnYXJkcywNCj4gQmFycnkNCj4N
Cj4+DQo+Pg0KPj4NCj4+DQo+PiBTdGV2ZSBHbGFkZGVuDQo+Pg0KPj4gTWljaGlnYW4gQnJvYWRi
YW5kIFN5c3RlbXMNCj4+IENvbm5lY3RpbmcgWW91ciBCdXNpbmVzcyENCj4+DQo+Pg0KPj4NCj4+
ICsxIDczNC41MjcuNzE1MCBEaXJlY3QNCj4+ICsxIDI0OC4zMjcuNDM4OSBGYXgNCj4+IHN0ZXZl
QG1pY2hpZ2FuYnJvYWRiYW5kLmNvbQ0KPj4gd3d3Lm1pY2hpZ2FuYnJvYWRiYW5kLmNvbQ0KPj4N
Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IEZyb206IFN0
ZXZlIEdsYWRkZW4NCj4+IFNlbnQ6IFN1bmRheSwgT2N0b2JlciAwOSwgMjAxNiAxMjoxMSBQTQ0K
Pj4gVG86IGxpbnV4LWJsdWV0b290aEB2Z2VyLmtlcm5lbC5vcmcNCj4+IFN1YmplY3Q6IEhvdyBj
YW4geW91IHNldCBUcmFuc21pdCBwb3dlciBsZXZlbCBpbiBCbHVldG9vdGggTEUgbW9kZSBmb3Ig
YW4gTEUgYmVhY29uPw0KPj4NCj4+IEhpLA0KPj4gTXkgbmFtZSBpcyBTdGV2ZSBhbmQgSSBhbSBs
b2NhdGVkIGluIEFubiBBcmJvciBNaWNoaWdhbiBVU0EuDQo+Pg0KPj4gSSBhbSBuZXcgIGJsdWV0
b290aCBMRSBhbmQgbGF0ZWx5IGFtIG9ic2Vzc2VkIHdpdGggQmx1ZXRvb3RoIExFIGJlYWNvbnMg
YW5kIHRyeWluZyB0aGVtIG91dC4NCj4+DQo+PiBJIGhhdmUgcmVhZCBhcnRpY2xlIGFmdGVyIGFy
dGljbGUgYW5kIHBhZ2UgYWZ0ZXIgcGFnZSBhYm91dCBob3cgDQo+PiBwZW9wbGUgaGF2ZSBzZXR1
cCB1cCBiZWFjb25zIHdpdGggVVNCIEJUIDQuMCBpbnRlcmZhY2VzIGFzIHdlbGwgYXMgc2VyaWFs
IGJsdWV0b290aCBib2FyZHMuDQo+Pg0KPj4gSSBhbSBjdXJyZW50bHkgZXhwZXJpbWVudGluZyB3
aXRoIGEgYmVhY29uIHJ1bm5pbmcgb24gYSBSYXNwYmVycnkgUGktQiBhbmQgdXNpbmcgYW4gZXh0
ZXJuYWwgVVNCIEJsdWV0b290aCA0LjAgY2xhc3MgMSBkb25nbGUuDQo+Pg0KPj4gTXkgZnJ1c3Ry
YXRpb24gaXMgdGhhdCBJIGhhdmUgbm90IGJlZW4gYWJsZSB0byBmaW5kIGFueSB1c2VmdWwgDQo+
PiBpbmZvcm1hdGlvbiBpbiBob3cgdG8gY2hhbmdlIHRoZSBUcmFuc21pdHRlciBwb3dlciBsZXZl
bCB3aGVuIGluIExFIG1vZGUuDQo+Pg0KPj4gVGhlIGRvbmdsZSBhcHBlYXJzIHRvIGJlIHdvcmtp
bmcgYXQgZGVmYXVsdCBsZXZlbCBiZWxvdyB6ZXJvIGRibS4NCj4+DQo+PiBUaGUgd2hvbGUgcG9p
bnQgb2YgYnVpbGRpbmcgeW91ciBvd24gYmVhY29uIHRoaXMgd2F5IGlzIHRvIGJlIGFibGUgdG8g
DQo+PiBjdXN0b21pemUgaXQgYW5kIHNldHRpbmcgdGhlIHBvd2VyIGxldmVsIGlzIGFuIGltcG9y
dGFudCBrZXkgaXRlbSB0aGF0IHNob3VsZCBiZSBlYXNpbHkgYWNjZXNzaWJsZSB5ZXQgSSBmaW5k
IHRoYXQgTk9CT0RZIGV2ZXIgZXZlbiBtZW50aW9ucyBpdCBsZXQgYWxvbmUgZG8gdGhleSBleHBs
YWluIG9yIHByb3ZpZGUgYSB3YXkgdG8gc2V0IHRoZSBwb3dlci4NCj4+DQo+Pg0KPj4gRXZlcnkg
dGV4dCB0aGF0IEkgaGF2ZSBmb3VuZCB0aGF0IGRldGFpbHMgYmVhY29uIHNldHVwcyBmcm9tIGNv
bW1hbmQgbGluZSBuZXZlciBib3RoZXIgdG8gbWVudGlvbiBzZXR0aW5nIGJlYWNvbiBUWCBwb3dl
ci4NCj4+DQo+PiBBbGwgdGhlIHBhZ2VzIEkgaGF2ZSBmb3VuZCBzZWVtIHRvIGNvcHkgZWFjaCBv
dGhlciBhbmQgcmVwZWF0IHRoZSANCj4+IHNhbWUgaW5mb3JtYXRpb24gb3ZlciAmIG92ZXIgQnV0
IG5ldmVyIGdldCBhcm91bmQgdG8gZXZlbiBtZW50aW9uaW5nIG9yIGRpc2N1c3Npbmcgc2V0dGlu
ZyB0aGUgcG93ZXIgb3V0cHV0IGxldmVsIG9mIHRoZSBibHV0b290aCBkb25nbGUuDQo+Pg0KPj4g
c3VkbyBoY2l0b29sIC1pIGhjaTAgY21kIDB4MDggMHgwMDA4IDFFIDAyIDAxIDFBIDFBIEZGIDRD
IDAwIDAyIDE1IFsgDQo+PiA5MiA3NyA4MyAwQSBCMiBFQiA0OSAwRiBBMSBERCA3RiBFMyA4QyA0
OSAyRSBERSBdIFsgMDAgMDAgXSBbIDAwIDAwIF0gDQo+PiBDNSAwMA0KPj4NCj4+IFRoZSBieXRl
IGp1c3QgbGVmdCBvZiB0aGUgbGFzdCBvbmUgaXMgdGhlICJyZXBvcnRlZCIgVFggbGV2ZWwgdGhh
dCB5b3UgYXJlIHRyYW5zbWl0dGluZyBhdC4NCj4+IFdoaWNoIG1lYW5zIHlvdSdyZSBzdXBwb3Nl
ZCB0byBrbm93IChvciBndWVzcz8pIHdoYXQgZGJtIGxldmVsIHlvdSBhcmUgYWN0dWFsbHkgdHJh
bnNtaXR0aW5nIGF0IGFuZCBzZXQgaXQgaGVyZSB0byBkaXNwbGF5IHRvIHRoZSB3b3JsZCB3aGF0
IHlvdXIgdHJhbnNtaXR0ZXIgbGV2ZWwgaXMgc2V0IHRvIHNvIHRoZXkgY2FuIHJhbmdlIChndWVz
cyBvciBlc3RpbWF0ZSBkaXN0YW5jZSBmcm9tIFRYKS4NCj4+IFRoaXMgdmFsdWUgZG9lcyBub3Qg
aW5mbHVlbmNlIG9yIHJlZmxlY3QgYWN0dWFsIHRyYW5zbWl0IHBvd2VyLg0KPj4NCj4+IFBsZWFz
ZSBoZWxwISENCj4+DQo+PiBDb3VsZCB1c2UgYW55IHBvaW50ZXJzLg0KPj4NCj4+IEknbSBhIGhh
cmR3YXJlIGd1eSBhcyB3ZWxsIHNvIG5vdCB2ZXJ5IGV4cGVyaWVuY2VkIGluIHNvZnR3YXJlL3By
b2dyYW1taW5nIGJ1dCBJJ20gd2lsbGluZyB0byB0cnkgYW55dGhpbmcgdG8gZ2V0IGNvbnRyb2wg
b2YgdGhpcy4NCj4+DQo+PiBCZWVuIGF0IHRoaXMgZm9yIG92ZXIgYSB3ZWVrIGFuZCBoYXZlIHNv
bWUgd29ya2luZyBiZWFjb25zIGJ1dCBubyBjb250cm9sIG9mIHRyYW5zbWl0IHBvd2VyIGxldmVs
Lg0KPj4NCj4+IEFtIHVzaW5nIFRyZW5kbmV0IFVTQiBkb25nbGVzIHdoaWNoIGFwcGVhciB0byB1
c2UgYSBDYW1icmlkZ2UgQ2hpcC4gIEJ1dCBJJ20gbm90IGV4YWN0bHkgc3VyZSB3aGljaCBjaGlw
Lg0KPj4NCj4+DQo+PiA6fiMgbHN1c2INCj4+IEJ1cyAwMDEgRGV2aWNlIDAwNzogSUQgMGExMjow
MDAxIENhbWJyaWRnZSBTaWxpY29uIFJhZGlvLCBMdGQgDQo+PiBCbHVldG9vdGggRG9uZ2xlIChI
Q0kgbW9kZSkNCj4+DQo+Pg0KPj4gcm9vdEByYXNwYmVycnlwaTp+IyBoY2ljb25maWcgaGNpMA0K
Pj4gaGNpMDogICBUeXBlOiBCUi9FRFIgIEJ1czogVVNCDQo+PiAgICAgICAgIEJEIEFkZHJlc3M6
IDAwOjE1OjgzOkVBOjBBOkI5ICBBQ0wgTVRVOiAzMTA6MTAgIFNDTyBNVFU6IDY0OjgNCj4+ICAg
ICAgICAgVVAgUlVOTklORw0KPj4gICAgICAgICBSWCBieXRlczo3ODAgYWNsOjAgc2NvOjAgZXZl
bnRzOjUwIGVycm9yczowDQo+PiAgICAgICAgIFRYIGJ5dGVzOjExMTAgYWNsOjAgc2NvOjAgY29t
bWFuZHM6NTAgZXJyb3JzOjANCj4+DQo+Pg0KPj4NCj4+DQo+Pg0KPj4NCj4+DQo+Pg0KPj4NCj4+
DQo+Pg0KPj4NCj4+DQo+Pg0KPj4gLS0NCj4+IFRvIHVuc3Vic2NyaWJlIGZyb20gdGhpcyBsaXN0
OiBzZW5kIHRoZSBsaW5lICJ1bnN1YnNjcmliZSANCj4+IGxpbnV4LWJsdWV0b290aCIgaW4gdGhl
IGJvZHkgb2YgYSBtZXNzYWdlIHRvIA0KPj4gbWFqb3Jkb21vQHZnZXIua2VybmVsLm9yZyBNb3Jl
IG1ham9yZG9tbyBpbmZvIGF0ICANCj4+IGh0dHA6Ly92Z2VyLmtlcm5lbC5vcmcvbWFqb3Jkb21v
LWluZm8uaHRtbA0KPiAtLQ0KPiBUbyB1bnN1YnNjcmliZSBmcm9tIHRoaXMgbGlzdDogc2VuZCB0
aGUgbGluZSAidW5zdWJzY3JpYmUgDQo+IGxpbnV4LWJsdWV0b290aCIgaW4gdGhlIGJvZHkgb2Yg
YSBtZXNzYWdlIHRvIG1ham9yZG9tb0B2Z2VyLmtlcm5lbC5vcmcgDQo+IE1vcmUgbWFqb3Jkb21v
IGluZm8gYXQgIGh0dHA6Ly92Z2VyLmtlcm5lbC5vcmcvbWFqb3Jkb21vLWluZm8uaHRtbA0KDQoN
Cg0KLS0NCi0tLS0gSGlldSBMZSAtLS0NCg==
Hi,
On Wed, Oct 12, 2016, Hieu Le wrote:
> In my opinion, the only way I can find to increase the tx_power is to
> recompile the linux kernel. There may be a better way
>
> It seems that bluetooth stack within kernel separated into two classes:
> 1. Inquiry Tx_power.
> 2. Advertise Tx_power.
>
> And the default value is 0.
>
> You can take a look at:
> *hci_alloc_dev(void) function within net/bluetooth/hci_core.c file
> hdev->inq_tx_power = HCI_TX_POWER_INVALID;
> hdev->adv_tx_power = HCI_TX_POWER_INVALID;
The adv_tx_power is not used for changing the controller advertising TX
power. It's only used for reading the current controller setting and
storing it in this variable. The reason for all this is that currently
(as of Bluetooth 4.2) there is no standard HCI command for changing the
advertising TX power.
Johan
Hi,
In my opinion, the only way I can find to increase the tx_power is to
recompile the linux kernel. There may be a better way
It seems that bluetooth stack within kernel separated into two classes:
1. Inquiry Tx_power.
2. Advertise Tx_power.
And the default value is 0.
You can take a look at:
*hci_alloc_dev(void) function within net/bluetooth/hci_core.c file
hdev->inq_tx_power = HCI_TX_POWER_INVALID;
hdev->adv_tx_power = HCI_TX_POWER_INVALID;
Hope it will be helpful to you.
Regards,
Hieu.
On Wed, Oct 12, 2016 at 12:52 AM, Steve Gladden
<[email protected]> wrote:
> Thanks!!
> Yes it's nice to hear from somebody.
>
> I've been scouring the web so far to no avail on what I think should be a simple and accessible setting.
> It's obvious from the specs that most chips have a programmable (settable) transmitter power.
> And with beacons it is very important and expected that one should be able to adjust the transmitter level.
> All of the serial boards do it with simple AT commands.
>
> I just don't get why there's no documentation on how to do it with a USB device!!
>
> They sell class 1 bluetooth usb dongles for applications that require more range (100m) is quoted on most class 1 products.
>
> I'd expect there should be a straight forward easy to set power in LE mode to get more range or save power and limit range when wanted.
>
> But I'm really not finding this information out there!
>
> I don;t understand what I am doing wrong or why this is so difficult to find. :)
>
>
>
>
>
>
>
> On 11 October 2016 at 17:50, Steve Gladden <[email protected]> wrote:
>> Is this this list just some kind of automated patch announcement log and not an actual mailing list where you can ask anything about bluetooth.
>> This is all I have seen here for the past few days?
>> Where can I ask an actual question about bluetooth?
>
> There are some real humans here too! :-)
>
> If you look back on the archive of this list you will see a mixture of
> questions and patch requests.
> marc.info/?l=linux-bluetooth
>
> I've kept quiet as I'm not sure I can answer questions. To offer some
> shared experience, I can say that I've been experimenting with
> (Eddystone) beacons on Linux single board computers accessing BlueZ
> through the DBus API using Python. I also have not found a way to
> change the power level of advertisements either. For what I'm doing,
> just making sure the TX power in the Eddystone advert matches what the
> dongle is actually broadcasting has been good enough.
>
> Sorry I couldn't be of more help.
>
> Regards,
> Barry
>
>>
>>
>>
>>
>> Steve Gladden
>>
>> Michigan Broadband Systems
>> Connecting Your Business!
>>
>>
>>
>> +1 734.527.7150 Direct
>> +1 248.327.4389 Fax
>> [email protected]
>> http://www.michiganbroadband.com
>>
>> ________________________________________
>> From: Steve Gladden
>> Sent: Sunday, October 09, 2016 12:11 PM
>> To: [email protected]
>> Subject: How can you set Transmit power level in Bluetooth LE mode for an LE beacon?
>>
>> Hi,
>> My name is Steve and I am located in Ann Arbor Michigan USA.
>>
>> I am new bluetooth LE and lately am obsessed with Bluetooth LE beacons and trying them out.
>>
>> I have read article after article and page after page about how people have setup up beacons with USB BT 4.0 interfaces
>> as well as serial bluetooth boards.
>>
>> I am currently experimenting with a beacon running on a Raspberry Pi-B and using an external USB Bluetooth 4.0 class 1 dongle.
>>
>> My frustration is that I have not been able to find any useful information in how to change the Transmitter power level when in
>> LE mode.
>>
>> The dongle appears to be working at default level below zero dbm.
>>
>> The whole point of building your own beacon this way is to be able to customize it and setting the power level is an important key item
>> that should be easily accessible yet I find that NOBODY ever even mentions it let alone do they explain or provide a way to set the power.
>>
>>
>> Every text that I have found that details beacon setups from command line never bother to mention setting beacon TX power.
>>
>> All the pages I have found seem to copy each other and repeat the same information over & over
>> But never get around to even mentioning or discussing setting the power output level of the blutooth dongle.
>>
>> sudo hcitool -i hci0 cmd 0x08 0x0008 1E 02 01 1A 1A FF 4C 00 02 15 [ 92 77 83 0A B2 EB 49 0F A1 DD 7F E3 8C 49 2E DE ] [ 00 00 ] [ 00 00 ] C5 00
>>
>> The byte just left of the last one is the "reported" TX level that you are transmitting at.
>> Which means you're supposed to know (or guess?) what dbm level you are actually transmitting at and set it here to display to the world what your transmitter level is set to so they can range (guess or estimate distance from TX).
>> This value does not influence or reflect actual transmit power.
>>
>> Please help!!
>>
>> Could use any pointers.
>>
>> I'm a hardware guy as well so not very experienced in software/programming but I'm willing to try anything to get control of this.
>>
>> Been at this for over a week and have some working beacons but no control of transmit power level.
>>
>> Am using Trendnet USB dongles which appear to use a Cambridge Chip. But I'm not exactly sure which chip.
>>
>>
>> :~# lsusb
>> Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
>>
>>
>> root@raspberrypi:~# hciconfig hci0
>> hci0: Type: BR/EDR Bus: USB
>> BD Address: 00:15:83:EA:0A:B9 ACL MTU: 310:10 SCO MTU: 64:8
>> UP RUNNING
>> RX bytes:780 acl:0 sco:0 events:50 errors:0
>> TX bytes:1110 acl:0 sco:0 commands:50 errors:0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
---- Hieu Le ---
Thanks!!
Yes it's nice to hear from somebody.
I've been scouring the web so far to no avail on what I think should be a simple and accessible setting.
It's obvious from the specs that most chips have a programmable (settable) transmitter power.
And with beacons it is very important and expected that one should be able to adjust the transmitter level.
All of the serial boards do it with simple AT commands.
I just don't get why there's no documentation on how to do it with a USB device!!
They sell class 1 bluetooth usb dongles for applications that require more range (100m) is quoted on most class 1 products.
I'd expect there should be a straight forward easy to set power in LE mode to get more range or save power and limit range when wanted.
But I'm really not finding this information out there!
I don;t understand what I am doing wrong or why this is so difficult to find. :)
On 11 October 2016 at 17:50, Steve Gladden <[email protected]> wrote:
> Is this this list just some kind of automated patch announcement log and not an actual mailing list where you can ask anything about bluetooth.
> This is all I have seen here for the past few days?
> Where can I ask an actual question about bluetooth?
There are some real humans here too! :-)
If you look back on the archive of this list you will see a mixture of
questions and patch requests.
marc.info/?l=linux-bluetooth
I've kept quiet as I'm not sure I can answer questions. To offer some
shared experience, I can say that I've been experimenting with
(Eddystone) beacons on Linux single board computers accessing BlueZ
through the DBus API using Python. I also have not found a way to
change the power level of advertisements either. For what I'm doing,
just making sure the TX power in the Eddystone advert matches what the
dongle is actually broadcasting has been good enough.
Sorry I couldn't be of more help.
Regards,
Barry
>
>
>
>
> Steve Gladden
>
> Michigan Broadband Systems
> Connecting Your Business!
>
>
>
> +1 734.527.7150 Direct
> +1 248.327.4389 Fax
> [email protected]
> http://www.michiganbroadband.com
>
> ________________________________________
> From: Steve Gladden
> Sent: Sunday, October 09, 2016 12:11 PM
> To: [email protected]
> Subject: How can you set Transmit power level in Bluetooth LE mode for an LE beacon?
>
> Hi,
> My name is Steve and I am located in Ann Arbor Michigan USA.
>
> I am new bluetooth LE and lately am obsessed with Bluetooth LE beacons and trying them out.
>
> I have read article after article and page after page about how people have setup up beacons with USB BT 4.0 interfaces
> as well as serial bluetooth boards.
>
> I am currently experimenting with a beacon running on a Raspberry Pi-B and using an external USB Bluetooth 4.0 class 1 dongle.
>
> My frustration is that I have not been able to find any useful information in how to change the Transmitter power level when in
> LE mode.
>
> The dongle appears to be working at default level below zero dbm.
>
> The whole point of building your own beacon this way is to be able to customize it and setting the power level is an important key item
> that should be easily accessible yet I find that NOBODY ever even mentions it let alone do they explain or provide a way to set the power.
>
>
> Every text that I have found that details beacon setups from command line never bother to mention setting beacon TX power.
>
> All the pages I have found seem to copy each other and repeat the same information over & over
> But never get around to even mentioning or discussing setting the power output level of the blutooth dongle.
>
> sudo hcitool -i hci0 cmd 0x08 0x0008 1E 02 01 1A 1A FF 4C 00 02 15 [ 92 77 83 0A B2 EB 49 0F A1 DD 7F E3 8C 49 2E DE ] [ 00 00 ] [ 00 00 ] C5 00
>
> The byte just left of the last one is the "reported" TX level that you are transmitting at.
> Which means you're supposed to know (or guess?) what dbm level you are actually transmitting at and set it here to display to the world what your transmitter level is set to so they can range (guess or estimate distance from TX).
> This value does not influence or reflect actual transmit power.
>
> Please help!!
>
> Could use any pointers.
>
> I'm a hardware guy as well so not very experienced in software/programming but I'm willing to try anything to get control of this.
>
> Been at this for over a week and have some working beacons but no control of transmit power level.
>
> Am using Trendnet USB dongles which appear to use a Cambridge Chip. But I'm not exactly sure which chip.
>
>
> :~# lsusb
> Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
>
>
> root@raspberrypi:~# hciconfig hci0
> hci0: Type: BR/EDR Bus: USB
> BD Address: 00:15:83:EA:0A:B9 ACL MTU: 310:10 SCO MTU: 64:8
> UP RUNNING
> RX bytes:780 acl:0 sco:0 events:50 errors:0
> TX bytes:1110 acl:0 sco:0 commands:50 errors:0
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Steve,
On 11 October 2016 at 17:50, Steve Gladden <[email protected]> wrote:
> Is this this list just some kind of automated patch announcement log and not an actual mailing list where you can ask anything about bluetooth.
> This is all I have seen here for the past few days?
> Where can I ask an actual question about bluetooth?
There are some real humans here too! :-)
If you look back on the archive of this list you will see a mixture of
questions and patch requests.
marc.info/?l=linux-bluetooth
I've kept quiet as I'm not sure I can answer questions. To offer some
shared experience, I can say that I've been experimenting with
(Eddystone) beacons on Linux single board computers accessing BlueZ
through the DBus API using Python. I also have not found a way to
change the power level of advertisements either. For what I'm doing,
just making sure the TX power in the Eddystone advert matches what the
dongle is actually broadcasting has been good enough.
Sorry I couldn't be of more help.
Regards,
Barry
>
>
>
>
> Steve Gladden
>
> Michigan Broadband Systems
> Connecting Your Business!
>
>
>
> +1 734.527.7150 Direct
> +1 248.327.4389 Fax
> [email protected]
> http://www.michiganbroadband.com
>
> ________________________________________
> From: Steve Gladden
> Sent: Sunday, October 09, 2016 12:11 PM
> To: [email protected]
> Subject: How can you set Transmit power level in Bluetooth LE mode for an LE beacon?
>
> Hi,
> My name is Steve and I am located in Ann Arbor Michigan USA.
>
> I am new bluetooth LE and lately am obsessed with Bluetooth LE beacons and trying them out.
>
> I have read article after article and page after page about how people have setup up beacons with USB BT 4.0 interfaces
> as well as serial bluetooth boards.
>
> I am currently experimenting with a beacon running on a Raspberry Pi-B and using an external USB Bluetooth 4.0 class 1 dongle.
>
> My frustration is that I have not been able to find any useful information in how to change the Transmitter power level when in
> LE mode.
>
> The dongle appears to be working at default level below zero dbm.
>
> The whole point of building your own beacon this way is to be able to customize it and setting the power level is an important key item
> that should be easily accessible yet I find that NOBODY ever even mentions it let alone do they explain or provide a way to set the power.
>
>
> Every text that I have found that details beacon setups from command line never bother to mention setting beacon TX power.
>
> All the pages I have found seem to copy each other and repeat the same information over & over
> But never get around to even mentioning or discussing setting the power output level of the blutooth dongle.
>
> sudo hcitool -i hci0 cmd 0x08 0x0008 1E 02 01 1A 1A FF 4C 00 02 15 [ 92 77 83 0A B2 EB 49 0F A1 DD 7F E3 8C 49 2E DE ] [ 00 00 ] [ 00 00 ] C5 00
>
> The byte just left of the last one is the "reported" TX level that you are transmitting at.
> Which means you're supposed to know (or guess?) what dbm level you are actually transmitting at and set it here to display to the world what your transmitter level is set to so they can range (guess or estimate distance from TX).
> This value does not influence or reflect actual transmit power.
>
> Please help!!
>
> Could use any pointers.
>
> I'm a hardware guy as well so not very experienced in software/programming but I'm willing to try anything to get control of this.
>
> Been at this for over a week and have some working beacons but no control of transmit power level.
>
> Am using Trendnet USB dongles which appear to use a Cambridge Chip. But I'm not exactly sure which chip.
>
>
> :~# lsusb
> Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
>
>
> root@raspberrypi:~# hciconfig hci0
> hci0: Type: BR/EDR Bus: USB
> BD Address: 00:15:83:EA:0A:B9 ACL MTU: 310:10 SCO MTU: 64:8
> UP RUNNING
> RX bytes:780 acl:0 sco:0 events:50 errors:0
> TX bytes:1110 acl:0 sco:0 commands:50 errors:0
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Is this this list just some kind of automated patch announcement log and not an actual mailing list where you can ask anything about bluetooth.
This is all I have seen here for the past few days?
Where can I ask an actual question about bluetooth?
Steve Gladden
Michigan Broadband Systems
Connecting Your Business!
+1 734.527.7150 Direct
+1 248.327.4389 Fax
[email protected]
http://www.michiganbroadband.com
________________________________________
From: Steve Gladden
Sent: Sunday, October 09, 2016 12:11 PM
To: [email protected]
Subject: How can you set Transmit power level in Bluetooth LE mode for an LE beacon?
Hi,
My name is Steve and I am located in Ann Arbor Michigan USA.
I am new bluetooth LE and lately am obsessed with Bluetooth LE beacons and trying them out.
I have read article after article and page after page about how people have setup up beacons with USB BT 4.0 interfaces
as well as serial bluetooth boards.
I am currently experimenting with a beacon running on a Raspberry Pi-B and using an external USB Bluetooth 4.0 class 1 dongle.
My frustration is that I have not been able to find any useful information in how to change the Transmitter power level when in
LE mode.
The dongle appears to be working at default level below zero dbm.
The whole point of building your own beacon this way is to be able to customize it and setting the power level is an important key item
that should be easily accessible yet I find that NOBODY ever even mentions it let alone do they explain or provide a way to set the power.
Every text that I have found that details beacon setups from command line never bother to mention setting beacon TX power.
All the pages I have found seem to copy each other and repeat the same information over & over
But never get around to even mentioning or discussing setting the power output level of the blutooth dongle.
sudo hcitool -i hci0 cmd 0x08 0x0008 1E 02 01 1A 1A FF 4C 00 02 15 [ 92 77 83 0A B2 EB 49 0F A1 DD 7F E3 8C 49 2E DE ] [ 00 00 ] [ 00 00 ] C5 00
The byte just left of the last one is the "reported" TX level that you are transmitting at.
Which means you're supposed to know (or guess?) what dbm level you are actually transmitting at and set it here to display to the world what your transmitter level is set to so they can range (guess or estimate distance from TX).
This value does not influence or reflect actual transmit power.
Please help!!
Could use any pointers.
I'm a hardware guy as well so not very experienced in software/programming but I'm willing to try anything to get control of this.
Been at this for over a week and have some working beacons but no control of transmit power level.
Am using Trendnet USB dongles which appear to use a Cambridge Chip. But I'm not exactly sure which chip.
:~# lsusb
Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
root@raspberrypi:~# hciconfig hci0
hci0: Type: BR/EDR Bus: USB
BD Address: 00:15:83:EA:0A:B9 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:780 acl:0 sco:0 events:50 errors:0
TX bytes:1110 acl:0 sco:0 commands:50 errors:0