GATT CONN TIMEOUT after rejecting connection parameters update

RE: GATT CONN TIMEOUT after rejecting connection parameters update

run_ar — Tue, 02 Jan 2018 12:30:58 GMT

@Nicole, Please consider creating a new question for your issue.

RE: GATT CONN TIMEOUT after rejecting connection parameters update

Nicole — Wed, 20 Dec 2017 09:38:37 GMT

Are there any updates to this circumstance by now? Experienced the same behaviour on nRF52832 even though never calling sd_ble_gap_disconnect() in the code.

RE: GATT CONN TIMEOUT after rejecting connection parameters update

etienne — Tue, 21 Mar 2017 08:56:01 GMT

Thx Kristin. we are currently debugging. will come back to you once we figure it out...

RE: GATT CONN TIMEOUT after rejecting connection parameters update

FormerMember — Tue, 21 Mar 2017 08:50:45 GMT

I would recommend you to check your code for sd_ble_gap_disconnec(), and find out where there is a chance that device has initiated a disconnect.

RE: GATT CONN TIMEOUT after rejecting connection parameters update

etienne — Tue, 21 Mar 2017 08:21:45 GMT

hi Kristin,

thats what we did, but why we still have GATT CONN TIMEOUT ? on iOS after 5/4h connection and on android sometimes in between (Using Connect App).

is there a way to stay also connected when the connection parameters update got ignored by the central...?? we know that the softdevice is handled it ;).

thx

RE: GATT CONN TIMEOUT after rejecting connection parameters update

FormerMember — Tue, 21 Mar 2017 08:03:58 GMT

The code in the peripheral side de has to be implemented such that it doesn't initiate a disconnect if the connection parameters are rejected (see for example update_timeout_handler() in ble_conn_params.c)

RE: GATT CONN TIMEOUT after rejecting connection parameters update

etienne — Mon, 20 Mar 2017 08:58:47 GMT

Hi kristin,

Thx for the fast answer, we really appreciate it. Your link on the chart makes it clear.

But we still have a question; Can we /How can we stay still connected (with central's connection parameters) after the central rejects the connection parameters ?

Thx

Cheers,

Etienne

RE: GATT CONN TIMEOUT after rejecting connection parameters update

FormerMember — Wed, 15 Mar 2017 08:36:30 GMT

A GATT CONN TIMEOUT (connection supervision timeout) will occur if one of the devices in the link doesn't send anything over the link for the period of the set CONN_SUP_TIMEOUT.

When the connection parameter update is rejected, the central has two options:

The central can reject the connection parameters, and the peripheral will have to decide what to do.
The central can ignore the connection parameter update, and there will be a linkloss upon connection supervision timeout.

This message sequence chart shows the two options.