RE: nRF52 beacone TXPOWER

YaroslavRakhnenko — Fri, 01 Apr 2022 13:37:06 GMT

Thanks for the answer! I found an error. I called sd_ble_gap_tx_power_set() with the wrong parameters in the wrong place (facepalm)

maybe it will be useful for someone, in the ble_app_beacone example (from SDK) you need to write it here:

RE: nRF52 beacone TXPOWER

Einar Thorsrud — Fri, 01 Apr 2022 12:18:14 GMT

Hi,

[quote user=""]

I tried to do it in several ways:

sd_ble_gap_tx_power_set() or NRF_RADIO->TXPOWER

but in this case, the beacon does not work at all.

[/quote]

Did you try to debug in this case? Did you get any errors? In any case, the correct way to adjust the Tx power for Bluetooth advertising is to use sd_ble_gap_tx_power_set() with the role (first parameter) set to BLE_GAP_TX_POWER_ROLE_ADV. The second parameter should be the advertising handle which you got from the call to sd_ble_gap_adv_set_configure(). Therefore, I suggest you simply call sd_ble_gap_tx_power_set() immediately after the call to sd_ble_gap_adv_set_configure().

(Note that if you use the advertising module this is not called directly, but by ble_advertising_init(), so you should get it from there. Also, in that case you can find the advertising handle from the ble_advertising_t struct after the call to ble_advertising_init().)

[quote user=""]Then I found a comment that says that the APP_MEASURED_RSSI parameter is responsible for the TX power[/quote]

That is not correct. This is just a information about the typical RSSI measured at a fixed distance from the beacon to make it a bit simpler to estimate distance based on RSSI.