RE: The effects of slave latency

andrey — Fri, 18 May 2018 00:22:22 GMT

Thanks updating the connection parameters at BLE_GAP_EVT_CONNECED has worked.

Here's the code:

static void on_ble_evt(ble_evt_t * p_ble_evt)
{
    uint32_t err_code;

    switch (p_ble_evt->header.evt_id) {
        case BLE_GAP_EVT_CONNECTED:
            err_code = bsp_indication_set(BSP_INDICATE_CONNECTED);
            APP_ERROR_CHECK(err_code);
            m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
        
            // ADDED THIS
            ble_gap_conn_params_t p_conn_params;
            p_conn_params.min_conn_interval = p_ble_evt->evt.gap_evt.params.connected.conn_params.min_conn_interval;
            p_conn_params.max_conn_interval = p_ble_evt->evt.gap_evt.params.connected.conn_params.max_conn_interval;
            p_conn_params.slave_latency     = SLAVE_LATENCY;
            p_conn_params.conn_sup_timeout  = p_ble_evt->evt.gap_evt.params.connected.conn_params.conn_sup_timeout;

            err_code = sd_ble_gap_conn_param_update(m_conn_handle, &p_conn_params);
            APP_ERROR_CHECK(err_code);
            //
        
            break;

        case BLE_GAP_EVT_DISCONNECTED:
            m_conn_handle = BLE_CONN_HANDLE_INVALID;
            break;
        
        case BLE_GAP_EVT_CONN_PARAM_UPDATE:
            break;

        default:
            // No implementation needed.
            break;
    }
}

RE: The effects of slave latency

jing — Wed, 09 May 2018 03:48:09 GMT

You should first check the effective connection parameter on BLE_GAP_EVT_CONNECTED.

Assuming that you are using ble_conn_params.c module, take note that it only checks for the connection interval. As long as the effective connection interval is within your desired min and max, it will not initiate a Connection Parameter Update Request.

jing