Peripheral disconnection Handling at BLE softdevice layer

RE: Peripheral disconnection Handling at BLE softdevice layer

Susheel Nuguru — Thu, 16 Apr 2015 10:52:38 GMT

Hi Swetika, please accept the appropriate answer by clicking on the right mark so that we can close this issue.

RE: Peripheral disconnection Handling at BLE softdevice layer

Swetika — Thu, 16 Apr 2015 07:12:05 GMT

Thanks for reply Aryan!

RE: Peripheral disconnection Handling at BLE softdevice layer

Swetika — Thu, 16 Apr 2015 07:11:47 GMT

Thanks for reply Max C.

RE: Peripheral disconnection Handling at BLE softdevice layer

Susheel Nuguru — Wed, 15 Apr 2015 19:09:11 GMT

Max C. is right, when app is sending no data, the Link_Layer is always sending empty packets from each side just to keep the connection alive. It also uses supervision timeout value to rest and choose not even send empty packets within the supervision timeout as those transfer miss will not make the connection to lose, but that depends on many factors and the Link Layer is smart enough to make a wise decision.

RE: Peripheral disconnection Handling at BLE softdevice layer

Max C. — Wed, 15 Apr 2015 16:44:59 GMT

The RF link between central and peripheral is always "checked" by the devices at lower levels of the bluetooth stack because there is always a minimal data exchange (at a predefined timings) between devices also when there is no data exchange at application level (the code you directly write);

These "predefined timings" are defined by the GAP connection parameters, in which you specify:

minumum and maximum connection interval;
slave latency;
connection supervisor timeout;