<?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>nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127143/nrf54l15-channel-sounding-abnormal</link><description>Device: nRF54L15 x 2, face to face 
 SDK: v3.2.2 
 Toolchain v 3.2.2 c717907b94 
 Sample code (with default setting): 
 channel_sounding_ras_reflector 
 channel_sounding_ras_initiator 
 
 
 Issue: 
 rtt is always 0 no matter how far between them 
 Both</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 02 Mar 2026 11:28:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127143/nrf54l15-channel-sounding-abnormal" /><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/562308?ContentTypeID=1</link><pubDate>Mon, 02 Mar 2026 11:28:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd15756d-8882-4fa2-803d-5100044c627f</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;He is using the same board. It is just a normal nRF54L15DK, and he is running the unmodified sample that you are looking at.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/562270?ContentTypeID=1</link><pubDate>Mon, 02 Mar 2026 01:41:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32390242-55ae-4d6b-ad68-78b8b8e8bea5</guid><dc:creator>JimmyChen</dc:creator><description>&lt;p&gt;However, in the video, your colleague Robin mentioned that he was using the &amp;#39;nRF54L15&amp;#39;. The development board shown in the video looks identical to the one I purchased, so I don&amp;#39;t believe he was using a different board. Could you please check with him how he managed to achieve such high-precision measurements of around 35 cm? &lt;br /&gt;Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/562114?ContentTypeID=1</link><pubDate>Thu, 26 Feb 2026 07:27:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:83e37731-4913-4487-9f79-b05df8584d83</guid><dc:creator>Edvin</dc:creator><description>[quote user="JimmyChen"]Could you please advise if these are the so-called &amp;quot;P&lt;span&gt;articular&amp;nbsp;&lt;/span&gt;DKs&amp;quot;? &lt;br /&gt;[/quote]
&lt;p&gt;There are no particular DKs. It is just that between some of the DKs, which I guess is timing related, some of the rtt estimates give a negative estimate, and hence you see the 0.00m.&lt;/p&gt;
[quote user="JimmyChen"]Additionally, rtt=0 is only one of the issues. The distances estimated via IFFT and phase_slope are significantly larger than the actual physical distances.[/quote]
&lt;p&gt;The accuracy of channel sounding is not that accurate. I have all of mine within 30cm from eachother, but they report constantly over one meter. That is just how (little) accurate distance measurement is.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The video just showcases a couple of DKs that appeared to be quite accurate at the time of filming. It is the same FW that you are using to test now.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/562104?ContentTypeID=1</link><pubDate>Thu, 26 Feb 2026 01:48:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9462b7e7-567b-4a13-9341-eeb8cdaca1f2</guid><dc:creator>JimmyChen</dc:creator><description>&lt;p&gt;Additionally, I purchased the devices featured in your colleague Robin&amp;#39;s video and set up my measurement environment exactly as he demonstrated.&lt;/p&gt;
&lt;p&gt;As shown in the video, he used a tape measure (tape borrowed from&amp;nbsp;my dad) and was able to achieve an accurate measurement of around 35 cm.&lt;/p&gt;
&lt;p&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;a class="ng-star-inserted" href="https://www.youtube.com/watch?v=dbQKqXN80ms" rel="noopener noreferrer" target="_blank" data-hveid="0" data-ved="0CAAQ_4QMahgKEwjim62R-_WSAxUAAAAAHQAAAAAQnwE"&gt;https://www.youtube.com/watch?v=dbQKqXN80ms&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Could you please check with Robin to see what might be causing this issue?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/562103?ContentTypeID=1</link><pubDate>Thu, 26 Feb 2026 01:22:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:83d68d16-9685-422a-aaeb-598c1bea0814</guid><dc:creator>JimmyChen</dc:creator><description>&lt;p&gt;I purchased these two boards from Mouser Electronics two weeks ago, and I do not have any other DKs.&lt;br /&gt;The labels on these two DKs are: PCA10156 1.0.0 2025.46 10577XXXXX.&lt;br /&gt;Could you please advise if these are the so-called &amp;quot;P&lt;span&gt;articular&amp;nbsp;&lt;/span&gt;DKs&amp;quot;? &lt;br /&gt;How can I purchase the &amp;quot;Regular&amp;quot; DKs?&lt;/p&gt;
&lt;p&gt;Note: The firmware on the boards has already been updated to the latest version via nRF Connect.&lt;/p&gt;
&lt;p&gt;Additionally, rtt=0 is only one of the issues. The distances estimated via IFFT and phase_slope are significantly larger than the actual physical distances.&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;
&lt;div id="gtx-trans" style="left:173px;position:absolute;top:63.4px;"&gt;
&lt;div class="gtx-trans-icon"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/562068?ContentTypeID=1</link><pubDate>Wed, 25 Feb 2026 14:28:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d032b032-06f4-4a9b-8f42-b9dfd773d9a4</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;So we found it. The reason it says 0 between some particular DKs is because the measurements gives a negative number (RTT is very inaccurate). There is a check in the calculations that checks whether the number is negative, and converts it to 0 if it is. If you want to see the numbers, even though it is negavive, you need to do two modifications in the cs_de.c&amp;#39;s function calculate_rtt_dist():&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;static void calculate_dist_rtt(cs_de_report_t *p_report)
{
	if (p_report-&amp;gt;rtt_count &amp;gt; 0) {
		float rtt_avg_measured_ns =
			(p_report-&amp;gt;rtt_accumulated_half_ns * 0.5f) / p_report-&amp;gt;rtt_count;
		float tof_ns = rtt_avg_measured_ns / 2.0f;
		//float rtt_distance_m = fmaxf(tof_ns * (SPEED_OF_LIGHT_M_PER_S / 1e9f), 0.0f);
		float rtt_distance_m = tof_ns * (SPEED_OF_LIGHT_M_PER_S / 1e9f);

		for (uint8_t ap = 0; ap &amp;lt; p_report-&amp;gt;n_ap; ap++) {
			//if (rtt_distance_m &amp;gt;= 0.0f) {
				p_report-&amp;gt;distance_estimates[ap].rtt = rtt_distance_m;
			//}
		}
	}
}&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;The changes I did was that I commented out line 7, 11, 13, and added line 8. Now it prints the numbers, which in my case is around -2.0m. This is within the expected accuracy of +-5.0m for rtt.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/562026?ContentTypeID=1</link><pubDate>Wed, 25 Feb 2026 11:46:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a33101ff-26b8-4b48-a9b3-4fe53dc45f54</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I just wanted to let you know that I am looking into your question, but I don&amp;#39;t yet have a conclusion.&lt;/p&gt;
&lt;p&gt;I have seen something similar before, but I thought it was an issue with an old DK, because it was only when I used a specific DK. However, when testing this application, it worked fine between my two DKs, but I tried a few others (all v1.0.0), and between two particular DKs, this issue occured. That means that if I have 3 DKs, A, B and C, I see the issue between B &amp;lt;=&amp;gt; C, but both A &amp;lt;=&amp;gt; B and A &amp;lt;=&amp;gt;C works fine.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Do you see the same? Do you have any more DKs to test with?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 channel sounding abnormal</title><link>https://devzone.nordicsemi.com/thread/561896?ContentTypeID=1</link><pubDate>Tue, 24 Feb 2026 02:05:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94a83ef1-1168-45b9-ab03-cdcb3584c202</guid><dc:creator>JimmyChen</dc:creator><description>&lt;p&gt;Note: devices distance is 15cm&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>