Multiple NUS_C and NUS configuration

[Fabien Comte]

Hello,

I use a configuration with multiple NUS_C and NUS links. When I receive events, how to know the index ?

I have seen mutiple exemples using conn_handle but in a only NUS_C configuration (not mixed).

I tried with conn_handle but sometimes, one of my NUS_C can continue to receive data after peer disconnected so I am not sure...

[Edvin]

Hello,

How do you determine that you continue to receive data after it has disconnected? That shouldn't be possible.

Is it your central that is connected to multiple peripherals? How do you assign the conn_handles? I suggest that you look into the ble_app_multilink_central example to see how it is done here. Note that it requires some changes in ble_nus_c.c

Also, the ble_nus_c_evt_handler() doesn't contain the conn_handle of which connection it came from. If you want this, then you must add it in on_hvx() in ble_nus_c.c

Add the line:

ble_nus_c_evt.conn_handle = p_ble_evt->evt.gattc_evt.conn_handle;

before the line 

p_ble_nus_c->evt_handler(p_ble_nus_c, &ble_nus_c_evt);

[Fabien Comte]

Hello,

Thank you for your help. I already applied this fix (found in forum elsewhere). How can I get a strong index please ?

[Edvin]

To be honest, I am not sure I understand your issue. How do you determine that you keep receiving data after the disconnect?

[Fabien Comte]

Ok I found. I added a serial number in my transmissions and after disconnect BLE_NUS_C_EVT_NUS_TX_EVT continues to be called with the same frame.

I did that in my nus_c event handler to fix it:

  case BLE_NUS_C_EVT_DISCONNECTED:
			{			
				p_ble_nus_c->conn_handle           = BLE_CONN_HANDLE_INVALID;
				p_ble_nus_c->handles.nus_tx_handle = BLE_GATT_HANDLE_INVALID;
				p_ble_nus_c->handles.nus_rx_handle = BLE_GATT_HANDLE_INVALID;
			}

 

[userming]

Thank you!This solved my problem.