<?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 use the default connection paramater as set by the central?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/17290/how-to-use-the-default-connection-paramater-as-set-by-the-central</link><description>I&amp;#39;m using the nRF52 + SDK11.0.0 + s132 and the ble_hrs example. The function conn_params_init() is called to initialize the connection parameters that the peripheral will request, but where is the actual call to request the new connection parameter made</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 25 Oct 2016 16:12:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/17290/how-to-use-the-default-connection-paramater-as-set-by-the-central" /><item><title>RE: How to use the default connection paramater as set by the central?</title><link>https://devzone.nordicsemi.com/thread/66440?ContentTypeID=1</link><pubDate>Tue, 25 Oct 2016 16:12:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:634a3345-d17f-4be8-9d4a-0a56b6426ed4</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;The functions implementing the connection parameters negotiation can be found in &lt;code&gt;ble_conn_params.c&lt;/code&gt;. The initial connection parameters are set by the central on connection. The function &lt;code&gt;on_connect()&lt;/code&gt; is called, and the initial connection parameters are saved in &lt;code&gt;m_current_conn_params&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The parameter negotiation is done in the function &lt;code&gt;conn_params_negotiation()&lt;/code&gt;, where the function &lt;code&gt;is_conn_params_ok()&lt;/code&gt; is used to check if the connection parameters received from the central are acceptable.&lt;/p&gt;
&lt;p&gt;If the initial received parameters are not acceptable, a timer called &lt;code&gt;m_conn_params_timer_id&lt;/code&gt; is started. When the timer expires after &lt;code&gt;FIRST_CONN_PARAMS_UPDATE_DELAY&lt;/code&gt;, and the peripheral still haven&amp;#39;t received any acceptable connection parameters from the central, it will send a &lt;strong&gt;connection parameters update request&lt;/strong&gt; to the central, with the preferred connection parameters.  This is done by calling the function &lt;code&gt;sd_ble_gap_conn_param_update()&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;So if you want to always accept the connection parameters from the central, I suggest you in &lt;code&gt;main.c&lt;/code&gt; set &lt;code&gt;MIN_CONN_INTERVAL&lt;/code&gt; to 7.5 ms and &lt;code&gt;MAX_CONN_INTERVAL&lt;/code&gt; to 4 s. This is the minium and maximum connection interval supported by the SoftDevice. Another solution could be to change &lt;code&gt;is_conn_params_ok()&lt;/code&gt; to always return true.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>