<?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>Channel Sounding ranging accuracy and stability</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/129039/channel-sounding-ranging-accuracy-and-stability</link><description>Hi, 
 I have been testing Channel Sounding precision and am experiencing difficulty achieving stable ranging results. Regardless of the configuration changes I make, the ranging measurements remain highly susceptible to interference, and the accuracy</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 Aug 2026 14:06:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/129039/channel-sounding-ranging-accuracy-and-stability" /><item><title>RE: Channel Sounding ranging accuracy and stability</title><link>https://devzone.nordicsemi.com/thread/570637?ContentTypeID=1</link><pubDate>Wed, 26 Aug 2026 14:06:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b938691-c51d-4a00-ae06-941855a06305</guid><dc:creator>Elfving</dc:creator><description>&lt;p&gt;Hi Nikola,&lt;/p&gt;
[quote user=""]Regardless of the configuration changes I make, the ranging measurements remain highly susceptible to interference, and the accuracy is rarely better than 0.5 m.[/quote]
&lt;p&gt;What is important to remember here is that channel sounding won&amp;#39;t get you anything as accurate as eg. UWB. My understanding is that the theoretical best case scenario is a result within half a meter.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;With that said, an additional limitation here is that you are to a large degree reliant on using a good algorithm to get the distances from &lt;a href="https://en.wikipedia.org/wiki/In-phase_and_quadrature_components"&gt;the raw IQ values&lt;/a&gt; etc. What we mainly provide is the back-end BLE compliant solution to get these values, not the distances. There are multiple impressive ways to get the distances from these I/Q values. A third party algorithm provider might get you some of these.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We do have an algorithm in the SDK as well that is being used in the samples you mention, we used to say in the documentation that we would recommend exchanging this for something better, though with some new changes to the algos I guess we&amp;#39;ve removed this recommendation. Though if you find that the accuracy that you get is not to your liking, aquiring a third party algorithm, or improving it yourself is something I would recommend. When it comes to how to do this though, I am not sure what to say, as this is a different technical field in a way.&amp;nbsp;There is not &lt;strong&gt;a main way&lt;/strong&gt; to go about doing this, not atleast to my knowledge.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Elfving&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>