Multi-NUS central and receiving data from peripherals

[PW]

Hello. 

I modified multi-nus central example to connect with four peripheral devices. I don't use uart at all, I don't need it, I don't need routing, I just send 16B frames beetween central and peripherals. It works fine, I can connect, send data to any peripheral I want. I'm receiving data from peripherals also, but I don't know which peripheral send me data. I know that central device in example code send address to peripheral after connection. Is it possible to do it in another way? Maybe something changed in conn_ctx lib since time when it was published? I'm using NCS 2.4.0.    

Best regards

PW

[Hieu]

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

[PW]

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?

[Hieu]

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.

[PW]

OK. Please delete your answer. 

[Hieu]

No need, a quick detour like this is just fine

[ropz]

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?

[Hieu]

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