How to know which peripheral sent data to central

RE: How to know which peripheral sent data to central

awneil — Fri, 19 Jul 2019 08:02:23 GMT

Have you looked at the Mulit Link example?

This worked for me:

/**@brief Function for handling data received by the Nordic UART Service.
 *
 */
static void ble_nus_on_rx_data(uint16_t conn_handle, uint8_t * p_data, uint16_t data_len)
{
    uint8_t slot = find_slot_from_conn_handle( conn_handle );

    NRF_LOG_DEBUG("Rx Handle %d; slot %d:", conn_handle, slot );
    NRF_LOG_HEXDUMP_DEBUG(p_data, data_len);

    // m_ble_nus_c[conn_handle] identifies the connection on which the data arrived

the "slot" is how I identify particular peripherals.

RE: How to know which peripheral sent data to central

prodey — Fri, 19 Jul 2019 06:07:08 GMT

Thanks for the reply. Can you please elaborate?

As I mentioned in the question, in the periodic state BLE_NUS_C_EVT_NUS_TX_EVT, on receiving packets from the peripheral, the conn_handle is always 0, even if the event is triggered by different peripherals. So, every instance we get this periodic event, how do you know which peripheral is the source of this data?

Do I need to have separate event handlers for the 2 peripherals? In that case how to initialize and how to handle it in the db_disc_handler()?

RE: How to know which peripheral sent data to central

awneil — Thu, 18 Jul 2019 14:34:28 GMT

The Connection Handle identifies which connection data came it on.

So you would have to manage relating that to which particular peripheral in on which connection ...