<?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>What is the order in which BLE signals are &amp;quot;seen&amp;quot; at the link layer or below?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/64829/what-is-the-order-in-which-ble-signals-are-seen-at-the-link-layer-or-below</link><description>I&amp;#39;m wondering how BLE signals are handled at the layer below the scanning module. Namely, suppose there are hundreds of BLE modules that are all advertising nearby. How does the lower-level logic work in determining which signals &amp;quot;bubble up&amp;quot; to the stack</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Aug 2020 13:15:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/64829/what-is-the-order-in-which-ble-signals-are-seen-at-the-link-layer-or-below" /><item><title>RE: What is the order in which BLE signals are "seen" at the link layer or below?</title><link>https://devzone.nordicsemi.com/thread/264885?ContentTypeID=1</link><pubDate>Mon, 17 Aug 2020 13:15:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:546a68fd-6f9b-4883-b8b1-bc2d280a2f81</guid><dc:creator>Edvin</dc:creator><description>[quote user="glenn_zelniker"]signals with the highest power?&amp;nbsp;[/quote]
&lt;p&gt;&amp;nbsp;No, the signal that occurs first (in time, not signal strength).&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is the order in which BLE signals are "seen" at the link layer or below?</title><link>https://devzone.nordicsemi.com/thread/264858?ContentTypeID=1</link><pubDate>Mon, 17 Aug 2020 12:24:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a1813d83-0c0a-4640-8ee0-934a5fd6a3e3</guid><dc:creator>Glenn Zelniker</dc:creator><description>&lt;p&gt;Edvin,&lt;/p&gt;
&lt;p&gt;I am asking specifically about what happens at a layer below the one at which filtering and whitelisting occurs. What does the radio see first and pass up to the stack: signals with the highest power?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Glenn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is the order in which BLE signals are "seen" at the link layer or below?</title><link>https://devzone.nordicsemi.com/thread/264803?ContentTypeID=1</link><pubDate>Mon, 17 Aug 2020 09:24:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0aa3f17-8b9d-4b35-93b4-ea9e130c7f85</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;When scanning, you are scanning on a specific advertising channel, 37, 38 or 39. The Softdevice will scan on one channel for the duration of your scan window, set in sdk_config.h (if you are using one of the later SDKs). Then it will wait for the next scan interval to start, and then scan on the next channel for the next scan window.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;When scanning, the softdevice will pick up the first advertising packet it can find, unless you are using bonding and whitelisting. Typically, our central examples are using some sort of filter. Either an advertising name or a specific UUID is used. Look for the filter_set() function in scan_init(), and see how the filters are applied in the BLE_GAP_EVT_ADV_REPORT event, which calls nrf_ble_scan_on_adv_report(), in nrf_ble_scan.c.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you can&amp;#39;t find this function, please let me know what SDK version you are using.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>