Scan timeout behavior in SDK 15 - Bug?/Workaround?

[Andy]

Hi,

I just found out that the scanning procedure does not time out in SDK 15. This is because in SDK 15 we are forced to restart the scanning procedure everytime an advertisement report event is received. When I restart the procedure, the timeout is reset.

The behavior I expected is the following: I want to scan for just 1 minute, I set the timeout to 1 minute. The timeout instead is 1 minute from the last advertisement report received. If my device is near a beacon or some other device that is constantly advertising, my device will never stop scanning.

Is this the behavior the Nordic team intended?

[tesc]

Hi,

The intended behavior is that when receiving an advertising report, you continue scanning by calling sd_ble_gap_scan_start() with p_scan_params of NULL. The original scan, which was put on pause when generating the BLE_GAP_EVT_ADV_REPORT event, will then be continued. The timeout will then still be the "old" one. See the sd_ble_gap_scan_start() documentation for details.

Regards,
Terje

[Andy]

Ok, so if I put NULL then the behavior is as intended. Is this documented anywhere? If not, I encourage you to :)

[Andy]

Nevermind, just saw it.