BLE Disconnect Detect

RE: BLE Disconnect Detect

Ulrich Myhre — Fri, 04 Aug 2017 21:16:34 GMT

I suggest that you read up on the getting started guides for BLE in the Infocenter. You probably want to start with the SoftDevice Specification and nRF5x Getting Started guide. The disconnection event will manifest as a SoftDevice event of type BLE_GAP_EVT_DISCONNECTED, and depending on your setup it might trigger a Software Interrupt (SWI). There are some examples in the SDK that can get you started. Normally, the main code will pull events and optionally call a xxx_on_ble_evt() function for each module. The heart rate and NUS examples are easy to start with.

RE: BLE Disconnect Detect

Mehrdad — Fri, 04 Aug 2017 18:13:02 GMT

Is there any interrupt of event to handle this disconnection. Would you provide some guides for the code?

Thanks!

RE: BLE Disconnect Detect

Ulrich Myhre — Fri, 04 Aug 2017 17:49:55 GMT

Hi,

The answer is yes, you will get a disconnection event on both sides after some time.

When two peers fail to communicate over Bluetooth, either due to poor signal quality, noise or other issues, they will retry until the Supervision Timeout is reached. The Supervision Timeout value is set by the central device upon connection, and is specified in a multiple of 10 milliseconds. Whenever the time since the last successful communication exceeds the timeout value, the link is considered lost and a disconnection event is triggered.

So what you want is to make sure that the supervision timeout is quite low, in order to quickly detect issues. There are some rules from the Bluetooth spec on how low it can be, which depends on the other connection parameters, and the maximum on Nordic SoftDevices, it is 32000 milliseconds.

I also recommend reading this answer for more information about connection parameters and what guidelines that phones are adhering to:

devzone.nordicsemi.com/.../