RE: Unstable advertising startup time

Yves Oesch — Sun, 10 Mar 2024 15:03:12 GMT

Thanks for the clarifications Vidar. After some rework on my timer code it now works fine. Thanks for the efficient support.

RE: Unstable advertising startup time

Vidar Berg — Thu, 29 Feb 2024 10:29:00 GMT

Hello,

The Bluetooth specification requires a random 0 ms to 10 ms delay to be added prior to every advertising event. This is to prevent scenarios where your advertising may become synchronized with advertisement events from other nearby advertisers.

[quote user=""]- Configure the stack to advertise only once then stop advertising. This would allow going to sleep mode quicker. As I have understood, there is a parameter m_adv_params.duration that could be set to 1 to advertise only once, but I get a crash if I use it. (BLE_GAP_EVT_ADV_SET_TERMINATED) So currently it is kept set to 0. Any pointer to working code using this feature?[/quote]

This is what I would have done. Then you can start the advertiser from the timer callback and immediately return to sleep to reduce power consumption. But I'm not sure why this lead to a crash in your application. Do you have logging enabled in your application, and have you checked the return code from the advertising start function?

Also, you may want to consider sending more than one advertisement to increase the probability of it being received by the Observer.

Best regards,

Vidar