<?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>Connection parameters are slow to update</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47559/connection-parameters-are-slow-to-update</link><description>Hi, 
 I&amp;#39;m currently trying to implement a switch between slow and fast connection parameters. For a certain amount of time during a connection the link between peripheral (nRF52832) and central (Android phone) needs to speed up. Therefor when the peripheral</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 May 2019 11:55:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47559/connection-parameters-are-slow-to-update" /><item><title>RE: Connection parameters are slow to update</title><link>https://devzone.nordicsemi.com/thread/188236?ContentTypeID=1</link><pubDate>Tue, 21 May 2019 11:55:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c156b0b9-fc86-4d85-b7ad-b3b8843c53c9</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Sounds that you have already identified the problem.&lt;/p&gt;
&lt;p&gt;One suggestion is that the peripheral can just send some dummy notifications very frequently after receiving the &amp;quot;start packet&amp;quot;, then it will at the same time &amp;quot;fetch&amp;quot; whatever the central may want to send at every interval (though this will not solve the math behind the slow update of connection interval).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection parameters are slow to update</title><link>https://devzone.nordicsemi.com/thread/188144?ContentTypeID=1</link><pubDate>Tue, 21 May 2019 08:32:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db29f8da-6626-452e-802b-d89a36c63c71</guid><dc:creator>AntonHellbe</dc:creator><description>&lt;p&gt;I found this in the Bluetooth 5.0 Core spec:&lt;/p&gt;
&lt;p&gt;The master should allow a minimum of 6 connection events that the slave will&lt;br /&gt;be listening for before the instant occurs, considering that the slave may only&lt;br /&gt;be listening once every connSlaveLatency events.&lt;/p&gt;
&lt;p&gt;So I&amp;#39;m assuming this explains the 16s delay since when we are in slow mode the connection interval is set to min: 1.5s max: 2s, slave latency: 0. 6 connection events = ~12 seconds.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>