Disconnection time

RE: Disconnection time

Guillaume76 — Mon, 04 Sep 2017 16:10:01 GMT

I'm using s132 v5.0 I can implement the no disconnection option, should not be a problem. Thanks!

RE: Disconnection time

Martin Tverdal — Mon, 04 Sep 2017 13:42:03 GMT

Hi, disconnecting in Bluetooth LE requires you to send the disconnect to the peer, and then get an ack for that disconnection. The SoftDevice will not give the BLE_GAP_EVT_DISCONNECTED until the ACK is received.

This can take 1 or more connection intervals. You are seeing that it takes two connection intervals, which might be because the SoftDevice has a simplified logic where it will delay sending the disconnect by one event. What version of the SoftDevice are you using?

You can consider (carefully!), to not do disconnect() on your central application. But just disable the SoftDevice. This will cause your peer (slave application) to wait until whatever you have configured for supervision_timeout, before it gets the Disonnected event with reason BLE_HCI_CONNECTION_TIMEOUT. This might be acceptable, depending on your usecase.

RE: Disconnection time

Guillaume76 — Thu, 31 Aug 2017 12:23:27 GMT

Hello Martin, thanks for your comment. I will register a new case on my page to share more informations regarding this issue.

RE: Disconnection time

MartinBL — Thu, 31 Aug 2017 11:43:37 GMT

I'm not sure why it would seem that 2 connection intervals are required before the disconnect event is received. Are you able to provide a sniffer trace?