Issue with advertising restart after disconnect...

[mstrouse]

All,

Can anyone tell me what is the fastest time that a ble SD (5.x / 6.x) running on an nRF51 can (re)start advertising from a disconnect. Basically looking to do an [advertise -> connect -> receive (1 byte) -> disconnect] and then back to advertise as quickly as possible... Right now I'm seeing turn around times in the 5-7 second range.

Before you ask ... it is not related to the central (in this case an iOS device) ... already checked that box. Would appear (after doing some debugging) that this issue is in the SD.

I tried to force this by doing a:

sd_ble_gap_disconnect(s_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);

followed by an:

advertising_start();

in another "thread" after the receive (a write to my peripheral handle), and the part does not like that ... causes a fault / reset.

MS.

[mstrouse]

This has now been solved. After investigation / debugging, the issue was a combination of a coding mistake and needing to restructure some code. The turn around time (between disconnect and the start of advertising) is now in the few hundred milliseconds range.

[Lully-Mark]

The heartrate app is heavily modified, but quite a bit of the structure (especially of main.c) is the same. The advertising, connection parameters, and functions are almost exactly the same. They added some GATTS services and characteristics in another piece of code as well, so I'm trying to trace the delay. I was hoping that whatever you found would provide some insight to try to track down what may be going on in our code as well.