<?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>Throughput BLE Meshv4 nRF52840</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62163/throughput-ble-meshv4-nrf52840</link><description>Hi community ! I saw a lot of subject about &amp;quot;Mesh throughput&amp;quot; which was outdated and i still have questions. I&amp;#39;m using nRF52840 DK with nRF5 SDK for Mesh v4.0.0 
 1) Does Bluetooth Mesh still based on Bluetooth v4.0 ? 
 2) I saw that max 11 byte payload</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 05 Jun 2020 13:14:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62163/throughput-ble-meshv4-nrf52840" /><item><title>RE: Throughput BLE Meshv4 nRF52840</title><link>https://devzone.nordicsemi.com/thread/253553?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 13:14:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c9bbda74-0bea-43c5-a9d9-e896b44dc788</guid><dc:creator>PaulGui</dc:creator><description>&lt;p&gt;Thanks again !&lt;br /&gt;For info, do you have an idea when sensor model will be out ? Or if an actual model could send logs ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Throughput BLE Meshv4 nRF52840</title><link>https://devzone.nordicsemi.com/thread/253551?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 13:07:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a0ae544-3a8f-4772-b7d6-9d5aeb16bf02</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Yes, connected BLE has the theoretical through put of 1.4Mbps (when running at 2Mbps) and 700kbps (when running at 1Mbps) . I have seen the practical throughput close to these number (~1.3Mbps and ~600kbps).&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Throughput BLE Meshv4 nRF52840</title><link>https://devzone.nordicsemi.com/thread/253546?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 12:58:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b6865d40-9a46-4131-8c9a-f93ee962e8a1</guid><dc:creator>PaulGui</dc:creator><description>&lt;p&gt;Thanks for your reply !&lt;br /&gt;Do you have practice throughput of classic BLE (p2p) on advertising and connected pls ?&lt;/p&gt;
&lt;p&gt;Cause i want to compare throughput between Classic BLE (p2p) and Ble Mesh to know if it&amp;#39;s better to implement Ble Mesh when sensor model will be out. &lt;br /&gt;Even if i&amp;#39;m expecting a huge gap between BLE and BLE Mesh&lt;br /&gt;Sincerely&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Throughput BLE Meshv4 nRF52840</title><link>https://devzone.nordicsemi.com/thread/253543?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 12:50:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb73f2be-abaa-4987-aed6-579431ce62aa</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Correct, 31 bytes payload for the advertising packet (37 bytes with the overhead) and 11 byte for actual mesh data.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The 3.45 kbps throughput is calculated on the 11 bytes of of actual payload.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Throughput BLE Meshv4 nRF52840</title><link>https://devzone.nordicsemi.com/thread/253527?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 12:02:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d2e6dad-5151-4e97-817c-8847522e08a2</guid><dc:creator>PaulGui</dc:creator><description>&lt;p&gt;Thanks for your quick reply !&lt;br /&gt;Just to be sure, Mesh messages have 31 bytes payloads but only 11 bytes for real information (string etc) ?&lt;br /&gt;And your &amp;quot;&lt;span&gt;3.45kbps point to point&lt;/span&gt;&amp;quot; is throughput for the entire message or only the 11 bytes of info ?&lt;br /&gt;Sincerely&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Throughput BLE Meshv4 nRF52840</title><link>https://devzone.nordicsemi.com/thread/253351?ContentTypeID=1</link><pubDate>Thu, 04 Jun 2020 15:27:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0179a6c7-6d8d-48f7-84c5-3794f801abfb</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;1) Yes, it&amp;#39;s mainly based on Bluetooth 4.0 however some Bluetooth 4.2 feature (Long ATT MTU) is supported on the GATT bearer connection but it doesn&amp;#39;t related to the mesh performance.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;2) Correct. Larger payload will be transmitted on segmented packets.&lt;/p&gt;
&lt;p&gt;3) It&amp;#39;s the payload of the advertising packet (37). It&amp;#39;s not the payload of mesh packet.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;span&gt;RADIO_MAX_PACKET_LEN&amp;nbsp; is the radio hardware max payload.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;4) In our test here the mesh throughput is roughly 3.45kbps point to point.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>