<?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>BLE Adv Interval</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25344/ble-adv-interval</link><description>I am working on S140 on nRF25840. I am using the ble_app_beacon sample.
I want to set the advertising interval smaller than 100ms while using non-connectable mode. But the BLE_GAP_ADV_NONCON_INTERVAL_MIN stops me. I wonder if there is any reason to set</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 22 Sep 2017 10:12:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25344/ble-adv-interval" /><item><title>RE: BLE Adv Interval</title><link>https://devzone.nordicsemi.com/thread/99883?ContentTypeID=1</link><pubDate>Fri, 22 Sep 2017 10:12:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:847569a1-b41a-43db-90c3-abed003271f1</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;As long as you don&amp;#39;t have whitelisting it will accept any connection request.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Adv Interval</title><link>https://devzone.nordicsemi.com/thread/99881?ContentTypeID=1</link><pubDate>Fri, 22 Sep 2017 08:48:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:665a3b89-faec-4c96-88a9-37fdf860df1f</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;But then SD will accept CONNECT_REQ? And what if the FW doesn&amp;#39;t want to handle any? Yes, it can terminate it straight away and also open another broadcasting in parallel so it will have &amp;quot;minimal&amp;quot; visible impact but there still we be some and also power consumption can be higher (if anyone cares). So having high frequency non-connectable broadcasts isn&amp;#39;t such a bad idea...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Adv Interval</title><link>https://devzone.nordicsemi.com/thread/99882?ContentTypeID=1</link><pubDate>Fri, 22 Sep 2017 08:35:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6f69b40d-239f-40a2-a554-6ba72206cc2a</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;The 100 ms limitation is only for non-connectable advertising. You can use connectable advertising with less than 100 ms. Doesn&amp;#39;t make your communication &amp;quot;wrong&amp;quot;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Adv Interval</title><link>https://devzone.nordicsemi.com/thread/99886?ContentTypeID=1</link><pubDate>Thu, 21 Sep 2017 02:39:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f5e65f31-0b25-4c76-86aa-93699a91beb9</guid><dc:creator>mich_x</dc:creator><description>&lt;p&gt;What if I use connectable mode, while the scan machine does not try to connect. Does it make the communication somehow wrong? Can I set the adv interval smaller than 100ms.&lt;/p&gt;
&lt;p&gt;BTW, the spec is long. My deadline doesn&amp;#39;t allow me to read them through. :(&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Adv Interval</title><link>https://devzone.nordicsemi.com/thread/99885?ContentTypeID=1</link><pubDate>Thu, 21 Sep 2017 02:25:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:72969de9-0907-4bf3-b604-04dbfe5f74c6</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;I didn&amp;#39;t know that - I guess I have to read the whole bloody spec again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Adv Interval</title><link>https://devzone.nordicsemi.com/thread/99884?ContentTypeID=1</link><pubDate>Thu, 21 Sep 2017 02:24:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e401bfb-b4c9-4ed4-9347-3e6b9e066caa</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Btw. BT 5.0 lifted this limitation for non-connectable adv. interval and &lt;a href="https://devzone.nordicsemi.com/question/142499/s140-non-connectable-advertising-interval/"&gt;Nordic team plans to update S140/132 stacks in the future&lt;/a&gt;...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Adv Interval</title><link>https://devzone.nordicsemi.com/thread/99880?ContentTypeID=1</link><pubDate>Thu, 21 Sep 2017 02:21:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aec2572b-a2b6-4c24-87bf-84737321caea</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;The reason is the BLE spec says that non-connectable advertising shall not have an advertising interval less than 100ms and the softdevice is certified to follow the spec.&lt;/p&gt;
&lt;p&gt;Correct, ADV_NONCONN_IND cannot be scanned. Again those terms are buried in the incredibly long BLE spec.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;ADV_DIRECT_IND    - connectable, not scannable, directed
ADV_IND           - connectable, scannable, undirected
ADV_NONCONN_IND   - not connectable, not scannable, undirected
ADV_SCAN_IND      - not connectable, scannable, undirected
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>