How to manually disconnect a certain peripheral from a central on SDK 16?

RE: How to manually disconnect a certain peripheral from a central on SDK 16?

Yeyzz — Fri, 01 Apr 2022 01:36:28 GMT

Oh i was thinking that the function "nrf_ble_qwr_conn_handle_assign(&m_central_qwr, m_conn_handle);" call in the example after a connection was a necessary step for validate or something the connection. Anyways it works creating a new conn_handle for the central and disconnect that one with disconnect call. So i think the extra step of the QWR module instance for the central was not necessary.

RE: How to manually disconnect a certain peripheral from a central on SDK 16?

Einar Thorsrud — Thu, 31 Mar 2022 09:21:34 GMT

I may be missing something, but why do you refer to the QWR module in relation to how to terminate a connection? The QWR module has its uses, but disconnecting the connection is a GAP operation that is not related to QWR in any way. (Also, the queued write module subscribes to BLE events so when you disconnect as I explained in my previous post, it will also get the BLE_GAP_EVT_DISCONNECTED and change the internal state accordingly).

Regarding using QWR for multiple connections you need multiple instances, yes. You can for instance see how that is done in examples\ble_central_and_peripheral\experimental\ble_app_hrs_rscs_relay\main.c where an array of instances is declared using NRF_BLE_QWRS_DEF().

RE: How to manually disconnect a certain peripheral from a central on SDK 16?

Yeyzz — Wed, 30 Mar 2022 14:20:49 GMT

For this i have to create another instance of the QWR? or is fine use the same one that the peripheral?

RE: How to manually disconnect a certain peripheral from a central on SDK 16?

Einar Thorsrud — Wed, 30 Mar 2022 13:22:13 GMT

Hi,

You will get a BLE_GAP_EVT_CONNECTED event when a connection is established both in the central and peripheral role. With that, you get a connection handle which is used for all subsequent API calls and events for the lifetime of that connection. With the BLE_GAP_EVT_CONNECTED event you are also informed about the role (see ble_gap_evt_connected_t). To disconnect, simply call sd_ble_gap_disconnect() with the connection handle of the connection you want to terminate. This is done in exactly the same way irrespective of the role.