Packet loss sending data from iOS to nRF52 DK

RE: Packet loss sending data from iOS to nRF52 DK

Vidar Berg — Tue, 06 Feb 2018 10:22:26 GMT

Iphone 7 and newer also support long MTU, data length extension, and 2mbit mode if you want increase throughput even more:)

infocenter.nordicsemi.com/.../ble_data_throughput.html

RE: Packet loss sending data from iOS to nRF52 DK

skhan80 — Mon, 05 Feb 2018 17:06:38 GMT

Vidar, it is a read only Boolean and it seems that the Toolbox DFU code already dynamically uses the Boolean based on what iOS version the phone running the app is :) If it returns false, the peripheralIsReady(toSendWriteWithoutResponse:) event occurs. Using there two in unison I have achieved higher throughput on iOS 11 using a iPhone 7 Plus.

RE: Packet loss sending data from iOS to nRF52 DK

Vidar Berg — Mon, 05 Feb 2018 16:09:25 GMT

Thanks for the update. I was not aware of the new canSendWriteWithoutResponse() function. Hopefully it will remove the need to use PRN in the future.

RE: Packet loss sending data from iOS to nRF52 DK

skhan80 — Mon, 05 Feb 2018 15:55:38 GMT

Vidar, this is a great answer. I successfully improved throughput by sending N number of packets before waiting for a custom ACK from the DK. I am investigating the Nordic DFU implementation in the Toolbox app and have discovered that since iOS 11 a new addition to the iOS CoreBluetooth called canSendWriteWithoutResponse. This seems to be a way to get information on iOS underlying transmission buffer! It seems to be working on iOS 11.2 and above but broken currently on MacOS.

RE: Packet loss sending data from iOS to nRF52 DK

Vidar Berg — Fri, 02 Feb 2018 16:38:27 GMT

Hi,

As I understand it, this is a limitation with the Bluetooth framework on ios. App is not notified of buffer overflow in tx output buffer, and packets added while buffer is full will become lost. We've have run into the same problem for our DFU solution, and there we have solved it by using 'packet receipt notification'. I.e., the iphone will send n number of packets before having to wait for the next packet receipt notification. It's possible to implement a similar mechanism in the UART example, but will require changes in both app and FW.