Where is the proper place to close a connection when a service is not discovered

RE: Where is the proper place to close a connection when a service is not discovered

Susheel Nuguru — Tue, 03 Jul 2018 17:06:59 GMT

that is also a good way to do it. thanks for updating us on one additional way to do it.

RE: Where is the proper place to close a connection when a service is not discovered

David Andresky — Tue, 03 Jul 2018 14:13:02 GMT

Thanks, I want to avoid editing SDK files. I ended up adding it to the ble_pss_on_db_disc_evt in my client code module so that if I fail to discover the desired UUID then I will close the connection. I also added to the BLE_GATTC_EVT_READ_RSP after read an attribute. This seems to satisfy my needs for now.

RE: Where is the proper place to close a connection when a service is not discovered

Susheel Nuguru — Thu, 28 Jun 2018 08:29:15 GMT

Hi,

Calling disconnect unconditionally in the on_srv_disc_completion will make the calling device disconnect even if discovered your service.

I would add a boolean, which is initialized to false and set to true when you found the service. Then fence the disconnect call with the logic of this boolean.

if(false == service_found)
{
   err_code = sd_ble_gap_disconnect(conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
   APP_ERROR_CHECK(err_code);
}

And to answer your question, with this small change, placing disconnect in on_srv_disc_completion looks good.