<?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 long does it take for the new negotiated connection interval to get applied?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/99786/how-long-does-it-take-for-the-new-negotiated-connection-interval-to-get-applied</link><description>Hello, 
 I am using nrf52832 as a peripheral and running SD S112, nordic UART Profile and SDK 17.1.0 on it. 
 I am requesting the update connection parameter between 60ms to 105ms. I see that the central has accepted the request and has also sent the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 30 May 2023 08:12:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/99786/how-long-does-it-take-for-the-new-negotiated-connection-interval-to-get-applied" /><item><title>RE: How long does it take for the new negotiated connection interval to get applied?</title><link>https://devzone.nordicsemi.com/thread/428073?ContentTypeID=1</link><pubDate>Tue, 30 May 2023 08:12:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a5a5ee2-9091-41f2-9925-399980d24e33</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The SoftDevice will generate the event&amp;nbsp;BLE_GAP_EVT_CONN_PARAM_UPDATE, and the connection param module will give you the event&amp;nbsp;BLE_CONN_PARAMS_EVT_SUCCEEDED when this happens.&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Also see this MSC,&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.2.0/group___b_l_e___g_a_p___c_p_u___m_s_c.html"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.2.0/group___b_l_e___g_a_p___c_p_u___m_s_c.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How long does it take for the new negotiated connection interval to get applied?</title><link>https://devzone.nordicsemi.com/thread/425996?ContentTypeID=1</link><pubDate>Tue, 16 May 2023 19:59:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e92136bd-8c93-47a5-aa96-202c68ed2591</guid><dc:creator>Justin</dc:creator><description>&lt;p&gt;Thank you&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/members/sigurdon"&gt;Sigurd&lt;/a&gt;&amp;nbsp; for the answer. This is really super helpful.&lt;/p&gt;
&lt;p&gt;Is there a way by which on peripheral side we can know that the&amp;nbsp; central has accepted the parameter update request?&lt;/p&gt;
&lt;p&gt;For e.g. any callback event ? I know on_conn_params_evt() that is registered in cp_init.evt_handler.&lt;/p&gt;
&lt;p&gt;Will this set event after the LLCP connection update Indication or right after when connection interval change is requested?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How long does it take for the new negotiated connection interval to get applied?</title><link>https://devzone.nordicsemi.com/thread/425856?ContentTypeID=1</link><pubDate>Tue, 16 May 2023 12:36:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a6f4bf1-99dd-4665-9079-47a50aebce84</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This is determined by the master.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1684240410944v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;In the LL_CONNECTION_UPDATE_IND packet the new connection parameters&amp;nbsp;is&amp;nbsp;set to be applied at connection event 371. The&amp;nbsp;&lt;span&gt;LL_CONNECTION_UPDATE_IND packet was sent at connection event 362. &lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Current CI ~1second * (371-362)= 9 seconds before it takes affect.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>