RE: BLE_NUS_C_EVT_NUS_TX_EVT event received twice when the central connect peripheral second times

CSZ_110 — Wed, 03 Feb 2021 03:00:11 GMT

Thank you for your reply.Yes,you're right.I add a filter in ble_nus_c_on_ble_evt().When the connection handles didn't match ,make it return.By the way,I download the latest SDK 17.02 ,I found that the issue has already solved.I revised my code in the ble_nus_c_on_ble_evt() function :

if ( (p_ble_nus_c->conn_handle == BLE_CONN_HANDLE_INVALID)
||(p_ble_nus_c->conn_handle != p_ble_evt->evt.gap_evt.conn_handle)
)
{
return;
}

instead of the original code

if ( (p_ble_nus_c->conn_handle != BLE_CONN_HANDLE_INVALID)
&&(p_ble_nus_c->conn_handle != p_ble_evt->evt.gap_evt.conn_handle)
)
{
return;
}

Thanks again for you kind help.

RE: BLE_NUS_C_EVT_NUS_TX_EVT event received twice when the central connect peripheral second times

Vidar Berg — Mon, 01 Feb 2021 13:00:19 GMT

Hi,

It sounds like you are experencing the same as described in this post: https://devzone.nordicsemi.com/f/nordic-q-a/70651/double-notifications-on-multilink-example-with-custom-service? The solution I suggested there was to ignore the event whenever the connection handles didn't match.