<?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>Timing of retransmissions</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126488/timing-of-retransmissions</link><description>Hi there, 
 We are currently developing a system, where around 480 kbytes of data are transmitted over BLE. Throughput is supposed to be as high as possible. 
 We are using Notifications, DLE enabled, 2M PHY and an ATT MTU of 247 Bytes. 
 The ATT Payload</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Jan 2026 13:43:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126488/timing-of-retransmissions" /><item><title>RE: Timing of retransmissions</title><link>https://devzone.nordicsemi.com/thread/558590?ContentTypeID=1</link><pubDate>Tue, 13 Jan 2026 13:43:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:037019fa-fbbc-4afe-9a4b-c90df2ab570a</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You can look into the &lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/throughput/README.html"&gt;throughput sample&lt;/a&gt;&amp;nbsp;found in NCS\nrf\samples\bluetooth\throughput, and use this on 2 DKs to play with the connection parameters. You have already picked up most of it. The idea is that you increase the MTU to 247, use 2MBPS PHY, and enable DLE. The question is the connection interval. Shorter connection intervals give shorter packets, while longer connection intervals give longer packets. In general longer packets means a lower header/payload throughput, which is good for throughput.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;But streching the connection interval too long is not good either, because it means that if a packet is lost (the receiver gets a bit flipped resulting in a wrong CRC), then the devices needs to wait for the beginning of the next connection interval to retransmit that packet, before it can continue transmitting. I would say that you should experiment with connection intervals of 50, 100 and 200ms in an environment that is close to what the environment where your devices will operate, to see what gives you the ideal throughput.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;A connection interval of 7.5ms is too short. It gives a too high header/payload throughput ratio. Check out the throughput sample (and try with 7.5ms as well, to verify). You can also see, if you experiment with the &lt;a href="https://devzone.nordicsemi.com/power/w/opp/2/online-power-profiler-for-bluetooth-le"&gt;online power profiler&lt;/a&gt;, that setting the connection interval = 7.5ms, and setting a high data throughput will use more than 7.5ms per connection interval:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1768311609523v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I believe the optimal connection interval is roughly 100-150ms, where you should see (in a quiet environment) you should see a throughput close to the theoretical maximum, somewhere between 1.3 and 1.4 Mbps.&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></channel></rss>