Understanding BLE_GATTC_EVT_TIMEOUT

RE: Understanding BLE_GATTC_EVT_TIMEOUT

Sigurd — Wed, 28 Dec 2016 09:55:00 GMT

Yes, calling sd_ble_gap_disconnect() will trigger BLE_GAP_EVT_DISCONNECTED . See this message sequence chart.

RE: Understanding BLE_GATTC_EVT_TIMEOUT

Boaz — Mon, 26 Dec 2016 10:01:42 GMT

Just to make sure: will calling sd_ble_gap_disconnect() when handling BLE_GATTC/S_EVT_TIMEOUT eventually trigger the BLE_GAP_EVT_DISCONNECTED event? I'm trying to unify business logic paths.

RE: Understanding BLE_GATTC_EVT_TIMEOUT

Sigurd — Thu, 22 Dec 2016 11:26:54 GMT

Hi,

Q1) Won't a client GATT timeout trigger a BLE_GAP_EVT_DISCONNECTED event anyway?

A1 ) No. The SoftDevice will disable all ATT traffic and mark the ATT connection as down, but it’s up to the application to do the final disconnect with sd_ble_gap_disconnect().

Q2) Why is BLE_GATTS_EVT_TIMEOUT (i.e. GATT server timeout) also checked?

A2) The SoftDevice can be configured to act concurrently as both a peripheral and as a central. In this case the code to check for both events is therefore added.