Setting the tx power to 8db is leading to configuration messages timing out

RE: Setting the tx power to 8db is leading to configuration messages timing out

Edvin — Fri, 31 Mar 2023 13:07:09 GMT

Hello,

I will refer to Hieu's answer again. It suggests how to work around it in your current version, by looking at how it is done in the HCI power control sample.

Please note that we will be very short staffed next week due to public holidays in Norway. I will be back in the office on April 11th. Sorry for the inconvenience.

Best regards,

Edvin

RE: Setting the tx power to 8db is leading to configuration messages timing out

Susheel — Tue, 28 Mar 2023 18:47:41 GMT

Hello Edvin, thank you for the reply.

I have tried migrating my sdk to 2.1.1 and there seem to be too many changes in between. I am gonna have to spend some time adapting my code to the new sdk. As my software is almost frozen for prototyping, is there any way to stick with 1.9.1 and still use the nordic software to get 8db power and reliable communications?

-Susheel

RE: Setting the tx power to 8db is leading to configuration messages timing out

Edvin — Thu, 23 Mar 2023 14:07:58 GMT

What NCS version are you using?

Please see my colleague, Hieu's, answer in this post.

BR,

Edvin

RE: Setting the tx power to 8db is leading to configuration messages timing out

Susheel — Wed, 22 Mar 2023 14:53:27 GMT

Hello Edvin, thank you for your suggestion. I have tried it out and it works(timining wise). However, I when I measured the actual RSSI(dbm) of the messages transmitted on my nrf Connect app, there I saw a difference.

When I used nothing but the CONFIG_BT_CTLR_TX_PWR_PLUS_8=y configuration, the RSSI received was -22dbm whereas when I used the LL_SW_SPLIT=y, CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y and set the tx power manually on start using set_tx_power(), I see that the RSSI received increased to -10dbm. I made sure to keep the distance constant when testing.

Please advice.

RE: Setting the tx power to 8db is leading to configuration messages timing out

Edvin — Mon, 20 Mar 2023 09:14:23 GMT

Ok. Can you please have a look at the sample found in NCS\zephyr\samples\bluetooth\hci_pwr_ctrl. This is a sample that is set up to read the TX power upon connect, but you can use the same approach to write it. As you can see from that sample, it doesn't require the LL_SW_SPLIT.

Do you really need to set it dynamically during the runtime of the app? It would be easier to set it at compile time, because then you can only use a config (CONFIG_BT_CTLR_TX_PWR_PLUS_8=y)

The reason I want you to take out the LL_SW_SPLIT is that when you include this, you will use the Zephyr Bluetooth controller, and not the Nordic Bluetooth controller. You can do this if you like, but that is not our stack, and I do not think the bluetooth mesh libraries will work with the Zephyr Bluetooth controller.

BR,

Edvin

RE: Setting the tx power to 8db is leading to configuration messages timing out

Susheel — Fri, 17 Mar 2023 12:32:05 GMT

When I remove it, the set_tx_power() function returns a IO error and fails to set the tx power to 8db

RE: Setting the tx power to 8db is leading to configuration messages timing out

Edvin — Fri, 17 Mar 2023 12:29:51 GMT

did you try removing CONFIG_BT_LL_SW_SPLIT (or set it to =n ?)

RE: Setting the tx power to 8db is leading to configuration messages timing out

Susheel — Thu, 16 Mar 2023 15:31:04 GMT

CONFIG_BT_CTRL_ADVANCED_FEATURES takes the default value when i do not add CONFIG_BT_LL_SW_SPLIT=y. Also, when i dont add CONFIG_LL_SW_SPLIT, the set_tx_power() gives an IO error and doesn't actually change the gain to 8db.

Update: I tried only adding the CONFIG_BT_LL_SW_SPLIT=y. In this case, the configuration of the sensor client is alright but the configuration of the sensor server times out. In my code, I return from the configure_node() function in the provisioner even if a single configuration call fails with an error. Here, the function bt_mesh_cfg_mod_sub_add_vnd() fails repeatedly with a timeout(-116) only for the sensor server.

I have added a few vendor models to my sensor server/client but, I am wondering why the configuration was going through when using the normal tx power settings.

I have changed the configuration timeout on the provisioner to 10 times the default value and the message still times out. Please suggest.

RE: Setting the tx power to 8db is leading to configuration messages timing out

Edvin — Thu, 16 Mar 2023 14:24:47 GMT

Hello,

1: Try to remove the CONFIG_BT_LL_SW_SPLIT=y

2: Try to remove the CONFIG_BT_CTRL_ADVANCED_FEATURES=y

And any combination of these. Does that affect the behavior?

BR,
Edvin