connection interval error

[DanisXZ]

Hi,

nrf SDK 17.1.0

Why am I restricted to keep the connection interval as mentioned in the examples ?

For example, in the template example, it is restricting the user to keep the interval between 0.1 and 0.2. But the BLE spec allows between 7.5 ms and 4000 ms. The above code is generating an error code of 0x07 for function "sd_ble_gap_ppcp_set".

1. Why am I not free to choose my own conenction interval ? 
2. How can I configure the connection in "Just works" ? I don't want central/peripheral to initiate any SMP protocol ? I made sec_param_bond to zero in the ble_app_template example as shown below. Is this enough ?

I don't need any security and want any SMP related packet to be sent during the connection.

 

[Joakim Jakobsen]

Thanks. 

I was concerned that you might violate the below:

* @note  If both conn_sup_timeout and max_conn_interval are specified, then the following constraint applies:
 *        conn_sup_timeout * 4 > (1 + slave_latency) * max_conn_interval
 *        that corresponds to the following Bluetooth Spec requirement:
 *        The Supervision_Timeout in milliseconds shall be larger than
 *        (1 + Conn_Latency) * Conn_Interval_Max * 2, where Conn_Interval_Max is given in milliseconds.

But it seems that the values are within the allowed values.

Let me do some further research on the issue and get back to you.

The values you listed below (2500/3000/4000) causes the sd_ble_gap_ppcp_set() function to return with the invalid param error?

Br,
Joakim

[DanisXZ]

Joakim Jakobsen said:

Let me do some further research on the issue and get back to you.

Okay

[Joakim Jakobsen]

Sorry about the delay.

I can't see any issues when testing this myself. 

DanisXZ said:

Custom board based on nRF52810. 

I haven't tested with the nRF52810. Do you have a Nordic DK available to test on?

Br,
Joakim

[DanisXZ]

Hi Joakim,

Joakim Jakobsen said:

Do you have a Nordic DK available to test on?

I tested with nRF52 DK and I face the same issue.

SW package: 

nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_hrs\pca10040\s132\ses

I changed the code like given below it fails as explained before:

I found that the issue is not happening if MAX_CONN_INTERVAL is less than 2000. But sd_ble_gap_ppcp_set() fails if MAX_CONN_INTERVAL  >= 2000

[treTreTo-IoT]

Had the same problem. Needed to increase CONN_SUP_TIMEOUT. Seems like  CONN_SUP_TIMEOUT > 2*MAX_CONN_INTERVAL