StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Issuing a <em>Connection Parameters Update</em> solved the problem and increased throughput from 5 kbit/s to <strong>~33 kbit/s</strong>. However, this is still below the expected ~305 kbit/s.</p> <pre><code>Conn_Interval = 0x000f = 18.75 ms Conn_Latency = 0x0000 Supervision_Timeout = 0x00fc </code></pre> <p>Are there any methods to reach the full ~305 kbit/s?</p> <p><strong><a href="https://electronics.stackexchange.com/questions/30964/improving-throughput-of-a-bluetooth-low-energy-connection">Follow-Up question on Electrical Engineering Stackexchange</a></strong></p> <blockquote> <p>Could get a reply from Apple by burning a TSI and waiting for a month.</p> <p>Basically, they tell that the behavior is intended in iOS 5.1. It somehow makes sense, because they don't want that your app's performance depends on whether another app uses Bluetooth or WiFi.</p> <blockquote> <p>Per the engineers comments - Under iOS 5.1 there should be 6 pairs of notifications during a connection interval, meaning 6*packetSize*1000/interval . This should translate to ~55kbps max (min interval is 20ms, packetsize is 23 bytes). We made the decision to limit the number of pairs per interval and have a minimum interval due to the fact that the iPhone and iPad both have shared antenna between BT classic, BT LE and WiFi.</p> <p>iOS LE is designed to be a low power transport. For higher throughput BT classic is a better transport method.</p> <p>Back to me - Based on the engineers comments above, if the desire is to achieve a 200 kbs throughput, Classic bluetooth is the answer. However, if the desire is to work with an application on the iPhone, I can understand that this is no simple change - Classic BT requires MFI licensing.</p> </blockquote> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload