<?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>nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27113/nrf52840-coded-phy-sensitivity</link><description>Hi, 
 I get RSSI values like -96 or -97 dBm before the coded PHY connection between two nRF52840 pdks drops. Are these values something expected? TI advertises sensitivity of -103 dBm in their youtube video of CC2640R2F. Are they slightly ahead or do</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 04 Dec 2017 15:28:34 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27113/nrf52840-coded-phy-sensitivity" /><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106681?ContentTypeID=1</link><pubDate>Mon, 04 Dec 2017 15:28:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:678934d8-9be9-4a81-a9ed-7bef06cf2c95</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi Christian,&lt;/p&gt;
&lt;p&gt;Please create a new question here on DevZone regarding this issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106680?ContentTypeID=1</link><pubDate>Thu, 30 Nov 2017 14:37:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:092b4624-9417-4dfc-b8c4-a3abd88e69c8</guid><dc:creator>Christian</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Is there anything else that needs to be considered apart from the soft device version? I used soft device 6.0.0-6.alpha and modified the att_mtu_throughput example to print the RSSI when changed, but connection between two nrf52840 boards is still lost at around -97 dbm.&lt;/p&gt;
&lt;p&gt;Thanks in Advance&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106675?ContentTypeID=1</link><pubDate>Fri, 06 Oct 2017 14:00:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb958970-dfc9-42d3-bc36-d2d241d8c343</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;The new S140 SoftDevice is now released and can be downloaded from here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.nordicsemi.com/eng/nordic/Products/nRF52840/S140-SD-v5/60624"&gt;www.nordicsemi.com/.../60624&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This version have fixed the BLE 5 Long Range issues that was present in the previous versions. From the S140 6.0.0-6.alpha release notes:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The SoftDevice now implements a range
delay (packet time of flight
compensation) corresponding to a
distance of 5 km when using LE Coded
PHY&lt;/p&gt;
&lt;/blockquote&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106674?ContentTypeID=1</link><pubDate>Thu, 28 Sep 2017 12:49:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:491b667f-1a2d-4cf6-b07c-7a76ead3e564</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;The new S140 SoftDevice version with the full fix is right around the corner... please give it some more time. I will update this post when it&amp;#39;s released.  Sorry for the inconvenience.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106673?ContentTypeID=1</link><pubDate>Thu, 28 Sep 2017 10:26:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f6ba0c2e-9965-44ce-a217-973858f4a17b</guid><dc:creator>slowhand</dc:creator><description>&lt;p&gt;I have not noticed updates yet. I am also still interested...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106672?ContentTypeID=1</link><pubDate>Thu, 28 Sep 2017 10:23:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53053ac6-f716-4f89-9cb0-02fe2c5c3a56</guid><dc:creator>Andrzej Kaczmarek</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Any update on this? My project does not use SoftDevice so if it&amp;#39;s possible to have some magic values (as in errata 164) to test with, would be great.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106670?ContentTypeID=1</link><pubDate>Mon, 07 Aug 2017 11:42:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8a1b5f5-0089-46eb-89da-d2df89c6de18</guid><dc:creator>slowhand</dc:creator><description>&lt;p&gt;Ok, thanks for the update. We shall wait!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106669?ContentTypeID=1</link><pubDate>Mon, 07 Aug 2017 11:38:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:93bfa3d8-69f2-4380-9d95-e38bf06dcfd2</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It seems that some additional workaround is needed to get the full sensitivity in long range mode. I.e. the workaround in &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.EngA.errata/anomaly_840_164.html?cp=2_0_1_0_1_48"&gt;Errata 164&lt;/a&gt; is not sufficient to get the -103 dBm sensitivity (and will &lt;strong&gt;not&lt;/strong&gt; give you better range). Final workaround and new version of the SoftDevice will be released when the final verification and testing is complete. Note that the current S140 SoftDevice version is still in alpha version. Sorry for the inconvenience.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106671?ContentTypeID=1</link><pubDate>Thu, 03 Aug 2017 08:10:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7daf01ae-67ca-4707-809c-9725e0d7debc</guid><dc:creator>slowhand</dc:creator><description>&lt;p&gt;Sorry, I noticed your comment late. I just came back to this and added the two suggested lines before ble_stack_init. The last RSSI value in my field test a moment ago was -95dBm. Not sure if I just added the lines to correct place. I used the long range multilink central and blinky peripheral example.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106679?ContentTypeID=1</link><pubDate>Mon, 17 Jul 2017 18:10:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a4a4a5cd-9bc3-480b-b81a-323560018efd</guid><dc:creator>KV</dc:creator><description>&lt;p&gt;If I have to add this workaround to the ATT throughput demo, what would be the best place to add this workaround? I was thinking of adding this to &amp;quot;preferred_phy_set&amp;quot; function. I assume, advertising_start and scan_start function would turn on the radio.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106678?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2017 09:06:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b63e8ab9-34ac-4548-b016-ccdf036c8367</guid><dc:creator>slowhand</dc:creator><description>&lt;p&gt;Good, thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106677?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2017 08:49:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29137eed-62b9-41f6-865f-053a51dda69a</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;I would hope maybe in 1-2 weeks (release in end of July).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106676?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2017 08:22:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c87d525a-6f9e-4ce8-a3f9-240be34457c0</guid><dc:creator>slowhand</dc:creator><description>&lt;p&gt;Ok, thanks! Do you want to give any guess on the 4.-alpha release timing?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 coded phy sensitivity</title><link>https://devzone.nordicsemi.com/thread/106668?ContentTypeID=1</link><pubDate>Fri, 14 Jul 2017 08:18:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eaf57d3c-03d0-4e81-81c1-617e5e8e14c1</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The nRF52840 have &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.ps/radio.html?cp=2_0_0_21_14_4#unique_953413568"&gt;-103 dBm Sensitivity&lt;/a&gt; in coded PHY(125kbps BLE mode). The reason why the connection drops at -96 / -97 dBm is a bug in the current alpha versions of the S140 SoftDevice. Errata with workaround for this bug can be found here: &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52840.EngA.errata/anomaly_840_164.html?cp=2_0_1_0_1_48"&gt;RADIO: Low sensitivity in long range mode&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Fix will be included in the upcoming S140 5.0.0-4.alpha release.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>