RE: BLE multilink inherent 1 second scheduling?

pcalleme — Tue, 03 Oct 2017 14:49:33 GMT

After hours of digging into this problem, finally solved the issue. The answer is not a difficult one and lies in altering the minimum and maximum connection times in ble_gap_conn_params in the connection manager code as follows:

/**
 *  Scan parameters requested for connection. 
 */
static const ble_gap_conn_params_t m_cnxn_param = 
{
    MSEC_TO_UNITS(50, UNIT_1_25_MS),                               // Minimum connection 
    MSEC_TO_UNITS(200, UNIT_1_25_MS),                              // Maximum connection     
    0,                                                              // Slave latency 
    MSEC_TO_UNITS(CONN_MNGR_SUPERVISION_TIMEOUT, UNIT_10_MS)        // Supervision time-out
};

I was confusing these values with the scan parameters. Problem solved.