RE: Inquiries about Central beacon scanner

Hung Bui — Thu, 02 Jan 2020 15:35:57 GMT

Hi Leejh,

As you can find the flow chart of the scanning mechanism here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___g_a_p___s_c_a_n___m_s_c___l_e_g_a_c_y.html?cp=4_5_2_1_2_1_5_14_0

From S132/S140 version 6.x, you would need to resume scanning by calling sd_ble_gap_scan_start() every time you get a adv_report event.

The interval and scan window still applied until the packet event is sent to the application. The application should call sd_ble_gap_scan_start() as soon as possible. The softdevice when receiving sd_ble_gap_scan_start() will not restart the scanning, but just continue the scheduled scanning. The call is just to tell the softdevice that the buffer is now safe to use and it can continue to scan.

2. I'm not aware of an option to scan by Manufacturer UUID. What we have in our nrf_ble_scan module is to scan by the service UUID, not the Manufactuerer UUID. But you can implement that on your own by handling the adv_report event.