Time managing data from several peripherals - BLE over uart

RE: Time managing data from several peripherals - BLE over uart

Jared — Fri, 24 Jun 2022 10:53:11 GMT

I was thinking that you could have a global buffer for each peer and fill the corresponding buffer when your receive data from a peer. You check the size of the buffer each time you fill and if it's full then you print it out.. Again, this would not be quite optimal memory wise when you have a lot of peers..

RE: Time managing data from several peripherals - BLE over uart

vw_dev — Thu, 23 Jun 2022 15:42:33 GMT

So I would have a buffer declared in the function ble_nus_chars_received_uart_print() common to all the peer, and while this buffer is not filled with the data, I would block any other data to be put in the uart? (through app_uart_put).

like:

uint8_t buffer[107];

const uint8_t buffer_length = sizeof(buffer);

memset(buffer, 0 , buffer_length);

while (buffer[107] != \n) { //because the data will end with a \n

for (uint32_t i = 0; i < data_len; i++)
{
do
{
ret_val = app_uart_put(p_data[i]);
buffer[i] = p_data[i];
if ((ret_val != NRF_SUCCESS) && (ret_val != NRF_ERROR_BUSY))
{
NRF_LOG_ERROR("app_uart_put failed for index 0x%04x.", i);
APP_ERROR_CHECK(ret_val);
}
} while (ret_val == NRF_ERROR_BUSY);
}

}

RE: Time managing data from several peripherals - BLE over uart

Jared — Thu, 23 Jun 2022 12:45:12 GMT

Hmm, maybe it isn't the best solution for many connections. You shouldn't have to have a for loop in the ble event handler. You only need to direct ble_nus_chars_received_uart_print() to the data buffer when it has been filled and provide the buffer length.

RE: Time managing data from several peripherals - BLE over uart

vw_dev — Thu, 23 Jun 2022 12:01:44 GMT

Hello, thank you for the answer.

I work with only 2 peripherals but I could have around 20 peripherals in my future development.

Do you think it could be an idea to create as many buffers as perripherals connected?

If so, that means I could create a for loop in the ble_nus_c_evt_handler in the BLE_NUS_C_EVT_NUS_TX_EVT case, where, for each handle, I would print the buffer associated to each peer?

RE: Time managing data from several peripherals - BLE over uart

Jared — Thu, 23 Jun 2022 10:52:52 GMT

Hi,

The BLE_NUS_C_EVT_NUS_TX_EVT is generated when data is received from a peer regardless of which peer that is sending the data. To only print data from one peer at a time, you could declare two buffers of 6*18 bytes for each peer and only print them when the buffer has been filled. The event structure will contain the connection handle which you can use to differentiate between the two peers.

regards

Jared