How should RSSI be interpreted in the Sniffer APIhttps://devzone.nordicsemi.com/f/nordic-q-a/57149/how-should-rssi-be-interpreted-in-the-sniffer-apiHello all, I have a pretty simple question that I hope can be answered for me. I&#39;m integrating an nrf52832 development kit (PCA10040) BLE sniffer into a test fixture to be used for automated testing of boards we will be producing. All that it needsen-USTelligent Community 13Thu, 30 Jan 2020 15:21:21 GMTRE: How should RSSI be interpreted in the Sniffer APIhttps://devzone.nordicsemi.com/thread/231949?ContentTypeID=1Thu, 30 Jan 2020 15:21:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7178ecbe-7f54-4feb-b61a-3cafc2dccb0aDon Weier<p>Thanks Einar!</p><div style="clear:both;"></div>RE: How should RSSI be interpreted in the Sniffer APIhttps://devzone.nordicsemi.com/thread/231804?ContentTypeID=1Thu, 30 Jan 2020 08:54:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fcaeb596-df99-4315-91e3-5be519ea8bf8Einar Thorsrud<p>Hi,</p> <p>The radio will give you the RSSI in dBm as an unsigned integer (see <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/radio.html?cp=4_2_0_22_13_23#register.RSSISAMPLE">RSSISAMPLE</a>), and this is what you get from the sniffer FW. So you just need to treat it as a negative number (as you assumed).</p> <p>(This is different when you use the SoftDevice API, which the sniffer FW does not use, since then the RSSI sample you get is already a signed integer. See <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.0.0/structble__gap__evt__scan__req__report__t.html">ble_gap_evt_scan_req_report_t::rssi</a>).</p><div style="clear:both;"></div>