BLE disconnect

RE: BLE disconnect

run_ar — Tue, 06 Feb 2018 14:09:34 GMT

This should have been posted as a new question.

RE: BLE disconnect

pranavsk1994 — Thu, 14 Sep 2017 22:16:08 GMT

Hi @sidekick, I had a similar kind of doubt regarding the connection interval time for BLE Nordic UART Service on nrf52840 microcontroller with softdevice s140. I want to know after connecting with a nordic mobile app, can the connection remain idle for longer time. If I keep the connection idle it disconnects after certain time The solution you mentioned of replacing "sd_ble_gap_disconnect" with "sd_ble_gap_ppcp_set" in connection parameter event handler, so "sd_ble_gap_ppcp_set" accepts connection parameters as input do I need to initialize the gap connection parameters in event handler again?

RE: BLE disconnect

sidekick — Mon, 04 Jul 2016 09:04:42 GMT

@Kristin: Thank you. The above method worked on Android, however later, while testing with an iOS based device, found that newer version of iOS (v9.3.2) exhibit Bluetooth spec. violation and had to resort to method described here.

RE: BLE disconnect

FormerMember — Wed, 22 Jun 2016 10:51:20 GMT

What you describe should work fine as long as it is fine for your device to accept any connection interval set by the central. However, I would recommend to have some parameter validation.

RE: BLE disconnect

sidekick — Tue, 21 Jun 2016 14:41:46 GMT

@Kristin: Thank you. I followed your suggestion and found that there were multiple problems. 1: I was not properly handling BLE_GAP_EVT_CONN_PARAM_UPDATE event coming from the central (on_ble_event) and 2: there were some explicit call to sd_ble_gap_disconnect(), which I've commented out at the moment. A call to ble_conn_param_init(&cp_init) creates a connection parameter update timer and associates a handler update_timeout_handler with it. It is called MAX_CONN_PARAMS_UPDATE_COUNT number of times if the parameters are not okay with the central and if the central rejects all of those requests from peripheral, the event handler on_conn_params_evt associated with the connection parameter gets invoked, where I was calling sd_ble_gap_disconnect. Now instead of calling sd_ble_gap_disconnect, I accept central's connection parameter by callingsd_ble_gap_ppcp_set in the connection parameter event handler. I know, I should also do some parameter validation, before accepting the values, but is this an okay approach ?

RE: BLE disconnect

FormerMember — Mon, 20 Jun 2016 10:42:18 GMT

I would recommend you to do the following:

Set a breakpoint on all sd_ble_gap_disconnect() calls in your application. When your peripheral device wants to disconnect, it will then stop there. From there, you can start "going backwards" and try to track down the root cause for the disconnect.