[nRF Connect SDK](Urgent) How to fix Tx power?

RE: [nRF Connect SDK](Urgent) How to fix Tx power?

Einar Thorsrud — Mon, 24 Oct 2022 07:26:54 GMT

Hi,

Ah, I did not notice that you posted this. Note that with this you are using the Zephyr LL instead of the SoftDevice Controller. That is OK and up to you, but I would normally recomend using the SoftDevice controller. This is also the controller we qualify (see Bluetooth QDIDs).

RE: [nRF Connect SDK](Urgent) How to fix Tx power?

Einar Thorsrud — Mon, 24 Oct 2022 07:22:01 GMT

[quote user="Tim Hwang"]1. CONFIG_XXX for Tx
Do you have any idea?[/quote]

You can change the default Tx power using CONFIG_BT_CTLR_TX_PWR_*, for instance CONFIG_BT_CTLR_TX_PWR_PLUS_4 to set +4 dBm. Note that this does not work with early versions of the SoftDevice controller, though.

[quote user="Tim Hwang"]2.. Handle[/quote]

This code looks a bit odd, and while I did not fully understand the failure you described it is clear an error occurred). You should essentially do as you can see in the implementation of set_tx_power() in zephyr/samples/bluetooth/hci_pwr_ctrl/src/main.c. Note also that this is called with a parameter that distinguishes between roles).

RE: [nRF Connect SDK](Urgent) How to fix Tx power?

Tim Hwang — Mon, 24 Oct 2022 07:10:23 GMT

Now I could fix my issue adding two configs, and clean build.
I could set Tx as 4.

#Tx
CONFIG_BT_CTLR_ADVANCED_FEATURES=y
CONFIG_BT_CTLR_CONN_RSSI=y
CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y

CONFIG_BT_LL_SOFTDEVICE=n
CONFIG_BT_LL_SW_SPLIT=y

RE: [nRF Connect SDK](Urgent) How to fix Tx power?

Tim Hwang — Mon, 24 Oct 2022 02:02:10 GMT

Thanks for updating.

1. CONFIG_XXX for Tx
Do you have any idea?

2.. Handle
if(0==bt_hci_get_conn_handle(m_conn, &default_conn_handle))
{
set_tx_power(BT_HCI_VS_LL_HANDLE_TYPE_CONN, default_conn_handle, 4);
}
handle is correct.

log
00> update_txupdate_tx
00> set_tx_power (4)
00> Actual Tx Power: 4

RE: [nRF Connect SDK](Urgent) How to fix Tx power?

Einar Thorsrud — Fri, 21 Oct 2022 12:03:28 GMT

Hi,

I am not sure I understand correctly, but is the problem that you are only able to set the Tx power for the first connection, but not subsequent ones? If so, my first thought is that you are using an invalid connection handle (for instance that you do not update it for subsequent connections). Could that be the case? If not, can you elaborate, explain what you have found by debugging (any error codes returned from bt_hci_cmd_send_sync() for instance?).

RE: [nRF Connect SDK](Urgent) How to fix Tx power?

Tim Hwang — Fri, 21 Oct 2022 09:49:50 GMT

In my additional test, sample including pairing made this issue.
peripheral_uart sample(\nrf\samples\bluetooth\peripheral_uart) works well.