<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scanning about 100 beacons at same time</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13718/scanning-about-100-beacons-at-same-time</link><description>Hi,
we have a project in which we have to scan a lot of beacons (up to 100) with Active Scan (scan request and response). We tried to implement this system with actually 6 beacons and we had some problems because with medium large advertising interval</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 10 May 2016 12:23:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13718/scanning-about-100-beacons-at-same-time" /><item><title>RE: Scanning about 100 beacons at same time</title><link>https://devzone.nordicsemi.com/thread/52428?ContentTypeID=1</link><pubDate>Tue, 10 May 2016 12:23:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7eea40b-3c30-4cdd-b29e-90ba93e9a41c</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;You will always miss some advertisement packets. Even if you do continuous scanning and there are only one broadcaster you will probably lose 1/1000 packets due to other interference. If you don&amp;#39;t want to loose any packets you need to connect to the peer device or implement some system for re-transmitting packets. There is a resent case &lt;a href="https://devzone.nordicsemi.com/question/78614/how-to-deal-with-broadcasting-collision/#78619"&gt;here&lt;/a&gt; about the probability of a packet collision.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>