Detecting extended advertisements on nRF52840

RE: Detecting extended advertisements on nRF52840

Oscar568 — Tue, 05 Mar 2019 02:00:53 GMT

Can you further elaborate on what you have done I am trying to scan extended advertising as well. Thank you

RE: Detecting extended advertisements on nRF52840

ntn — Tue, 11 Dec 2018 15:14:02 GMT

hi peurpdapeurp, I was in the same situation when the example provided above hit and miss extended advertising packets. Can you point out more detail how you used scan_evt_handler to detect extended advertisements? Which particular scan_evt_id did you use? My use case is open, i.e. filter policy is BLE_GAP_SCAN_FP_ACCEPT_ALL and thus NRF_BLE_SCAN_EVT_NOT_FOUND is always returned. Thanks in advance!

RE: Detecting extended advertisements on nRF52840

peurpdapeurp — Mon, 03 Dec 2018 17:59:17 GMT

Ah I think I have actually figured this out; it seems like it is far better to use the function passed into nrf_ble_scan_init (this is called scan_evt_handler in most of the SDK examples I found) rather than using the function passed into NRF_SDH_BLE_OBSERVER (this was what the ble_evt_handler function I was trying to use was).

I have gotten the detection of extended advertisements working successfully using the scan_evt_handler function rather than the ble_evt_handler function; it just took reading the API's for functions a little more carefully. Hopefully this helps anyone else who gets confused in the same way I did.