https://devzone.nordicsemi.com/f/nordic-q-a/12662/scan-beaconsHi. I&#39;m currently trying to scan beacons with timeslot example. However, I found that there&#39;re more than 20% of loss while scanning beacons broadcast. I think that&#39;s huge even if broadcast has no guarantee to be transferred. I set up 1 beaconen-USTelligent Community 13Wed, 06 Apr 2016 08:36:03 GMThttps://devzone.nordicsemi.com/thread/48116?ContentTypeID=1Wed, 06 Apr 2016 08:36:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:86602303-1aac-4fab-9daf-0b0fc9d99e16endnode<p>Hi, hard to even spot the update in your question. have you thought about some better structuring (when it comes to technical debate)?;) Cheers Jan</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/48115?ContentTypeID=1Sat, 19 Mar 2016 20:38:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:aab7941d-b371-4cda-80bb-466fe5642676endnode<p>Hi,</p> <p>Any particular reason why you do it with timeslot API? When using normal dual-role stack (S130) on nRF51 DK I have basically zero packet loss when scanning with 100% duty cycle down to 10 broadcasters @20ms interval (beacons if you want but I simply use connectable adv. to be able to go below 100ms with standard BLE stack). If S13x scans at 100% duty cycle I get resolution down to ~1 adv per ms (1000 adv. reports per second) and if I&#39;d be also advertising I expect to keep it very close to that because advertising Tx+Rx blocks radio for &lt;1ms.</p> <p>Cheers Jan</p><div style="clear:both;"></div>