How to know the central and peripheral are still connected

RE: How to know the central and peripheral are still connected

Andrew — Fri, 05 Feb 2016 20:39:44 GMT

conn handle 0 is a valid conn handle. You would want to check for BLE_CONN_HANDLE_INVALID, which is 0xffff

RE: How to know the central and peripheral are still connected

Konrad Traczyk — Fri, 05 Feb 2016 14:26:15 GMT

Shouldn't checking the m_conn_handle variable be enough? If it is set to 0 - the device is not connected, if anything else - it is connected.

RE: How to know the central and peripheral are still connected

Torsten Robitzki — Thu, 04 Feb 2016 09:16:47 GMT

If you designed the software, to do so, I would expect the device to do it.

RE: How to know the central and peripheral are still connected

Susheel Nuguru — Thu, 04 Feb 2016 09:13:31 GMT

The system will still go to sleep mode if you have called sleep funtion in a loop in your main(). The system will however wakeup every connection interval to send empty PDUs to keep the connection alive and then go to sleep again because you are calling sleep function in a loop.
Just make sure that you did not get BLE_GAP_EVT_DISCONNECTED event.

RE: How to know the central and peripheral are still connected

Minh — Thu, 04 Feb 2016 09:12:46 GMT

If devices still exchange empty PDU, does peripheral device go to sleep mode ?

RE: How to know the central and peripheral are still connected

Torsten Robitzki — Thu, 04 Feb 2016 09:03:33 GMT

No, in Bluetooth LE, there are still empty PDUs (protocol data units) exchanged, and this is nessary to synchronize the master and slave (central and peropheral). If you do not want this to happen, you have to disconnect the devices.