<?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>About RSSI of BLE</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/228/about-rssi-of-ble</link><description>Hi, I am trying to get the rssi value of a connection, and what I am trying to do is to start the rssi in the beginning at the connection and end it at the end of connection. So in my on_ble_evt of my app I have: 
 case BLE_GAP_EVT_CONNECTED:
 nrf_gpio_pin_set</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 Jun 2014 15:55:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/228/about-rssi-of-ble" /><item><title>RE: About RSSI of BLE</title><link>https://devzone.nordicsemi.com/thread/1270?ContentTypeID=1</link><pubDate>Mon, 02 Jun 2014 15:55:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:348f8b80-c069-4b75-9d82-ed20751d6c2c</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;This issue was fixed in version 6.0.0 of the S110 SoftDevice.&lt;/p&gt;
&lt;p&gt;Here&amp;#39;s a quote from the release notes:
Fixed an issue where calling sd_ble_gap_rssi_stop() after connection had ended would cause an assert. In addition, RSSI will now be stopped automatically when the connection ends (NRFFOETT-499, DRGN-3131).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About RSSI of BLE</title><link>https://devzone.nordicsemi.com/thread/1269?ContentTypeID=1</link><pubDate>Mon, 05 Aug 2013 12:45:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff5dec1c-80db-4dcf-a72d-d18fce14a85d</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We have recently come across this bug, where the RSSI stop function does give back an error code.
The connection handle is actually invalid once the &amp;quot;BLE_GAP_EVT_DISCONNECTED&amp;quot; is called, so this is why you are seeing an assert at this point.
The bug from Nordic&amp;#39;s side is that the RSSI is not stopped properly after a disconnect occurs.&lt;/p&gt;
&lt;p&gt;You can work around this by:
call function &amp;quot;(void)sd_ble_gap_rssi_stop(m_conn_handle);&amp;quot; before starting RSSI in BLE_GAP_EVT_CONNECTED.&lt;/p&gt;
&lt;p&gt;Another way is to use a variable to stop the RSSI, as the attached .c file shows.&lt;/p&gt;
&lt;p&gt;You should then not call sd_ble_gap_rssi_stop in the &amp;quot;BLE_GAP_EVT_DISCONNECTED&amp;quot; event.&lt;/p&gt;
&lt;p&gt;Best regards
Håkon&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/sd_5F00_rssi_5F00_wrkaround.c"&gt;sd_rssi_wrkaround.c&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>