How to dynamically change the connection interval

[Kc Owen]

Why do I use this function bt_conn_le_param_update( ), only after the power on the first time to work, then do not work

[Einar Thorsrud]

Hi,

There should not be any limitations on how often you can call bt_conn_le_param_update(), and updating the connection parameters several times during a connection is common. In what way does it not work?

[Kc Owen]

Is there no requirement for the interval between the first call to bt_conn_le_param_update() and the second call？

[Einar Thorsrud]

CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS is enabled by default, so unless you have disabled it it it used (you should see it in the generated .config). That is not a problem though, but as you cannot have parallell procedures, this is just an example that you need to handle that it could happen (check the return value and handle it appropriately).

[Kc Owen]

Both calls checked the return value, no error was returned, but only the second call can normally print the connection parameter change information, the first call does not seem to have been executed, but I am sure it has been executed, probably was rejected by the central, so I want to know whether the interval between the two calls is required

[Kc Owen]

My conf file does not use CONFIG_BT_LL_SOFTDEVICE=y because my program is modified based on routines from the nRF connect SDK

[Kc Owen]

What I find interesting is that if I connect my phone to the peripheral immediately after the broadcast, the two calls work, but if I connect after a while, the first call doesn't work

[Einar Thorsrud]

Hi,

You need to check the generated .config file in your build folder to see what you actually use, as there his a hiarachy of configs, and they also have default values. If you are building for a nRF devices, you will have CONFIG_BT_LL_SOFTDEVICE=y by default unless you explicitly picked the Zephyr LL instead.