something wrong SPIS communication...

RE: something wrong SPIS communication...

Vidar Berg — Fri, 30 Dec 2022 13:13:11 GMT

Hello,

The max. throughput you can get with the Softdevice is shown in the specification here: Bluetooth Low Energy data throughput. Although this is likely to be limited by your central (PC).

Does the data packet length get increased in your gatt_evt_handler() callback after the connection is established? In any case, the throughput will become better if you can fill the full packet length (m_ble_nus_max_data_len) with multiple ADC samples instead of sending only one sample in each notification packet.

You may also want to increase the hvn_tx_queue_size via the sd_ble_cfg_set() API in ble_stack_init(). This will allow you to queue up more notification packets before ble_nus_data_send() starts returning NRF_ERROR_NO_MEM.

RE: something wrong SPIS communication...

KorJH — Fri, 30 Dec 2022 12:50:24 GMT

Hello,

I am check with this code,

I found many losses in BLE.

How can i increase BLE throghput?

Thank you.

RE: something wrong SPIS communication...

Vidar Berg — Fri, 30 Dec 2022 11:54:43 GMT

Hello,

The first thing I would suggest you do is to check the return code from ble_nus_data_send() to find out if your Bluetooth link is able to keep up with the sample rate.

e.g.

err_code = ble_nus_data_send(..);
if (err_code != NRF_SUCCESS) 
{
    NRF_LOG_INFO("Failed to send notification. (0x%x)", err_code);
}

Best regards,

Vidar