How to handle BLE_GAP_EVT_CONN_PARAM_UPDATE and BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST events ?

RE: How to handle BLE_GAP_EVT_CONN_PARAM_UPDATE and BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST events ?

Petter Myhre — Fri, 14 Aug 2015 22:12:32 GMT

The first.

RE: How to handle BLE_GAP_EVT_CONN_PARAM_UPDATE and BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST events ?

Siva Subrahmanyam — Fri, 14 Aug 2015 17:17:41 GMT

if central should update the connection parameters by peripheral requests. of the two below which connection parameters should be used?

sd_ble_gap_conn_param_update(p_gap_evt->conn_handle, &p_gap_evt->params.conn_param_update_request.conn_params);

sd_ble_gap_conn_param_update(p_gap_evt->conn_handle, &p_gap_evt->params.conn_param_update.conn_params);

RE: How to handle BLE_GAP_EVT_CONN_PARAM_UPDATE and BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST events ?

Petter Myhre — Fri, 14 Aug 2015 13:20:04 GMT

If the central should accept whatever connection parameters the peripheral requests you can use it.

RE: How to handle BLE_GAP_EVT_CONN_PARAM_UPDATE and BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST events ?

Siva Subrahmanyam — Fri, 14 Aug 2015 13:13:19 GMT

So on central we can ignore BLE_GAP_EVT_CONN_PARAM_UPDATE event.

on central for BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST can we use below update function with request parameters. sd_ble_gap_conn_param_update(p_gap_evt->conn_handle, &p_gap_evt->params.conn_param_update_request.conn_params);

RE: How to handle BLE_GAP_EVT_CONN_PARAM_UPDATE and BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST events ?

Petter Myhre — Fri, 14 Aug 2015 11:26:55 GMT

The peripheral can request an update of the connection parameters by calling sd_ble_gap_conn_param_update(). Then the central will receive the BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST event. The central can then

Accept the request and respond with sd_ble_gap_conn_param_update(connection parameters) to update the connection parameters
Reject the request and respond with sd_ble_gap_conn_param_update(NULL)
Ignore it.

Please see this MSC for more information.

The central can update the connection parameters by calling sd_ble_gap_conn_param_update(). Then the peripheral and the central will get the BLE_GAP_EVT_CONN_PARAM_UPDATE event. The peripheral can check the new connection parameters and if they are unacceptable it can do a disconnect or something else, or if they are acceptable, it can ignore it.

Please see this MSC for more information.