RE: checking if connection is bonded in multiperipheral device

lee-marc — Sat, 27 Apr 2019 17:13:04 GMT

Meanwhile I found the mistake (misunderstanding) in my firmware. I mixed the address (i) and the value of the array m_qwr[i].conn_handle.

RE: checking if connection is bonded in multiperipheral device

Einar Thorsrud — Fri, 29 Mar 2019 12:34:30 GMT

Hi,

I am not following exactly how you organize the connection handles. Essentially you just need to store them somehow for later use. The connection handle does not change for the duration of a connection, so as long as there has not been any disconnect it will stay the same and represent the same peer. (I do not see any reason for mixing with the QWR module, it could be kept separate.)

I suggest something like the following:

When a device connections the applications gets a BLE_GAP_EVT_CONNECTED event, which includes the connection handle.
Store the connection handle somewhere and start a single shot app timer with 10 seconds timeout.
If the connection is terminated before the timer expires, stop the app timer so that nothing more happens.
When the timeout occurs, check if the connection handle represents a bonded device using pm_peer_id_get().
If not bonded, disconnect by calling sd_ble_gap_disconnect().

The above method is a bit simplistic as it does not handle a second connection within the 10 second before checking if it has bonded so it needs a bit expansion to be complete, but it demonstrates how it can be done.