Discovery timeout in BLE Central Example Code

RE: Discovery timeout in BLE Central Example Code

Petter Myhre — Tue, 21 Nov 2017 18:30:39 GMT

You can check p_ble_evt->evt.gap_evt.params.disconnected.reason when you get BLE_GAP_EVT_DISCONNECTED.

RE: Discovery timeout in BLE Central Example Code

nordicdev — Tue, 21 Nov 2017 02:29:37 GMT

Hi Petter Myhre, thanks for the reply. I didnt know what caused the disconnected event - do you recommend any way to check that? Before the short press of the button the nrf51 runs in peripheral mode. After the short button press, the nRF51 reboots into central mode and scans and connects to peripheral if uuid matches. I run the example code of ble_central and ble_peripheral_uart. In the central code, I disabled all the places where start_scan is called, except for the first time. So, the central code basically scans only once upon boot up.

RE: Discovery timeout in BLE Central Example Code

Petter Myhre — Mon, 13 Nov 2017 12:58:03 GMT

You get a BLE_GAP_EVT_DISCONNECTED event in the central application? Have you checked the reason the struct? So what does short presses of the button do? What code do you run? Is it okay to run this code if you are already scanning?