Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 19 (0x13)

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 19 (0x13)

Edvin — Thu, 22 Feb 2018 14:41:02 GMT

Could you either post the sniffer trace (file, not just screenshot) or send the projects, so that I can create my own sniffer trace? If you do not want to publish it here, you can send me a PM here on DevZone.

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 19 (0x13)

Arepa — Wed, 21 Feb 2018 16:02:12 GMT

update: I had tried that before, I put some breakpoints when disconnect_on_fail, but the program never reaches there also I commented out the sd_ble_gap_disconnect().and it still disconnect when the connection interval is below 100

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 19 (0x13)

Arepa — Wed, 21 Feb 2018 14:38:28 GMT

Hi Ed, I am trying to connect between two nRF52 one central and a peripheral, but where I was getting the problem is with the central, I apologize I thought I said it before.

both have the same setup for MIN and MAX connection interval, 7.5 and 25 respectively. when the MAX connection interval is above 100 it works fine but, when it is lower I get the random disconnect.

I am going to test using the breakpoint in ble_conn_params.c

I solved my issue in this way. But I am still wondering why it was disconnecting and from where it was disconnecting. Because on neither central or peripheral run into my breakpoint on ble_conn_params and I also commented the sd_disconnection command for both

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 19 (0x13)

Edvin — Wed, 21 Feb 2018 11:54:02 GMT

What are you trying to connect to? Is it something you have made yourself, or is it a phone, or what is it?

It looks like you have conflicting connection intervals on the two connected devices. Do you know what the preferred connection interval settings is for the central?

Basically, the central decides the connection interval. If the peripheral is not satisfied with the connection interval (if it is not between MIN and MAX), it can decide to disconnect. You can try to set a breakpoint in ble_conn_params.c, on line 106, and see if that is the place where it disconnects.

If that is the place, and you don't care about the connection interval, you can try to change the conn_params setup. I don't know what your setup looks like, but if you set disconnect_on_fail to false, then you should not disconnect even if the conn_params you desire is not met.

static void conn_params_init(void)
{
    uint32_t               err_code;
    ble_conn_params_init_t cp_init;

    memset(&cp_init, 0, sizeof(cp_init));

    cp_init.p_conn_params                  = NULL;
    cp_init.first_conn_params_update_delay = FIRST_CONN_PARAMS_UPDATE_DELAY;
    cp_init.next_conn_params_update_delay  = NEXT_CONN_PARAMS_UPDATE_DELAY;
    cp_init.max_conn_params_update_count   = MAX_CONN_PARAMS_UPDATE_COUNT;
    cp_init.start_on_notify_cccd_handle    = BLE_GATT_HANDLE_INVALID;
    cp_init.disconnect_on_fail             = false;
    cp_init.evt_handler                    = on_conn_params_evt;
    cp_init.error_handler                  = conn_params_error_handler;

    err_code = ble_conn_params_init(&cp_init);
    APP_ERROR_CHECK(err_code);
}

However, the best solution would be to set the desired max and min connection interval to something that is supported by the central.

Best regards,

Edvin

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 19 (0x13)

Arepa — Tue, 20 Feb 2018 22:51:04 GMT

Hey Ed, I think I found the problem, but it is still very disconcerting.... how I said above I am getting random disconnections since the connection is established I am always getting disconnection reason 0x19[BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION]

If I change the values for MIN_CONN_INTERVAL and MAX_CONN_INTERVAL to bigger numbers it does not happen anymore, for example, I was working with MIN_CONN_INTERVAL =7.5 and MAX_CONN_INTERVAL =25 and I was getting random disconnections. I changed the values respectively to 100 and 200 and it is now working fine.

What could be the cause of this behavior?

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 8

Edvin — Tue, 20 Feb 2018 15:44:47 GMT

send me a PM here on devzone.

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 8

Arepa — Tue, 20 Feb 2018 14:30:29 GMT

Hi Ed, sure I can. But can you test the project a project made on visualgdb? And is there a way to share it private instead posting here?

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 8

Edvin — Tue, 20 Feb 2018 14:23:42 GMT

Commenting out all sd_ble_gap_disconnect()s will not keep the devices connected. One device will disconnect if the other one e.g. stops responing.

Could you zoom a bit out on the sniffer log?

It says that the slave sends the disconnect message. What device are you trying to connect the nRF to? Is it a phone or another nRF (e.g. with nRF Connect for Desktop)?

Would it be possible to send the entire project instead of the snippet? Or something that I can reproduce the error with?

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 8

Arepa — Tue, 20 Feb 2018 00:00:02 GMT

Hey Ed, I found my central device is being forced to perform a disconnection, but I am not calling it anywhere, I commented all my sd_ble_gap_disconnect() on my central and peripherical and it is still disconnecting reason 19 or 0x13

What other functions can perform a disconnection besides sd_ble_gap_disconnect?

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 8

Edvin — Mon, 19 Feb 2018 09:27:00 GMT

Hello,

I understand. What device are you trying to connect to? the nRF is the peripheral in the connection? Do you try to connect to a phone acting as a central? Can you try to connect to another nRF using nRF Connect for desktop, and see if you get any information in the log there? Or can you try to provide a sniffer trace, e.g. using nRF Sniffer?

The reason I want you to try nRF Connect for desktop is that not all devices support LESC. The nRF Connect for desktop using another DK does support this, so it is only to see if the error is on the peripheral side, or on the central side. A supervision timeout suggests that there is something missing from the central, or perhaps there is something that you are not handling correctly on the peripheral side. A sniffer trace would shed some light on this.

Best regards,

Edvin

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 8

Arepa — Fri, 16 Feb 2018 17:20:48 GMT

Hi Ed, after the BLE_GAP_EVT_LESC_DHKEY_REQUEST, I got a BLE_GAP_EVT_DISCONNECTED event from there I printf "p_ble_evt->evt.gap_evt.params.disconnected.reason" and I got error 8 or error 19, my code was working fine until I added the code on BLE_GAP_EVT_LESC_DHKEY_REQUEST it is still unknown for me what is generating it disconnection the only I got is the error code

RE: Disconnection after BLE_GAP_EVT_LESC_DHKEY_REQUEST error 8

Edvin — Fri, 16 Feb 2018 13:33:13 GMT

Hello,

Could you specify what function that returned error = 0x08?