https://devzone.nordicsemi.com/f/nordic-q-a/60877/beacon-advertising-and-scanning-inconsistentHi, I&#39;ve developed firmware for nRF52832 to beacon and scan for identical beacons. So with many devices, each can detect the others. What I&#39;ve noticed is that while most devices detect most beacons, 2 devices might &#39;synchronize&#39; and miss most of eachen-USTelligent Community 13Thu, 30 Apr 2020 12:52:56 GMThttps://devzone.nordicsemi.com/thread/247565?ContentTypeID=1Thu, 30 Apr 2020 12:52:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5cb2a5a0-6a76-4695-9e64-3ae86efbf5d9Jacques<p>Thanks Simon,</p> <p>The random delay is definitely not something I would want to remove. Making smaller scanning windows and intervals seems to improve things. I think that this is because the scanner is switching between the 3 advertising channels more frequently (?)</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/247562?ContentTypeID=1Thu, 30 Apr 2020 12:47:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:89f5d874-671e-4037-a52a-df43b20ccad1Simonr<p>Hi</p> <p>There might be multiple reasons for this inconsistency, but here is one possible cause. This is just based on the information provided and the first thing that came to mind.</p> <p>In the BLE specification, it is required to add a random delay of 0-10 ms to your requested advertising interval. This is added in the link layer in the SoftDevice, and the application has no control<span>&nbsp;</span>of<span>&nbsp;</span>this delay. By increasing the&nbsp;advertising intervals or scan windows you should be able to mitigate this, but there&#39;s no way (in the BLE spec.) to remove this random delay.</p> <p>Best regards,</p> <p>Simon</p><div style="clear:both;"></div>