<?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>BLE disconnect with 0x16 reason</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/26755/ble-disconnect-with-0x16-reason</link><description>Hi, 
 I have two nrf51822 device, on work as GAP Central, another work as GAP Peripheral.The two device use different connection parameters, after the connection is established, Peripheral device send BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST to the Central</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 10 Nov 2017 08:35:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/26755/ble-disconnect-with-0x16-reason" /><item><title>RE: BLE disconnect with 0x16 reason</title><link>https://devzone.nordicsemi.com/thread/105180?ContentTypeID=1</link><pubDate>Fri, 10 Nov 2017 08:35:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:42d0dd12-c955-4621-8976-297991664827</guid><dc:creator>Ian</dc:creator><description>&lt;p&gt;Yes, use &lt;code&gt;sd_ble_gap_conn_param_update(p_gap_evt-&amp;gt;conn_handle, NULL)&lt;/code&gt; can avoid peripheral disconnect the connection. Central must response BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST, if central ignore it, the peripheral will disconnect.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>