<?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>How to maximize Conn CTE packet rate on nRF5340?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126276/how-to-maximize-conn-cte-packet-rate-on-nrf5340</link><description>Dear Nordic Specialist, 
 I am using two nRF5340 DKs running the Direction Finding connection-based Central/Peripheral examples, and I would like to evaluate the maximum achievable CTE (DF) packet rate. 
 At first, I did not find any explicit parameter</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 21 Jan 2026 08:40:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126276/how-to-maximize-conn-cte-packet-rate-on-nrf5340" /><item><title>RE: How to maximize Conn CTE packet rate on nRF5340?</title><link>https://devzone.nordicsemi.com/thread/559226?ContentTypeID=1</link><pubDate>Wed, 21 Jan 2026 08:40:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb4e514c-55c2-49da-811a-0617c1987b61</guid><dc:creator>cheng</dc:creator><description>&lt;p&gt;Thanks! Now&amp;nbsp;I understand where its limitations come from.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to maximize Conn CTE packet rate on nRF5340?</title><link>https://devzone.nordicsemi.com/thread/559159?ContentTypeID=1</link><pubDate>Tue, 20 Jan 2026 13:02:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28da4433-a37c-49e4-97c8-0412f80d9fc5</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="cwdao"]Is this a limitation of the SDK, or a limitation of the BLE specification?[/quote]
&lt;p&gt;As is, the SoftDevice Controller responds with LL_CTE_RSP on the next connection event, not the current one. This has to do with implications for the complexity of the scheduler. According to the Bluetooth specification, the response to a link layer procedure can be sent in either the same or during a later connection event. Hence the delay is not a limitation of the specification, but implementation specific to the SoftDevice Controller. This does mean one connection event of latency compared to the maximum possible according to the specification, but it is at the same time well within the specifications.&lt;/p&gt;
&lt;p&gt;Further, also according to the Bluetooth specification, the CTE_Request_Interval parameter, which is what is set here for the device requesting CTE, is a suggestion (not a hard requirement). In the case of periodic operation (non-zero value), &amp;quot;the procedure is initiated every CTE_Request_Interval. However, the Controller may delay initiating the procedure beyond the requested interval (e.g., in order to prioritize other activities.)&amp;quot; Ref. Vol 4, Part E, 7.8.85 LE Connection CTE Request Enable command.&lt;/p&gt;
&lt;p&gt;From what I can tell the SoftDevice Controller implementation will send requests every connection event as requested (to the extent allowed by the Bluetooth specification with respect to overlapping procedures etc.) This means the SoftDevice Controller as a requester acts as quickly as permitted by the Bluetooth specification, and as a responder responds on the following connection event.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to maximize Conn CTE packet rate on nRF5340?</title><link>https://devzone.nordicsemi.com/thread/559029?ContentTypeID=1</link><pubDate>Mon, 19 Jan 2026 13:27:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d5eaa3b-ee46-45bf-b4be-97d547fea042</guid><dc:creator>cheng</dc:creator><description>&lt;p&gt;Hi tesc,&lt;/p&gt;
&lt;p&gt;No need to apologize&amp;mdash;no worries. This forum isn&amp;rsquo;t an instant-messaging tool.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m using Nordic&amp;rsquo;s sample:&lt;br /&gt; &lt;a href="https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/direction_finding_central"&gt;https://github.com/nrfconnect/sdk-nrf/tree/main/samples/bluetooth/direction_finding_central&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I use an nRF5340 as the central, and an nRF54L15 and nRF5340 as peripherals.&lt;/p&gt;
&lt;p&gt;In this program, the CTE interval is specified by &lt;code&gt;bt_df_conn_cte_req_params&lt;/code&gt;. The &lt;code&gt;interval&lt;/code&gt; field is described as: if set to 0, the CTE runs only once; if non-zero, it runs periodically with the configured interval. Therefore, the minimum value I can set is 1. From my observations, this means I receive one CTE packet every 1 connection interval.&lt;/p&gt;
&lt;p&gt;As far as I understand, connection-based CTE should be able to complete the request and the CTE response within a single connection interval. In other words, when I set the connection interval to 10 ms, I would like to receive one CTE every 10 ms; however, with the current configuration, I can only receive a CTE at best every 20 ms. Is this a limitation of the SDK, or a limitation of the BLE specification?&lt;/p&gt;
&lt;p&gt;Best,&lt;br /&gt; Cheng&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to maximize Conn CTE packet rate on nRF5340?</title><link>https://devzone.nordicsemi.com/thread/559005?ContentTypeID=1</link><pubDate>Mon, 19 Jan 2026 12:07:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:785632d5-ad45-4d87-a1e8-32f252b9550b</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am sorry for the delays. We are looking into your latest question about CTE happening every other connection interval. Which BLE controller are you using, the SoftDevice Controller or the Zephyr controller?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to maximize Conn CTE packet rate on nRF5340?</title><link>https://devzone.nordicsemi.com/thread/557772?ContentTypeID=1</link><pubDate>Wed, 31 Dec 2025 10:41:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7512c7fe-c10f-4486-b9c7-a485c0d1942f</guid><dc:creator>cheng</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;Thanks you! I tried this parameter and it worked. I really appreciate it!&lt;br /&gt;&lt;br /&gt; I have one more question about the CTE update frequency. I noticed that when I set the BLE connection interval to 50 ms, I don&amp;rsquo;t receive a CTE extension packet every 50 ms. Instead, it looks like the SDK requests a CTE in one connection event, and the peripheral sends the CTE in the next event.&lt;br /&gt;&lt;br /&gt; Is it possible to configure it so that the CTE request and the CTE transmission happen within the same connection event each time? If so, then with a 50 ms interval the central should be able to receive a CTE every 50 ms.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to maximize Conn CTE packet rate on nRF5340?</title><link>https://devzone.nordicsemi.com/thread/557683?ContentTypeID=1</link><pubDate>Mon, 29 Dec 2025 13:55:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a70ec964-3dcb-4981-be8a-8ad87fe9408d</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Try to disable&amp;nbsp;&lt;span&gt;CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>