<?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 reconnection time after an already established bonding</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67424/ble-reconnection-time-after-an-already-established-bonding</link><description>To the kind attention of Nordic support team, 
 we are building some demo program for evaluation purposes using your sdk16 examples with freertos, ble, usb. 
 But we also added many other features that should be needed in our custom application. What</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 22 Oct 2020 07:22:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67424/ble-reconnection-time-after-an-already-established-bonding" /><item><title>RE: BLE reconnection time after an already established bonding</title><link>https://devzone.nordicsemi.com/thread/276347?ContentTypeID=1</link><pubDate>Thu, 22 Oct 2020 07:22:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9175834d-98b4-43ba-91af-53cee567698c</guid><dc:creator>astella</dc:creator><description>&lt;p&gt;Thank you Kenneth for your kindness and your interesting suggestions. In our case, we found that for our custom application can be ok to do directed advertisement. We enabled it using your sdk examples as described in here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/67476/how-to-activate-directed-high-duty-advertising-for-quick-re-connections-after-a-bonding-has-already-been-established"&gt;devzone.nordicsemi.com/.../how-to-activate-directed-high-duty-advertising-for-quick-re-connections-after-a-bonding-has-already-been-established&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE reconnection time after an already established bonding</title><link>https://devzone.nordicsemi.com/thread/276165?ContentTypeID=1</link><pubDate>Wed, 21 Oct 2020 11:49:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0aa7fe76-7584-4934-941e-7d26758d980d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;This sounds like an issue in your demo application (maybe you have a state machine that doesn&amp;#39;t update the leds as it should depending the softdevice events for advertisment, connection, and disconnect), do you observe the same using any of the nRF5 SDK examples? They typically use LED&amp;#39;s to indicate advertising and connected state.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If that is not the case, then you may check that you are advertising without whitelist, in case you have whitelist enabled which may prevent peers to connect. Also have in mind that if you power cycle a device that is connected, the other peer will typically wait a supervisor timeout until it consider the link is lost.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>