BLE throughput to Android central quick start

RE: BLE throughput to Android central quick start

Edvin — Wed, 20 Nov 2019 09:07:24 GMT

Hello,

[quote user="yf13"]It seems that this nRF program will show the throughput at nRF sender side and it uses NUS for sending in a loop and will quit with any error. [/quote]

Yes. It uses NUS, and will send as long as there is free space in the queue for the softdevice. When it returns NRF_ERROR_RESOURCES, it means that it can't queue any more packets, and it will wait until the next TX complete event and try to queue more packets.

NUS is a custom service. It will not add any more overhead to the data stream than using any other service. I don't know if you noticed, but it should also print out what MTU size you get when you connect with your phone. This will typically vary from phone to phone. It also takes some time to change from 1MBPS to 2MBPS after the connected event.

Best regards,

Edvin

RE: How to quickly check BLE throughput to Android central device?

yf13 — Tue, 19 Nov 2019 00:58:02 GMT

Thank you Edvin!

It seems that this nRF program will show the throughput at nRF sender side and it uses NUS for sending in a loop and will quit with any error.

I feel that using NUS might be simpler than using a custom GATTS service --- is this right? Will NUS add any overhead to the one-way data streaming problem?

regards,

yf13

RE: How to quickly check BLE throughput to Android central device?

Edvin — Mon, 18 Nov 2019 14:22:15 GMT

Hello,

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_TP.zip

I wrote this example once for SDK14.1.0. It prints the throughput in the log. Connect to your phone with nRF Connect, and enable notifications on the TX Characteristic, and the nRF should print the throughpt every second or so.

If you want to use a later SDK, you can look at this one for inspiration, and port it to SDK16.

Best regards,

Edvin