<?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>How to determine if a disconnection is due to a bad signal (signal loss)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/1992/how-to-determine-if-a-disconnection-is-due-to-a-bad-signal-signal-loss</link><description>Hi, 
 I am trying to detect if a disconnection occurs due to a signal loss. 
 In the application&amp;#39;s BLE Stack event handler, I have found that there is a disconnect reason in the ble_evt_t parameter : p_ble_evt-&amp;gt;evt-&amp;gt;gap_evt-&amp;gt;params-&amp;gt;disconnected-&amp;gt;reason</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 28 Mar 2014 12:03:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/1992/how-to-determine-if-a-disconnection-is-due-to-a-bad-signal-signal-loss" /><item><title>RE: How to determine if a disconnection is due to a bad signal (signal loss)</title><link>https://devzone.nordicsemi.com/thread/8545?ContentTypeID=1</link><pubDate>Fri, 28 Mar 2014 12:03:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:407d0e80-af48-4654-b08c-21bef92f8452</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;You should never see values like this, so this sounds very strange. Could there be some issue with how you use this value? Could you share the code you&amp;#39;re working with?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to determine if a disconnection is due to a bad signal (signal loss)</title><link>https://devzone.nordicsemi.com/thread/8544?ContentTypeID=1</link><pubDate>Fri, 28 Mar 2014 08:59:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:876fda67-3214-4f9b-ab72-7269ddc6e413</guid><dc:creator>S&amp;#233;bastien Despont</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;Thank you for your answer.&lt;/p&gt;
&lt;p&gt;You are right, the reason is 0x08 when the device is out of range. But after some tries, the disconnected reason sometimes weird values like 0x90, 0x8F, 0x4E, ...&lt;/p&gt;
&lt;p&gt;As these values are not existing in the documentation, it is a bit unclear.
Do you have some explanation?&lt;/p&gt;
&lt;p&gt;FYI I am using SDK 5.2 and softdevice 110 6.0&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to determine if a disconnection is due to a bad signal (signal loss)</title><link>https://devzone.nordicsemi.com/thread/8543?ContentTypeID=1</link><pubDate>Thu, 27 Mar 2014 12:31:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2e5dc4c6-578f-409b-af14-cd931b1fbbbc</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Sebastien,&lt;/p&gt;
&lt;p&gt;In case of signal loss, (no connect event receives from master until timeout occurs) you will receive Disconnect event with reason = BLE_HCI_CONNECTION_TIMEOUT (0x08). You can find this in our linkloss service (ble_lls.c) example.&lt;/p&gt;
&lt;p&gt;You can test this by move the device out of range or power off (remove battery) the phone or unplug the dongle if you test with Master Control Panel.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>