<?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>Optimizing throughput</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9610/optimizing-throughput</link><description>Hello, 
 I am currently optimizing the throughput for my mesh network and I am wondering whether I&amp;#39;ve hit the limit of what&amp;#39;s currently possible. I have two methods for sending data, reliable (write_req) and unreliable (write_cmd). 
 
 As far as I</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 09 Oct 2015 10:39:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9610/optimizing-throughput" /><item><title>RE: Optimizing throughput</title><link>https://devzone.nordicsemi.com/thread/35512?ContentTypeID=1</link><pubDate>Fri, 09 Oct 2015 10:39:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbdf6483-1994-4c82-8858-c5f6e3603d27</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@ Marius: For beta release, I would say ..weeks :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Optimizing throughput</title><link>https://devzone.nordicsemi.com/thread/35511?ContentTypeID=1</link><pubDate>Thu, 08 Oct 2015 13:31:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63268760-6c6b-45cf-9f1f-b1530e48ac5f</guid><dc:creator>Marius Heil</dc:creator><description>&lt;p&gt;Thanks, that covers my questions :-) Now I&amp;#39;ll only have to wait until the next release of the SoftDevice. Any rough timeframe on a beta release? weeks, months or years?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Optimizing throughput</title><link>https://devzone.nordicsemi.com/thread/35510?ContentTypeID=1</link><pubDate>Thu, 08 Oct 2015 09:12:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:27fbaddf-d648-4800-acf6-def442ffd37c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Marius,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;We are working on flexible solution where you can choose to reduce the max number of concurrent connection to have more packet per connection event. It will be available most likely in the next release of the S130.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;2)If you can send more than 1 packet per connection event, the master can ACK to the last packet from Slave to Master. However, it&amp;#39;s not the case with current S130.&lt;/p&gt;
&lt;p&gt;3)It&amp;#39;s about the MD bit in the link layer packet, please have a look at section 2.4 Vol 6 Part B in Bluetooth Spec v4.2. The slave can request to send more packet (MD=1), but if the master won&amp;#39;t support more packet, there will be no more packet in that connection event.&lt;/p&gt;
&lt;p&gt;4)It&amp;#39;s on first come first served base, no priority. But next packet (any type) can only start when earlier write request has been confirmed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>