How to decrease the possibility of BLE disconnection when in connected?

RE: How to decrease the possibility of BLE disconnection when in connected?

David Edwin — Mon, 14 Jan 2019 07:55:12 GMT

I am talking about a disconnect reason code.

in ble_gap.h

/**@brief Event structure for @ref BLE_GAP_EVT_DISCONNECTED. */
typedef struct
{
uint8_t reason; /**< HCI error code, see @ref BLE_HCI_STATUS_CODES. */
} ble_gap_evt_disconnected_t;

print out the reason along with the event that is received.

RE: How to decrease the possibility of BLE disconnection when in connected?

Ralph — Mon, 14 Jan 2019 06:58:41 GMT

It's a real problem. I just comment the inside stuff of pwr_mgmt_standby_timeout_check() so there is not any TIMED_OUT showing up. Are we talking about the same TIMED_OUT?

There is no log which shows the disconnect reason. Only m_coms: M_COMS_BLE_EVT_DISCONNECTED without any prior reason.

RE: How to decrease the possibility of BLE disconnection when in connected?

David Edwin — Fri, 11 Jan 2019 13:36:56 GMT

What is the disconnect reason code ? Typically a TIMED_OUT reason code can mean a lot of packet losses.

Stick in a sniffer and see what is happening.

Is this a real problem or are you talking about a hypothetical problem ?

RE: How to decrease the possibility of BLE disconnection when in connected?

Ralph — Fri, 11 Jan 2019 00:47:17 GMT

Yes, I do send battery level notification every 10 secs.

So it must be other reasons?

RE: How to decrease the possibility of BLE disconnection when in connected?

Kenneth — Thu, 10 Jan 2019 15:48:03 GMT

There is no reason why the peripheral should disconnect when in a connection, even if no data is sent. You may just send some battery level notification every 10 seconds, but it should not be necessary. A disconnect by supervisor timeout should only occur if they are out of range or one device is powered off after supervisor timeout period have elapsed.

Best regards,
Kenneth