<?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>Can I achieve 160Kbps through BLE4.2?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25841/can-i-achieve-160kbps-through-ble4-2</link><description>Hello, 
 I was wondering whether or not it&amp;#39;s possible to achieve a data rate of 160Kbps using BLE4.2. According to what I have read on this nordic blog it should be feasable, since there the maximum throughput is stated as 775 Kbps for BLE 4.2 
 Running</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Oct 2017 12:06:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25841/can-i-achieve-160kbps-through-ble4-2" /><item><title>RE: Can I achieve 160Kbps through BLE4.2?</title><link>https://devzone.nordicsemi.com/thread/101787?ContentTypeID=1</link><pubDate>Wed, 11 Oct 2017 12:06:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:205e5b48-0742-45f0-ac74-cc185ce8285a</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;I&amp;#39;m not sure if I understand. Throughput bottleneck? You shouldn&amp;#39;t get disconnects just because you try to send too fast. At least if you handle your buffers and queues gracefully in your application.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can I achieve 160Kbps through BLE4.2?</title><link>https://devzone.nordicsemi.com/thread/101786?ContentTypeID=1</link><pubDate>Wed, 11 Oct 2017 11:53:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d1ca6e6f-8856-4aa8-b520-4622a83c081d</guid><dc:creator>ndarkness</dc:creator><description>&lt;p&gt;Thanks @Martin, I will take a look into the link. Another question, setting &lt;code&gt;CONN_INTERVAL_MIN&lt;/code&gt; to 400 will grant that less connections/disconnections occur between the devices, since there I see that the bottleneck might be.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Can I achieve 160Kbps through BLE4.2?</title><link>https://devzone.nordicsemi.com/thread/101785?ContentTypeID=1</link><pubDate>Wed, 11 Oct 2017 10:01:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53b3e43d-6d09-4b24-8514-cc288592f90d</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;As you can see in the &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/ble_data_throughput/ble_data_throughput.html?cp=2_3_0_0_16"&gt;Softdevice Specification&lt;/a&gt; you will get the highest throughput with Connection interval 400ms and an MTU size of 247. You will also need to use data length extension and event length extension to get rid of overhead and to be able to transmit with 100% duty cycle in your connection intervals. Here is a link to a pretty informative blog post on the subject: &lt;a href="https://www.novelbits.io/bluetooth-5-speed-maximum-throughput/"&gt;Bluetooth 5 speed: How to achieve maximum throughput for your BLE application&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To increase the chances that the peer device accepts a connection interval of 400ms you should set both CONN_INTERVAL_MIN and CONN_INTERVAL_MAX to 400. This is because it is the central that ultimately decides on a connection interval, but by setting both min and max to 400, it is more likely that the central will respect that.&lt;/p&gt;
&lt;p&gt;I also suggest that you take a look in the S132 v3 Migration Document (bundled in the softdevice download) to learn more about bandwidth configuration.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>