<?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>I want to know the validity of RSSI in Peripheral.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/102930/i-want-to-know-the-validity-of-rssi-in-peripheral</link><description>hi 
 I am trying to adjust the TX power after acquiring RSSI while connecting to the central in Peripheral. 
 
 ex) RSSI &amp;lt; -40dBm -&amp;gt; TX Power 4dBm 
 RSSI &amp;lt; -20dBm -&amp;gt; TX Power 0dBm 
 
 
 First of all, RSSI gets data through BLE_GAP_EVT_SCAN_REQ_REPORT</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 18 Aug 2023 00:03:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/102930/i-want-to-know-the-validity-of-rssi-in-peripheral" /><item><title>RE: I want to know the validity of RSSI in Peripheral.</title><link>https://devzone.nordicsemi.com/thread/441975?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2023 00:03:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d2bcf2e-563f-4a0d-9de8-19d2fdc578d8</guid><dc:creator>SHMoon</dc:creator><description>&lt;p&gt;hi&amp;nbsp;Einar Thorsrud&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Being able to check every time the RSSI changes is a really nice feature.&lt;/p&gt;
&lt;p&gt;Thank you very much for recommending a great feature that I hadn&amp;#39;t thought of.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I want to know the validity of RSSI in Peripheral.</title><link>https://devzone.nordicsemi.com/thread/441840?ContentTypeID=1</link><pubDate>Thu, 17 Aug 2023 11:38:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5cc609e5-9464-48ee-aa35-81ede85c5e02</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]The question is, is it correct to set the rssi obtained from BLE_GAP_EVT_SCAN_REQ_REPORT as a standard in BLE_GAP_EVT_CONNECTED?[/quote]
&lt;p&gt;Both these samples are equally valid (as long as they are from the same device). But it would probably also make sense to monitor the RSSI while in a connection (see &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/45707/finding-rssi-value-after-connection-continously/179991"&gt;this post&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;I see some problems with this approach though. The RSSI you measure is determined by the environment (attenuation, reflections, path loss, etc). However, it is also dependent on the Tx power of the peer. So, ff you don&amp;#39;t control the peer, it could be that it sends with a higher or lower Tx power than you do, so the RSSI at your end may not be a good indication of the RSSI at the peer, which is what you can control by adjusting the Tx power. Therefor, I would not make such an approach too fine tuned, but perhaps separate on &amp;quot;close&amp;quot; and &amp;quot;far away&amp;quot;, and use (say) -4 dBm and +4 dBm or whatever fits the use case best, but don&amp;#39;t fine-tune more than that as there are so many unknowns you don&amp;#39;t have control over.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>