According to the documentation of the softdevice v6. The scanner will automatically stop in the following cases: sd_ble_gap_scan_stop is called. sd_ble_gap_connect is called. A BLE_GAP_EVT_TIMEOUT with source set to BLE_GAP_TIMEOUT_SRC_SCAN is received. When a BLE_GAP_EVT_ADV_REPORT event is received and ble_gap_adv_report_type_t::status is not set to BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA . In this case scanning is only paused to let the application access received data. The application must call this function to continue scanning, or call sd_ble_gap_scan_stop to stop scanning. I just want to check. Is there a specification about this in the BLE spec? I tried to find it myself but could not see any. Thank you. Jie

This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Softdevice v6. Scan pause specification

mich_x over 7 years ago

According to the documentation of the softdevice v6.

The scanner will automatically stop in the following cases:

sd_ble_gap_scan_stop is called.
sd_ble_gap_connect is called.
A BLE_GAP_EVT_TIMEOUT with
source
set to BLE_GAP_TIMEOUT_SRC_SCAN is received.
When a BLE_GAP_EVT_ADV_REPORT event is received and ble_gap_adv_report_type_t::status is not set to BLE_GAP_ADV_DATA_STATUS_INCOMPLETE_MORE_DATA. In this
case
scanning is only paused to let the application access received data. The application must call this function to continue scanning, or call sd_ble_gap_scan_stop to stop scanning.

I just want to check. Is there a specification about this in the BLE spec?

I tried to find it myself but could not see any.

Thank you.

Jie

Parents

0 run_ar over 7 years ago

Hi,

As far as I know this is implementation specific. I.e. previously (before v6 api) it was not necessary to restart scanning when a ble_gap_evt_adv_report event was received.
0 mich_x over 7 years ago in reply to run_ar

Yes, exactly. This is why I have some concerns about this? If you automatically stop the scan and depends on the program to restart it, then how does it guarantee that the scanning will not miss the next possible beacon?

Reply

0 mich_x over 7 years ago in reply to run_ar

Yes, exactly. This is why I have some concerns about this? If you automatically stop the scan and depends on the program to restart it, then how does it guarantee that the scanning will not miss the next possible beacon?

Children

0 run_ar over 7 years ago in reply to mich_x

Well, there is no guarantee. It is a trade off, and necessary to give the chip some time to access the received data. As you pasted originally: "In this case scanning is only paused to let the application access received data.".