Discovery timeout in BLE Central Example Code

[nordicdev]

Hi, I have taken the BLE Central Example code (ble_app_uart_c)in one nRF51822 hardware and in the other nRF51822 hardware, I have taken the BLE Peripheral Example(ble_app_uart) code. I made changes in the central code such that whenever a button is pressed, BLE central would wake up and scan for peripheral.

All works fine for a while (meaning central connects to peripheral, discovers services, exchanges data). After some 10 times, Discovery timeout event happens at BLE Central example code. This is because, after starting a discovery in the central code, a disconnect event happens. This happens especially when the button is pressed in the central board very quickly (meaning, time between successive button presses is very short).

Is there a reason why this happens / has this been already identified? I used sdk10.0.0 and sdk12.3.0 and the above happens in both.

[Petter Myhre]

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?