<?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>Default coded PHY (S=2 vs S=8) on nRF52833 for advertising and connections under ncs 3.1.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124213/default-coded-phy-s-2-vs-s-8-on-nrf52833-for-advertising-and-connections-under-ncs-3-1-0</link><description>Hi, 
 
 I am working with an nRF52833 using the SoftDevice Controller in nRF Connect SDK 3.1.0, and I have a question about LE Coded PHY (long range). 
 
 I understand that the device supports coded PHY, but I found conflicting information regarding whether</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 08 Sep 2025 14:00:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124213/default-coded-phy-s-2-vs-s-8-on-nrf52833-for-advertising-and-connections-under-ncs-3-1-0" /><item><title>RE: Default coded PHY (S=2 vs S=8) on nRF52833 for advertising and connections under ncs 3.1.0</title><link>https://devzone.nordicsemi.com/thread/548083?ContentTypeID=1</link><pubDate>Mon, 08 Sep 2025 14:00:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0cb1800-48d6-4872-8100-c109a56651f0</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You are correct. I was not clear, but what I wanted to say was that you gain very little range using S=2 compared to using the normal 1 Mbps PHY. You get the downside of reduced bitrate and increased power consupmtion per transfered unit of information, but not a significant gain in range. So in practice, the choise whoudl be between 1 (or 2) Mbps PHY and S=8 Coded PHY.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Default coded PHY (S=2 vs S=8) on nRF52833 for advertising and connections under ncs 3.1.0</title><link>https://devzone.nordicsemi.com/thread/548077?ContentTypeID=1</link><pubDate>Mon, 08 Sep 2025 13:45:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a25af23f-247c-437a-8062-7852fe4500c8</guid><dc:creator>longo92</dc:creator><description>&lt;p data-start="101" data-end="137"&gt;Thank you for the detailed answer.&lt;/p&gt;
&lt;p data-start="139" data-end="512"&gt;I have one point I&amp;rsquo;d like to clarify: you mentioned &lt;em data-start="191" data-end="275"&gt;&amp;ldquo;however, you gain very little range using S=2, so this has little practical use.&amp;rdquo;&lt;/em&gt;&lt;br data-start="275" data-end="278" /&gt; From my understanding, when using S=2 there is a gain in bitrate but a reduction in maximum distance compared to S=8. Moreover, from a power consumption perspective, S=2 should consume less since the transmission time is shorter. Am I correct?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Default coded PHY (S=2 vs S=8) on nRF52833 for advertising and connections under ncs 3.1.0</title><link>https://devzone.nordicsemi.com/thread/548072?ContentTypeID=1</link><pubDate>Mon, 08 Sep 2025 13:34:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0fa5664e-412d-4183-bbb4-824f092a7d1d</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user=""]1. When I enable coded PHY advertising on the nRF52833, which coding (S=2 or S=8) is used by default?[/quote]
&lt;p&gt;Using coded PHY, S=8 is the defaut.&lt;/p&gt;
[quote user=""]&lt;p&gt;2. When establishing a connection on coded PHY, which coding is negotiated by default?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;[/quote]
&lt;p&gt;There is no negotiation on this part. All devices supporting coded phy need to suppor both, and the header is always transmited as S=8, and this tells if the rest of the packet is S=8 or S=2 encoded.&lt;/p&gt;
[quote user=""]3. Is it possible to explicitly request S=2 on the nRF52833, or is only S=8 supported?[/quote]
&lt;p&gt;for recent nRF Connect SDK versions, both S=8 and S=2 are supported. You can specify S=2 using the&amp;nbsp;&lt;code&gt;BT_CONN_LE_PHY_OPT_CODED_S2&lt;/code&gt; option. For a sample, please take a look at &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/121687/is-it-possible-to-use-coded-s-2-with-nrf5340-dk-and-nrf52840-dongle-in-zephyr-ncs/536512"&gt;this post&lt;/a&gt;. However, you gain very little range using S=2, so this has little practical use.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>