<?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>Unexpected disconnection of nRF8002</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8119/unexpected-disconnection-of-nrf8002</link><description>Hi everyone, 
 We&amp;#39;re working with nFR8002 devices, and it works fine most of the time.
Even after losing the link intentionnally (Bluetooth stopped, or walking out of Bluetooth range), they all reconnect easily if the link is already possible. 
 However</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 13 Jul 2015 12:06:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8119/unexpected-disconnection-of-nrf8002" /><item><title>RE: Unexpected disconnection of nRF8002</title><link>https://devzone.nordicsemi.com/thread/29149?ContentTypeID=1</link><pubDate>Mon, 13 Jul 2015 12:06:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e30908f0-78fe-4ecd-9404-4f618f9d3333</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Victor: I guess you also have registered a case on our Support portal (by Hugo). I don&amp;#39;t have any other idea, beside what you already mentioned here that there could be the chance that the central rejected the Connection update request and because of the the nRF8002 disconnect and enter sleep mode.&lt;/p&gt;
&lt;p&gt;If possible, could you try to record a &lt;a href="https://www.nordicsemi.com/eng/Products/Bluetooth-Smart-Bluetooth-low-energy/nRF-Sniffer/(language)/eng-GB"&gt;sniffer trace&lt;/a&gt; and capture the moment when it&amp;#39;s disconnected from the central ? We should be able so find the root cause with the trace.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>