<?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>Who set initial connection parameters on BLE?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/4772/who-set-initial-connection-parameters-on-ble</link><description>Hello!
I&amp;#39;ve some doubt about set-up of initial parameters in a BLE connection, using S110. 
 In ble_app_lbs I try to change the following macro definitions:
MIN_CONN_INTERVAL=500ms, 
MAX_CONN_INTERVAL=500ms,
SLAVE_LATENCY=7,
CONN_SUP_TIMEOUT=4000ms</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Dec 2014 15:44:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/4772/who-set-initial-connection-parameters-on-ble" /><item><title>RE: Who set initial connection parameters on BLE?</title><link>https://devzone.nordicsemi.com/thread/16882?ContentTypeID=1</link><pubDate>Tue, 09 Dec 2014 15:44:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c0a4922e-00b8-4cda-8aa4-2660d48ca9a7</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;The central decides the connection parameters I&amp;#39;m afraid. The PPCP values set by sd_ble_gap_ppcp_set() updates some values in the GATT database that can later be read out by the central device &lt;em&gt;after&lt;/em&gt; connecting. Even in connection parameter update (not to be confused with the new 4.1 feature) the peripheral only sends a request, and it is up to the central to decide what the parameters should update to.&lt;/p&gt;
&lt;p&gt;But - it is possible to put the connection interval in your advertisement data, see Core Spec Supplement v4 - Chapter 1.9. It will still be up to the central devices to actually use the advertised intervals, but you could save yourself a connection parameter update if it does. The &amp;quot;Slave connection interval range&amp;quot; will take 4 octets + flag + length, so 6 octets in total.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>