<?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>From Discoverable to Non-discoverable (but still connectable!) using the Advertising Library</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25551/from-discoverable-to-non-discoverable-but-still-connectable-using-the-advertising-library</link><description>Is it possible to configure the parameters of the advertising library (eg. SDK v12.3.0 using SD130 v2.0.1) so that my peripheral device (eg. nRF51) changes after a limited time -say 2 minutes- from limited discoverable into non-discoverable but remaining</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 03 Oct 2017 13:10:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25551/from-discoverable-to-non-discoverable-but-still-connectable-using-the-advertising-library" /><item><title>RE: From Discoverable to Non-discoverable (but still connectable!) using the Advertising Library</title><link>https://devzone.nordicsemi.com/thread/100738?ContentTypeID=1</link><pubDate>Tue, 03 Oct 2017 13:10:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17aabfdf-835f-492f-af5c-4f2818946549</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;No, i think Darrew is correct here. &amp;quot;Discoverability&amp;quot; is a concept that is easy to misunderstand. When you advertise, every scanner can see that advertisement, period. That&amp;#39;s regardless of the contents of the advertisement. But in the PDU, you can set some flags to give a hint to the scanner. What you make out of these hints is up to you, but the other advertisement parameters are largely unaffected by these flags. Some scanners might be on the lookout for general discoverable devices, prioritizing to display those over limited/non-discoverable ones.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: From Discoverable to Non-discoverable (but still connectable!) using the Advertising Library</title><link>https://devzone.nordicsemi.com/thread/100737?ContentTypeID=1</link><pubDate>Fri, 29 Sep 2017 09:45:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3558fd46-7aeb-482f-bbf6-b0415c9cf7a8</guid><dc:creator>Darrew</dc:creator><description>&lt;p&gt;Ok, let&amp;#39;s say my device should be &lt;strong&gt;discoverable for a limited period&lt;/strong&gt; of time and &lt;strong&gt;connectable&lt;/strong&gt; all the time. How would you set up the advertising library to do that?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: From Discoverable to Non-discoverable (but still connectable!) using the Advertising Library</title><link>https://devzone.nordicsemi.com/thread/100736?ContentTypeID=1</link><pubDate>Thu, 28 Sep 2017 20:43:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c9d94951-1699-4c03-8be3-2460dc96518b</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;I&amp;#39;m afraid your understanding of BT SIG specification contradicts with &lt;a href="https://devzone.nordicsemi.com/question/164203/ble-advertising-data-flags-field-and-discovery/"&gt;understanding of other people here on the forum...&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: From Discoverable to Non-discoverable (but still connectable!) using the Advertising Library</title><link>https://devzone.nordicsemi.com/thread/100735?ContentTypeID=1</link><pubDate>Thu, 28 Sep 2017 13:44:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e2075bed-2e76-4dae-a3d0-698bc4107679</guid><dc:creator>Darrew</dc:creator><description>&lt;p&gt;The standard Core4.2 says:
&amp;quot;... A device configured in non-discoverable mode will not be discovered by any
device that is performing either the general discovery procedure or the limited
discovery procedure.&amp;quot;&lt;/p&gt;
&lt;p&gt;moreover,&lt;/p&gt;
&lt;p&gt;&amp;quot;...A device in the undirected connectable mode shall accept a connection
request from a device performing the auto connection establishment procedure
or the general connection establishment procedure.&amp;quot;&lt;/p&gt;
&lt;p&gt;Both modes are not incompatible.&lt;/p&gt;
&lt;p&gt;A device can be in both non-discoverable mode and connectable mode (eg. undirected).
In other words, it may allow connections from a peer device performing any connection establishment procedure but it will not be discoverable to those performing any discovery procedure.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: From Discoverable to Non-discoverable (but still connectable!) using the Advertising Library</title><link>https://devzone.nordicsemi.com/thread/100734?ContentTypeID=1</link><pubDate>Thu, 28 Sep 2017 13:13:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c07da4a9-72a8-4174-8981-f9f4bfdcb776</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Non-discoverable means not connectable.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>