Scanning parameter settings to get the most advertisements but also handle connections

RE: Scanning parameter settings to get the most advertisements but also handle connections

ovrebekk — Thu, 04 Apr 2024 06:46:59 GMT

Hi Manuel

I discussed this with the developers, and they pointed out that when you set the scan interval and window to the same value the scheduler uses so called cooperative scanning to maximize scanning duty cycle, while letting other activities such as connections or advertisements occur in between.

This is described in more detail here.

In other words my earlier comment regarding scan interval and window is incorrect, sorry for the confusion.

With this in mind it makes sense that you see better performance when using 50/50 compared to 200/150. You could try higher values also, like 100/100 or 200/200, but I wouldn't expect a dramatic difference.

Best regards
Torbjørn

RE: Scanning parameter settings to get the most advertisements but also handle connections

Phobios — Wed, 03 Apr 2024 11:15:09 GMT

Hi Torbjørn,

I've tried your settings. The peripherals are currently sending periodic advertisements every second
With the scanning to 200/150 I only get around 1/3 of the advertisements which are sent out, with greater distance even only about 1/6 - I have far better results with 50 /50...

What can I do to improve the receiving of the advertisements?
Is it better to send out advertisement bursts in a greater interval?

Thanks and best Regards,
Manuel

RE: Scanning parameter settings to get the most advertisements but also handle connections

ovrebekk — Tue, 02 Apr 2024 09:18:10 GMT

Hi Manuel

Sorry for the slow response, it has been pretty hectic here around the Easter holidays.

Setting the scan interval and window to the same is not a good idea, then you will get a lot of scheduling conflicts between your connections and the scanning. Scanning has lower priority than connections and would typically be down prioritized, and you would see scanning duty cycle drop.

By default the central connections should be scheduled 2.5ms apart, which means 20 connections should occupy 50ms every 200ms when using this connection interval.

Could you try to set the scan interval to 200ms and the scan window somewhere in the 100-150ms range?

Then the stack should be able to schedule scanning and connections without any conflict.

Best regards
Torbjørn

RE: Scanning parameter settings to get the most advertisements but also handle connections

Tyta — Sun, 24 Mar 2024 14:05:27 GMT

[deleted]