Short Connection Default Interval not being set

[Sebastian Luntraru]

Hi everyone,

I’m working with Zephyr 3.2.3 in a Windows environment and trying to run the shorter connection intervals sample:
https://github.com/nrfconnect/sdk-nrf/tree/v3.2.3/samples/bluetooth/shorter_conn_intervals

What I’m trying to achieve:

I would like to use the default connection parameters defined in the sample without explicitly requesting a connection parameter update.

In particular, I’m referring to the default configuration in:
https://github.com/nrfconnect/sdk-nrf/blob/v3.2.3/samples/bluetooth/shorter_conn_intervals/src/main.c#L432

I tried to remove the connection parameter update logic from:
github.com/.../main.c

Expected behavior:

• The connection should use the default parameters (including the minimum interval).

Actual behavior:

• Even when relying on default settings, the connection does not use the expected interval unless I explicitly trigger a connection parameter update.

Question:
Is this expected behavior?
Is there a way to enforce the default minimum connection interval without calling a connection parameter update?

Thanks in advance!

[longo92]

Hi Edvin,

i am also interested in the matter (in use case enlighten by Sebastian):

- if do not call bt_conn_le_conn_rate_set_defaults() but only bt_conn_le_conn_rate_request(), what happens?

- In wich cases the central uses the parameters set in bt_conn_le_conn_rate_set_defaults()?

Thanks,

Alessandro

[Edvin]

You can do that. But it will still enter the connection using a legal connection interval, backwards compatible to BLE, of minimum 7.5ms.