s110 connection parameters negotiation

[Wojtek]

My peripheral device connects with central one very rarely. I decided that I don't want peripheral to negotiate connection parameters with central, just use settings imposed by central. I've used function from some example:

static void conn_params_init(void){
uint32_t               err_code;
ble_conn_params_init_t cp_init;

memset(&cp_init, 0, sizeof(cp_init));

cp_init.p_conn_params                  = NULL;
cp_init.first_conn_params_update_delay = FIRST_CONN_PARAMS_UPDATE_DELAY;
cp_init.next_conn_params_update_delay  = NEXT_CONN_PARAMS_UPDATE_DELAY;
cp_init.max_conn_params_update_count   = MAX_CONN_PARAMS_UPDATE_COUNT;
cp_init.start_on_notify_cccd_handle    = BLE_GATT_HANDLE_INVALID;
cp_init.disconnect_on_fail             = false;
cp_init.evt_handler                    = on_conn_params_evt;
cp_init.error_handler                  = conn_params_error_handler;

err_code = ble_conn_params_init(&cp_init);
APP_ERROR_CHECK(err_code);

}

I just commented it line with call of this function, and I don't receive BLE_GAP_EVT_CONN_PARAM_UPDATE events anymore. That would solve my problem, but after connecting and disconnecting (without any negotiations...) my device doesn't advertise anymore. I use timers to call advertising start/stop. No assert is shown on debug after that. Is it possible that interrupts stop working somehow?

[Wojtek]

It turned out that was not good idea to replace the code as you said.

My application uses other timers and while receiving events such as gap disconnect, the m_conn_params_timer_id code that wasn't removed messed up with my timer (actually it stopped it). So i just set min/max connection parameters same on central and peripheral.