Can't scan extended advertise packets using nrf-ble-driver

RE: Can't scan extended advertise packets using nrf-ble-driver

Simonr — Thu, 21 Nov 2019 08:54:17 GMT

No, I'm sorry, the official reply is that SoftDevice v.6 is not suited for serialization. Related discussion on the matter can be found in this DevZone thread as well.

Best regards,

Simon

RE: Can't scan extended advertise packets using nrf-ble-driver

Simonr — Wed, 20 Nov 2019 07:24:46 GMT

Not to my knowledge, but I'll ask internally and get back to you with a definitive answer.

Best regards,

Simon

RE: Can't scan extended advertise packets using nrf-ble-driver

Ivlampiy223 — Tue, 19 Nov 2019 14:44:14 GMT

I tried to test it with nordic blinky. I moved full name to response and changed adv interval. Got same results. Fast response with small interval and unacceptable slow (about 45 sec) response with 2000 ms interval.

RE: Can't scan extended advertise packets using nrf-ble-driver

Ivlampiy223 — Tue, 19 Nov 2019 14:21:38 GMT

Delay is 4-10 secs for 100 ms advertise and up to minute or even more for device with 2000 ms advertise period. Sometimes it catches fast, but sometimes it unacceptable slow.

I measured delay in my application and it takes 2-7 ms between ble event handler start and scan_start called. I use qt, emit event and resume scan, event is being processed in another thread.

I use nRF Connect for desktop and for android.

So is there way to make it work except moving to older API?

RE: Can't scan extended advertise packets using nrf-ble-driver

Simonr — Tue, 19 Nov 2019 08:41:37 GMT

How large are the delays in scan responses you are seeing? The delay between the BLE_GAP_EVT_ADV_REPORT events until scanning is resumed again with sd_ble_gap_scan_start() is the root of this issue. This is present in SoftDevice versions 6 and later.

The pc-ble-driver has support for SoftDevice API versions 2, 3, 5 and 6. nRF Connect for Desktop still uses SoftDevice v3, also for the nRF52840, which is why the scan response is faster on the nRFConnect for desktop app. Note that nRF52840 products that are going to be listed with Bluetooth SIG need to use SoftDevice version 6 or newer according to this QDID list.

A full recap of this issue can be found in this case. I'm afraid there is no fix for this delay issue at the moment.

Best regards,

Simon

RE: Can't scan extended advertise packets using nrf-ble-driver

Ivlampiy223 — Mon, 18 Nov 2019 15:28:04 GMT

Thank you for answer, Simon!

I am using nRF Connect advertiser and other applications. That was my mistake that i didn't get extended packets. I thought that nRF Connect shows really raw data under "RAW" button. There wasn't extended packets. I tried to create really extended packet and it works perfectly.

So the problem is that i'm getting scan responses slower than nRF Connect app. How to configure it for best perfomance?

RE: Can't scan extended advertise packets using nrf-ble-driver

Simonr — Mon, 18 Nov 2019 13:46:59 GMT

What beacon application is it that you're trying to scan? Do you have the beacon's application code?

The nRFConnect app also uses data from the scan response packet in order to get all the information, as there isn't enough room in a single advertising packet for all that information.

Best regards,

Simon