<?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>nRF51 beacon high frequency scanning and advertising?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8897/nrf51-beacon-high-frequency-scanning-and-advertising</link><description>Hello, beginner here. :) 
 I just bought an nRF51 DK, but have not received it yet. 
I decided to test it because my older BLE module (HM-11) only allowed me to scan beacons once every 3 seconds. 
 My intention: using nRF51822 chips I want to make</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 28 Aug 2015 09:16:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8897/nrf51-beacon-high-frequency-scanning-and-advertising" /><item><title>RE: nRF51 beacon high frequency scanning and advertising?</title><link>https://devzone.nordicsemi.com/thread/32728?ContentTypeID=1</link><pubDate>Fri, 28 Aug 2015 09:16:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a0dff57-3268-434f-8756-e3826f0b92ba</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Luis,&lt;/p&gt;
&lt;p&gt;I meant why do you want to have lower than 100ms advertising interval ? It&amp;#39;s based on my assumption that you want higher frequency than 10Hz.&lt;/p&gt;
&lt;p&gt;Regarding the test, no, we haven&amp;#39;t done any test like that. But the time frame needed to transmit 3 advertising packet is around 2ms. The scanner can be scanning all the time (on 3 channels, one by one in turn). I guess you can use Mathlab or other tools to do the simulation and calculate the transmit success rate base on your desired advertising interval.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51 beacon high frequency scanning and advertising?</title><link>https://devzone.nordicsemi.com/thread/32727?ContentTypeID=1</link><pubDate>Thu, 27 Aug 2015 11:17:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a1fd5f3-c03d-438b-ad0c-4a25cb04f790</guid><dc:creator>Luis</dc:creator><description>&lt;p&gt;Thank you very much for your answers. When you say &amp;quot;the advertising interval should be lower than&amp;quot; I think that is a typo and you meant &amp;quot;higher&amp;quot;.
I understand that is the Bluetooth Core Spec. So the softdevice won&amp;#39;t let me go over that spec and I have to use the two workarounds you noted? Connectable up to 50Hz and stop+restart for higher frequencies?
Do you know of any tested case like this? In order to estimate what is the highest advertising/scanning frequency I may reach using 5 beacons and 1 scanner (all with nrf51) in the same room?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51 beacon high frequency scanning and advertising?</title><link>https://devzone.nordicsemi.com/thread/32726?ContentTypeID=1</link><pubDate>Thu, 27 Aug 2015 11:16:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96d2694a-166d-42ef-81cf-556ce66492f5</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;One more thing, since non-connectable advertising will most likely be transmitted all the time ( e.g beacon) having larger advertising interval will reduce the chance of interference between them.&lt;/p&gt;
&lt;p&gt;When doing connectable advertising, the device not supposed to advertise all the time, main point is to get connected. So it can have shorter interval.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51 beacon high frequency scanning and advertising?</title><link>https://devzone.nordicsemi.com/thread/32725?ContentTypeID=1</link><pubDate>Thu, 27 Aug 2015 11:06:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54bbaa0b-ced7-456e-9b3e-d80d743d5862</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@mst: It was defined in the Bluetooth specification. I have the reference to the spec in my answer.&lt;/p&gt;
&lt;p&gt;From my point of view the 100ms minimum limitation is due to the requirement to be low power consumption. For connectable advertising the minimum limitation of 20ms is to make sure the connection can be quickly established. It&amp;#39;s not the case when doing non-connectable advertising.&lt;/p&gt;
&lt;p&gt;No technical reason here, just to make sure the power consumption remains low when using the protocol.&lt;/p&gt;
&lt;p&gt;Do you have a reason that the advertising interval of your beacon should be lower than 100ms ? Note that if your beacon running on CR2032 battery, having a 100ms advertising interval or lower, will drain your battery in less than 3 months.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51 beacon high frequency scanning and advertising?</title><link>https://devzone.nordicsemi.com/thread/32724?ContentTypeID=1</link><pubDate>Wed, 26 Aug 2015 14:46:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a55f1a79-0532-4613-a7bb-fa8068182051</guid><dc:creator>mst</dc:creator><description>&lt;p&gt;Reading this answer makes me wonder.. What is the main (technical) reason that when using non-connectable advertising, the advertising interval should be at least 100ms, while for connectable advertising it can be at least 20ms? Or is there none, and therefore it can be overruled by stopping and re-starting advertising with an interval lower than 100ms?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51 beacon high frequency scanning and advertising?</title><link>https://devzone.nordicsemi.com/thread/32723?ContentTypeID=1</link><pubDate>Wed, 26 Aug 2015 13:10:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd3c0905-dd9f-4daa-915b-18d5872113e0</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Luis,&lt;/p&gt;
&lt;p&gt;Yes, you can use the nRF51 to scan for several beacons with higher than 10Hz frequency.&lt;/p&gt;
&lt;p&gt;If you advertise as non-connectable advertising, the advertising interval should be lower than 100ms. ( Section 4.4.2.2 Vol 6 Part B in Bluetooth Core Spec v4.4.2.2)&lt;/p&gt;
&lt;p&gt;You can get away from that either by advertise with connectable advertising or you can advertise with non-connectable advertising, but stop and re-start advertising with interval lower than 100ms.&lt;/p&gt;
&lt;p&gt;When advertising, there will be an extra delay added, to avoid interference (define at the same place at section 4.4.2.2). So you don&amp;#39;t have to worry that all the beacon will advertise at the same time.&lt;/p&gt;
&lt;p&gt;The scanner can scan continuously (when you set scan windows= scan interval) however, we have to scan on 3 channels (37, 38, 39) so we will scan on each channel in turn, one by one on one scan window. ( One scan window with channel 37 , next window with channel 38 and so on). Note that when advertising, by default the advertiser advertises in all 3 channels one after each other.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>