Setting slave connection interval (same as GAP PPCP?)

[sam]

Hi,

I'm wondering if the slave connection interval range is the same as the GAP peripheral preferred connection parameters i.e. does it make sense to do the following (GAP connection parameters have been set before):

ble_gap_conn_params_t    gapConnParams;
sd_ble_gap_ppcp_get(&gapConnParams);

p_advertising->slave_conn_int.min_conn_interval = gapConnParams.min_conn_interval;
p_advertising->slave_conn_int.max_conn_interval = gapConnParams.max_conn_interval;

Thanks

[Sigurd]

Hi,

The sd_ble_gap_ppcp_get(...) is used to get the peripheral Preferred Connection Parameters.

When you set it like this:

gap_conn_params.min_conn_interval = MIN_CONN_INTERVAL;
gap_conn_params.max_conn_interval = MAX_CONN_INTERVAL;
gap_conn_params.slave_latency     = SLAVE_LATENCY;
gap_conn_params.conn_sup_timeout  = CONN_SUP_TIMEOUT;

err_code = sd_ble_gap_ppcp_set(&gap_conn_params);
APP_ERROR_CHECK(err_code);

You can later use the function sd_ble_gap_ppcp_get(...) to get the parameters(gap_conn_params) that the softdevice is currently set to use.

[Sigurd]

You don’t need to add the connection interval to the advertising packet. When the central device connects to the peripheral, the devices will negotiate the connection interval to use. This is handled for you in the Connection Parameters module (ble_conn_params.c) and initialized in conn_params_init(), the SoftDevice takes care of the rest.