RE: Restart Scanning failed - SD140 6.1.0

Kenneth — Thu, 16 Aug 2018 14:43:31 GMT

Hi,

I can see that you have already found the problem and the solution. Here you can find the message sequence chart for sd_ble_gap_connect():
http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.0.0/group___b_l_e___g_a_p___c_e_n_t_r_a_l___c_o_n_n___m_s_c.html

You will either get the BLE_GAP_EVT_CONNECTED or the BLE_GAP_EVT_TIMEOUT event, however if you set timeout to infinite (e.g. .timeout = 0), then you may become stuck forever if the peripheral device is no longer present by the time you call sd_ble_gap_connect(). So it is recommended to set a reasonable timeout (e.g. a few seconds to a minute) in case the peripheral device is no longer present.

Best regards,
Kenneth

RE: Restart Scanning failed - SD140 6.1.0

lolek — Thu, 16 Aug 2018 11:35:00 GMT

I found a solution for the problem above - I changed the Advertising timeout from infinite to 1 min.

if the corrupted sensors tries to connect, after the advertising time out I get BLE_GAP_TIMEOUT_SRC_CONN instead of BLE_GAP_TIMEOUT_SRC_SCAN and then start scanning again.

it seems like a bug...