how to reduce BLE reconnection time after disconnect from the application(its taking 16 seconds to reconnect after disconnect)

RE: how to reduce BLE reconnection time after disconnect from the application(its taking 16 seconds to reconnect after disconnect)

Kenneth — Wed, 30 Oct 2024 12:14:52 GMT

Sorry, I was mixing things here, I don't expect using 7.5ms in this case will help. My suggestion would be to reduce the CONN_SUP_TIMEOUT. Still it doesn't really explain 12seconds in any way, is this testing using an nRF52833 DK? Do you see the same if you use a BLE example from the nRF5 SDK without changes for comparison?

Kenenth

RE: how to reduce BLE reconnection time after disconnect from the application(its taking 16 seconds to reconnect after disconnect)

babu_80 — Wed, 30 Oct 2024 05:37:05 GMT

Even after changing to 7.5 ms, it takes 12 seconds and above to reconnect after being disconnected from the device.
What are the other parameters I need to check?

RE: how to reduce BLE reconnection time after disconnect from the application(its taking 16 seconds to reconnect after disconnect)

Kenneth — Tue, 29 Oct 2024 12:44:46 GMT

You need to decrease MIN_CONN_INTERVAL to 7.5 instead of 15ms.

Kenneth

RE: how to reduce BLE reconnection time after disconnect from the application(its taking 16 seconds to reconnect after disconnect)

babu_80 — Tue, 29 Oct 2024 09:30:58 GMT

Hello Kenneth,

Here is the configured parameter values

#define APP_ADV_INTERVAL 300
#define APP_ADV_DURATION BLE_GAP_ADV_TIMEOUT_GENERAL_UNLIMITED
#define MIN_CONN_INTERVAL MSEC_TO_UNITS(15, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(40, UNIT_1_25_MS)
#define SLAVE_LATENCY 0
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(4000, UNIT_10_MS)
#define FIRST_CONN_PARAMS_UPDATE_DELAY 5000
#define NEXT_CONN_PARAMS_UPDATE_DELAY 30000

is that Supervision timeout i need to decrease?

RE: how to reduce BLE reconnection time after disconnect from the application(its taking 16 seconds to reconnect after disconnect)

Kenneth — Mon, 28 Oct 2024 13:40:25 GMT

Hello,

Normally when you are in a connection you have a connection parameter called supervisor timeout. This parameter control how long the link should be assumed valid, before considered lost. I assume in this case that maybe this parameter is set very high, and thereby the central or peripheral will not advertise or connect before it's timed out.

If that is not the problem, then I suggest to look at the advertisement interval, maybe it's set very long.

Kenneth