<?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>inactivity timeout</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13117/inactivity-timeout</link><description>I use a nrf51822 with the sdk 10.0.0 and s110 8.0.0. The nrf51822 have a peripheral role. The Connection interval min is set to 500ms, the Connection interval max to 1s, the slave latency to 0 and the connection supervisory timeout to 4s. The connexion</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Apr 2016 13:58:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13117/inactivity-timeout" /><item><title>RE: inactivity timeout</title><link>https://devzone.nordicsemi.com/thread/50014?ContentTypeID=1</link><pubDate>Tue, 12 Apr 2016 13:58:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:19f35b1a-12ff-49b6-8238-4b55e704931e</guid><dc:creator>John</dc:creator><description>&lt;p&gt;You are welcome. Please mark the answer as accepted if you don&amp;#39;t mind.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: inactivity timeout</title><link>https://devzone.nordicsemi.com/thread/50015?ContentTypeID=1</link><pubDate>Tue, 12 Apr 2016 13:52:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:73240ad2-b610-4cd1-ba57-a7f28c8b9981</guid><dc:creator>jp</dc:creator><description>&lt;p&gt;Thanks you very much John for your answer. It was very helpful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: inactivity timeout</title><link>https://devzone.nordicsemi.com/thread/50016?ContentTypeID=1</link><pubDate>Tue, 12 Apr 2016 07:23:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbf1c975-d948-4512-be7d-962252191561</guid><dc:creator>jp</dc:creator><description>&lt;p&gt;Yes it&amp;#39;s inactivity of messaging between the central and peripheral.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: inactivity timeout</title><link>https://devzone.nordicsemi.com/thread/50013?ContentTypeID=1</link><pubDate>Mon, 11 Apr 2016 20:05:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:23fa3af6-62e9-4fe3-91f0-c9497ae55ccd</guid><dc:creator>John</dc:creator><description>&lt;p&gt;Is the inactivity you mention inactivity of your messaging between the central and peripheral, or are you referring to 4 seconds of no connection events?&lt;/p&gt;
&lt;p&gt;Update: OK, the BLE protocol keeps the connection up using connect events. As long as those are flowing, the connection will not time out. What I did in my application was to create an app timer to timeout my activity on the connection. If I do not get a message from my central application in X seconds I then execute the following call:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sd_ble_gap_disconnect(appBleData.connHandle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This will break the connection.&lt;/p&gt;
&lt;p&gt;I restart the timer every time I receive one of my proprietary commands.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>