Multi-NUS central and receiving data from peripherals

RE: Multi-NUS central and receiving data from peripherals

Hieu — Mon, 10 Jun 2024 07:54:56 GMT

Hi ropz, as the topic is quite different, I recommend opening a new DevZone case for it.

RE: Multi-NUS central and receiving data from peripherals

ropz — Mon, 10 Jun 2024 04:27:04 GMT

Hi, PW I want to know how to subscribe from several peripherals and send data to several peripherals. And how to create several discovery manager for when I add another function: bt_gatt_dm_start It will show that it cannot start discovery err:-120. Do you know how to solve this problem?

RE: Multi-NUS central and receiving data from peripherals

Hieu — Thu, 17 Aug 2023 07:42:38 GMT

Hi PW ,

I found a method that could be more proper. You can use the bt_conn_get_dst() API with the conn field in struct bt_nus_client.

This method works for other use cases where you don't have a client structure as well. In such cases, the address of struct bt_conn is not as reliable, because it can be recycled for another connection by the BLE stack.

Best regards,

Hieu

RE: Multi-NUS central and receiving data from peripherals

Hieu — Wed, 09 Aug 2023 08:37:07 GMT

No need, a quick detour like this is just fine 🙂

RE: Multi-NUS central and receiving data from peripherals

PW — Wed, 09 Aug 2023 08:15:51 GMT

OK. Please delete your answer.

RE: Multi-NUS central and receiving data from peripherals

Hieu — Wed, 09 Aug 2023 08:05:29 GMT

Let me answer this quickly, but for follow-ups, please consider opening a new question. We usually prefer to have each DevZone question focused on a topic.

There will be time slots for each connection, and collision should not be a concern.

RE: Multi-NUS central and receiving data from peripherals

PW — Tue, 08 Aug 2023 19:18:25 GMT

Thanks. I used:

uint8_t my_index = bt_conn_index(nus->conn);

I have general question about BLE multi-nus. What about collision? I have one client and several servers, they send data in random time. Is there any time slots for each of connection?

RE: Multi-NUS central and receiving data from peripherals

Hieu — Mon, 07 Aug 2023 20:04:21 GMT

Hi PW,

In the .received callback function, you can use the struct bt_nus_client * parameter to differentiate between peripherals.

The idea is that for each peripheral there is a NUS Client structure. Using the address of the client structure, you can differentiate between connections.

Best regards,

Hieu