Heartbeat with response to understand both mobile device is connected

RE: Heartbeat with response to understand both mobile device is connected

Serhan — Thu, 01 Oct 2020 10:47:09 GMT

Hello, I have implemented it the exact same way you described. It works as I wanted. But currently I refresh the timer only when heartbeat response received. How can i refresh the timer for any packet received?

Thanks & Best Regards

RE: Heartbeat with response to understand both mobile device is connected

Karl Ylvisaker — Wed, 30 Sep 2020 12:35:09 GMT

Hello,

Sorry for my late reply.

[quote user="Serhan"]thanks for your answer.[/quote]

No problem at all, I am happy to help!

[quote user="Serhan"]By unplanned disconnection I meant power off of mobile phone or disconnection because of distance. I want to detect this disconnection in 2-3 seconds and go back to advertising. Supervision timeout takes too long to go back to advertising state.[/quote]

I understand what you mean, thank you for clarifying.
This is usually what the supervision timeout feature is used for, but I understand your issue with the Android central dictating a too long supervision timeout.

[quote user="Serhan"]What came to my mind is, sending heartbeat every 2-3 seconds from peripheral and on the mobile phone side, during the handling of this heartbeat notification, writing to a write characteristic provided by peripheral. And in peripheral side check if this write characteristic is triggered every 2-3 secs. If not go back to advertising state. [/quote]

You could use the sd_ble_gap_disconnect function for this, as illustrated in this sequence diagram. You could have this function called following a timer timeout, and then refresh the timer with every received packet, or after a certain transfer has occurred. What do you think about this solution, could it work for your application?
The disconnect is usually handled by going back to advertising, so this will require only small changes to your existing code - namely the addition of such a timer.

Best regards,
Karl

RE: Heartbeat with response to understand both mobile device is connected

Serhan — Fri, 25 Sep 2020 14:05:20 GMT

Hello, thanks for your answer. By unplanned disconnection I meant power off of mobile phone or disconnection because of distance. I want to detect this disconnection in 2-3 seconds and go back to advertising. Supervision timeout takes too long to go back to advertising state.

What came to my mind is, sending heartbeat every 2-3 seconds from peripheral and on the mobile phone side, during the handling of this heartbeat notification, writing to a write characteristic provided by peripheral. And in peripheral side check if this write characteristic is triggered every 2-3 secs. If not go back to advertising state.

RE: Heartbeat with response to understand both mobile device is connected

Karl Ylvisaker — Fri, 25 Sep 2020 13:57:04 GMT

Hello,

[quote user=""]I want to detect unplanned disconnection of mobile device in 2-3 seconds.[/quote]

By this, do you mean a termination of the link from either side, or that a device stops responding - such as if it is out of reach?

[quote user=""]I tried to do this with supervision timeout but android forces its 20s supervision timeout.[/quote]

This is correct, it is the central that determines the supervision timeout.

[quote user=""]I am planning to implement a heartbeat that nrf51 sends and mobile phone receives, but i want to include give a response from the mobile phone to the heartbeat received from nrf51dk.[/quote]

Well, strictly speaking, every connection event will be such a heartbeat - because a connection event starts with the central sending a packet, followed by the slave's response, acknowledging the masters initial packet.

[quote user=""]How can i do this? is there any notify with response gatt type? or any other suggestions?[/quote]

Every packet sent over BLE needs to be acknowledged by the other device. If a packet is not acknowledged, then it will be re-transmitted until it is acknowledged or the timeout supervision is up, and the link is terminated.
I am not entirely sure what you would like to achieve here.
I suppose you could implement a timer that keeps track of how long time has passed since the last received packet - but this would come in addition to the existing timeout supervision timer. ~~Additionally, if you then were to send a link termination packet, it will not be acknowledged either, so the link will time out instead.~~
Could you tell me more about what you intend for the peripheral to do, if it does not receive anything from the central for 2-3 seconds?

Best regards,
Karl