This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Why waking up every conn_interval even with slave latency?

I have a min connection interval of 200ms and max of 250ms. I have set slave latency to 10. These parameters are set both on peripheral and on central. Still, after connecting peripheral nRF to oscilloscope I can see that it wakes up every connection interval (~250ms). I expected it to wake up every 2500ms. Is this expected (why?) or do I have some other thing going on in the code?

image description

Parents
  • I am running heavily modified omnipresent UART example (I can upload it though). I have sniffed the link though, pcap log is here. I am not very keen with reading the packets yet, though.

    The only thing happening on central in BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST event is:

    err_code = sd_ble_gap_conn_param_update(p_gap_evt->conn_handle, &p_gap_evt->params.conn_param_update_request.conn_params);
    
Reply
  • I am running heavily modified omnipresent UART example (I can upload it though). I have sniffed the link though, pcap log is here. I am not very keen with reading the packets yet, though.

    The only thing happening on central in BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST event is:

    err_code = sd_ble_gap_conn_param_update(p_gap_evt->conn_handle, &p_gap_evt->params.conn_param_update_request.conn_params);
    
Children
No Data
Related