Hi
How can I increase the connection interval of BLE radio from default value of 30mS-50mS to 600ms in NRF5340-SDK.
Hi
How can I increase the connection interval of BLE radio from default value of 30mS-50mS to 600ms in NRF5340-SDK.
Hello!
The connection interval can be adjusted using Zephyr's Bluetooth API:
https://docs.zephyrproject.org/latest/reference/bluetooth/connection_mgmt.html
To learn how to use this API I would recommend having a look at the BLE throughput sample:
Notice how a bt_le_conn_param struct is defined using the BT_LE_CONN_PARAM() macro, and how that is used in the bt_conn_le_param_update() function to adjust the parameters.
Best regards,
Einar
Hi
Thank you very much for your information. But I want to increase the Connection interval in peripheral_uart sample code.
Would you please to guide me to modify this program to work with a different Connection interval. I defined the
bt_le_conn_paramm struct at the top and call the bt_conn_le_param_update() function in the main part of program.
It didn't work.
Hi
From my understanding, the procedure for modifying the connection interval from a peripheral should be the same, but there might be a significant delay before the changes take effect.
Is the param update function returning an error code, or are you just observing that the behavior doesn't change?
I would recommend going through the BLE throughput sample more thoroughly, in case you've missed a step of the procedure.
-Einar
Hi
I tried compiling and building the so called program with nRF Connect SDK V1.6.1 and it worked perfectly.
But by compiling and building with nRF Connect SDK V1.8.0 which is a newer version it didn't work and
the chip is resetting repeatedly.
my nRF Connect for desktop version is 3.10.0
Hi
I tried compiling and building the so called program with nRF Connect SDK V1.6.1 and it worked perfectly.
But by compiling and building with nRF Connect SDK V1.8.0 which is a newer version it didn't work and
the chip is resetting repeatedly.
my nRF Connect for desktop version is 3.10.0
Hi
What program are you seeing this behavior with?
Is it the throughput sample itself or your own custom application?
-Einar