What is the max data throughput with S132 v3?

[jmc]

The absolute max throughput for the nRF52 using S132 v2 was 128 kbps.

The new S132 v3 was recently released and boasts throughput increases by 400%. Has anyone tested this and found the actual max throughput rather than an estimate? Is there example code for testing this?

[Martin Roa Villescas]

I actually found that there is a bug in the ble_nus_c.h. Now that the SoftDevice supports the Long ATT MTU increase, the uint8_t data_len variable inside the ble_nus_c_evt_t definition is not large enough to store values higher than 255. I changed the type to uint16_t, increased the MTU to the maximum, and started seeing throughputs close to 800 kbps. Could you report this bug?

[Ulrich Myhre]

Good catch! I have notified the team that works on the SDK, and they will track this internally.

[Nivetha]

Hi, Ulrich! my question is posted here. I want to keep the connection interval to 10ms, Can I still set MTU 247, DLE 251 to achieve max throughput with nrf52 DK. Please help!

[Ulrich Myhre]

You will have to do some experiments. At 10ms, the length of each connection event will be limited in order to start the next one.

[Nivetha]

Thanks, Ulrich. Currently, im using att_mtu as 48 bytes which is given as NRF_BLE_GATT_MAX_MTU_SIZE. Now for this case, the connection interval is 10ms and 10 samples each sample of 12 bytes are transmitted. Can the attribute data be 44 bytes ? or do I need to reduce to 20 bytes to send more packets in 1connection interval?