How to handle BLE_GAP_EVT_CONN_PARAM_UPDATE and BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST events ?

[Siva Subrahmanyam]

I am working on s120(central) and s130(central/peripheral). I am getting BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST event after updating conn_parameters w.r.t to peer using sd_ble_gap_conn_param_update i am getting BLE_GAP_EVT_CONN_PARAM_UPDATE event. How to handle this?

I am connecting multiple s130 devices at time. I am not getting any response are event so i am doing
a radio reset on s120.

[Petter Myhre]

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

1. Accept the request and respond with sd_ble_gap_conn_param_update(connection parameters) to update the connection parameters
2. Reject the request and respond with sd_ble_gap_conn_param_update(NULL)
3. 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.

[Petter Myhre]

The first.