connect timeout

RE: connect timeout

amywei — Fri, 04 May 2018 08:04:24 GMT

Hi,Sigurd

Thanks for your answer, I think I can solve my problem now

Best Regards

RE: connect timeout

Sigurd — Fri, 04 May 2018 07:58:33 GMT

Hi,

[quote userid="69821" url="~/f/nordic-q-a/34011/connect-timeout/130904"]If there is always an empty data packet interaction, will Bluetooth have a connection timeout?[/quote]

No, in that case you will not timeout.

[quote userid="69821" url="~/f/nordic-q-a/34011/connect-timeout/130904"]BLE_HCI_CONNECTION_TIMEOUT is a error code，not event ，how can i use it?[/quote]

In the event structure for BLE_GAP_EVT_DISCONNECTED, you will find the reason for the disconnect. See this page. If the disconnect happend because of a connection timeout, the disconnct reason will be BLE_HCI_CONNECTION_TIMEOUT.

Snippet:

static void on_ble_evt(ble_evt_t * p_ble_evt)
{
    uint32_t err_code;
    uint8_t disconnect_reason;

    switch (p_ble_evt->header.evt_id)
    {

        case BLE_GAP_EVT_DISCONNECTED:
            disconnect_reason = p_ble_evt->evt.gap_evt.params.disconnected.reason;
            if(disconnect_reason  == BLE_HCI_CONNECTION_TIMEOUT)
            {
                //disconnect_reason is BLE_HCI_CONNECTION_TIMEOUT
            }
            err_code = bsp_indication_set(BSP_INDICATE_IDLE);
            APP_ERROR_CHECK(err_code);
            m_conn_handle = BLE_CONN_HANDLE_INVALID;
            break; // BLE_GAP_EVT_DISCONNECTED

RE: connect timeout

amywei — Fri, 04 May 2018 01:44:33 GMT

Thanks

My BLE peripheral is in a connection with a central. In order to keep the connection, Bluetooth will send empty data packets to keep connection when there is no valid data interaction. If there is always an empty data packet interaction, will Bluetooth have a connection timeout?

BLE_HCI_CONNECTION_TIMEOUT is a error code，not event ，how can i use it?

RE: connect timeout

Sigurd — Thu, 03 May 2018 10:54:33 GMT

Hi,

If your BLE peripheral is in a connection with a central, and the central stops responding for so long that the supervision timeout triggers, you will get the event BLE_GAP_EVT_DISCONNECTED with reason BLE_HCI_CONNECTION_TIMEOUT (0x08). You will not get the event BLE_GAP_EVT_TIMEOUT.

If you are using the advertising module in the SDK, ble_advertising.c, the default behavior is to start advertising again after a disconnect. This happens in the function on_disconnected(). If you start advertising again, this will typically consume 30µA+ (depending on advertising interval)