Helping increasing throughput, Weird deadtime behaviour

RE: Helping increasing throughput, Weird deadtime behaviour

Edvin — Tue, 17 Dec 2019 09:14:11 GMT

If you look in the ble_app_uart_example, this one has about the maximum throughput you can get, except using 2MBPS, I believe. What you want to look for is the NRF_SDH_BLE_GAP_DATA_LENGTH. Try setting this one equal to what it is in the ble_app_uart example (251).

What sort of throughput are you looking at? It is difficult to say whether you can improve it further without knowing what you already have. You can't use the radio 100% of the time. It has to follow the BLE specification.

BR,

Edvin

RE: Helping increasing throughput, Weird deadtime behaviour

lagrangepoint1 — Mon, 16 Dec 2019 19:34:32 GMT

The NRF_SDH_BLE_GAP_EVENT_LENGTH was set to 244. I found that as I increase the NRF_SDH_BLE_GAP_EVENT_LENGTH the time between the last packet and the next connection interval increased.

Is this suppose to be happening?

RE: Helping increasing throughput, Weird deadtime behaviour

Edvin — Mon, 16 Dec 2019 12:57:04 GMT

Hello,

What sort of throughput are you looking at? Have you enabled DLE (Data length extension)?

RE: Helping increasing throughput, Weird deadtime behaviour

Jimmy Wong — Sun, 15 Dec 2019 02:14:00 GMT

Hi,

What is the NRF_SDH_BLE_GAP_EVENT_LENGTH in your setting?

In the softdevice S140 specification v2.1, it shows the throughput as below.

I did the example code on throughput with packet error rate (https://github.com/jimmywong2003/nrf5-packet-error-rate-measurement-on-ble-connection).