<?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>Connection Interval &amp;#39;s relationship with Data rate and power consumption</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/121579/connection-interval-s-relationship-with-data-rate-and-power-consumption</link><description>Hi 
 I noticed one ticket says that &amp;quot;the following combination offers low power consumtion and high througput when needed :Short Connection Interval + High Slave Latency + Long supervision timeout &amp;quot; 
 I try to study this in two nRF54L15 DKs, I will change</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 20 May 2025 06:58:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/121579/connection-interval-s-relationship-with-data-rate-and-power-consumption" /><item><title>RE: Connection Interval 's relationship with Data rate and power consumption</title><link>https://devzone.nordicsemi.com/thread/536092?ContentTypeID=1</link><pubDate>Tue, 20 May 2025 06:58:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:14ff5805-4c1c-4995-b16a-d788877d5744</guid><dc:creator>Ziyao Zhou</dc:creator><description>&lt;p&gt;Thank you for your information&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection Interval 's relationship with Data rate and power consumption</title><link>https://devzone.nordicsemi.com/thread/535991?ContentTypeID=1</link><pubDate>Mon, 19 May 2025 12:39:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:88f064ac-8dcf-4152-90eb-3b6eb26d6687</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;In a realistic end product use case it&amp;#39;s very likely some kind of interference (e.g. other BLE, classic BT, Wifi, and other 2.4GHz protocol or interference sources (e.g. microwave oven or USB3.0 ports). All these source may cause packet loss, and in BLE if any error is found in the packet, it will wait until next connection interval before retransmitting and continue sending packets. This means that packet loss will have a high impact on the throughput if you use long connection interval, that is why I always recommend having the lowest possible connection interval, because even though under ideal conditions longer connection interval may seem better, in realistic scenarios the short interval will have better stable results.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection Interval 's relationship with Data rate and power consumption</title><link>https://devzone.nordicsemi.com/thread/535875?ContentTypeID=1</link><pubDate>Sun, 18 May 2025 12:22:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d1ff3f4e-2ba2-4fd6-afff-68f452b97f21</guid><dc:creator>Ziyao Zhou</dc:creator><description>&lt;p&gt;Thank you for your information! Yes, I am using BLE to do video transfer. So that if I use low throughput appliacation the interval will have difference?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection Interval 's relationship with Data rate and power consumption</title><link>https://devzone.nordicsemi.com/thread/535871?ContentTypeID=1</link><pubDate>Sun, 18 May 2025 09:40:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c20c6887-d64c-4c1b-bae8-67b95b51a998</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Careful: BTLE is not intended for high data rates.&lt;/p&gt;
&lt;p&gt;Your throughput is only achievable with close to 100% radio on-time, thus you will see basically the same current consumtion over a large parameter range.&lt;/p&gt;
&lt;p&gt;Does your application really need those rates? Then BTLE may not be the best choice.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>