Connection Timeout with nRF Connect Desktop tool

RE: Connection Timeout with nRF Connect Desktop tool

beemavishnu — Tue, 10 Mar 2020 09:48:47 GMT

Hi,

Please let me know your inputs on the experiment you did.

RE: Connection Timeout with nRF Connect Desktop tool

beemavishnu — Tue, 03 Mar 2020 14:35:16 GMT

Sure. Please share your inputs based on your tests. As mentioned, we need to use either Dongle or DK to connect to nRF Connect Desktop tool.

RE: Connection Timeout with nRF Connect Desktop tool

Sigurd — Tue, 03 Mar 2020 14:16:01 GMT

Hi,

[quote user="beemavishnu"]I am using nRF Development board for testing. I think it should be 20ppm.[/quote]

Based on my testing here, the problem seems to be the nRF52840 dongle. For me it seems like the nRF52840 dongle is not 20 ppm. If I use e.g. nRF52840 DK for nRF Destkop BLE app instead, I don't see this issue. I will do some more testing on this.

BR,

Sigurd

RE: Connection Timeout with nRF Connect Desktop tool

beemavishnu — Fri, 28 Feb 2020 11:55:07 GMT

Hi,

I am using nRF Development board for testing. I think it should be 20ppm.

Thanks & Regards

Vishnu Beema

RE: Connection Timeout with nRF Connect Desktop tool

Sigurd — Fri, 28 Feb 2020 11:32:19 GMT

Hi,

1) What is the ppm accuracy of your LF crystal ? Maybe it was set too low.

2) Passkey should be supported on nRF Connect Desktop app also.

3) nRF Connect Desktop parses the data for you. Raw format is not shown.

4) No support for different data type. Only hex values.

5) Yes, this seems to be a bug. "ms" should be removed.

RE: Connection Timeout with nRF Connect Desktop tool

beemavishnu — Wed, 26 Feb 2020 09:40:40 GMT

Hi,

With NRF_SDH_CLOCK_LF_SRC set to 1 and NRF_SDH_CLOCK_LF_ACCURACY to 1 now its working fine. Can you please clarify my above queries. For easy tracking, I updated once again.

1) With my settings it was working well with nRF Connect mobile app. With the changes you mention, will there be any impact on timing issues and Current consumption. Any reason why it is working with nRF Android app but not with nRF Connect Desktop tool.

2) Even we want to work with Static passkey. With Android app we are give passkey as input. With nRF Desktop tool what are the options to give passkey.

3) Similar to nRF Mobile app how to see RAW data of Advertisement packet in nRF Desktop connect tool.

4) Using nRF Connect app, I am able to select type of data. But how to do the same in nRF Connect desktop tool. I am not seeing such options.

5) Just a correction. For Latency there is no units. In below its showing as 5 ms when I configure Latency as 5.

Thanks & Regards

Vishnu Beema

RE: Connection Timeout with nRF Connect Desktop tool

Sigurd — Tue, 25 Feb 2020 18:01:18 GMT

Hi,

You can keep NRF_SDH_CLOCK_LF_SRC at 1.

1) Did you try to set NRF_SDH_CLOCK_LF_ACCURACY to 1 ? Did it change the behavior?

2) If it did not change the behavior, can you then try to caputure a sniffer trace ? See nRF Sniffer.

RE: Connection Timeout with nRF Connect Desktop tool

beemavishnu — Tue, 25 Feb 2020 16:38:18 GMT

Hi,

I am getting 0x8 as error

1) But NRF_SDH_CLOCK_LF_SRC is already set to 1. Still do I need to set NRF_SDH_CLOCK_LF_ACCURACY to 1.

2) I was working well with nRF Connect mobile app. With the changes you mention, will there be any impact on timing issues and Current consumption.

Thanks & Regards

Vishnu Beema

RE: Connection Timeout with nRF Connect Desktop tool

Sigurd — Tue, 25 Feb 2020 15:54:18 GMT

What is the disconnect reason on the nRF5-side ?

You can print it in ble_evt_handler() like this, snippet:

        case BLE_GAP_EVT_DISCONNECTED:
        
            NRF_LOG_INFO("Disconnected");
            NRF_LOG_INFO("Disconnected reason: 0x%x",p_ble_evt->evt.gap_evt.params.disconnected.reason)

If its 0x16 (BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION), then check if you are calling sd_ble_gap_disconnect() in the function on_conn_params_evt().

If its 0x08 (BLE_HCI_CONNECTION_TIMEOUT), then try to set NRF_SDH_CLOCK_LF_ACCURACY in sdk_config.h to 1 (500ppm), if you have NRF_SDH_CLOCK_LF_SRC set to 0.

RE: Connection Timeout with nRF Connect Desktop tool

beemavishnu — Tue, 25 Feb 2020 07:39:40 GMT

Hi,

1) There is no error on device side. It’s just disconnecting. Below is the RTT log. Even with original ble_app_blink, just changed with my BLE configuration and it’s just disconnecting. You can crosscheck as is with my settings.

2) With the settings you mentioned its working fine. But we need Connection interval for 1 sec and Slave latency as 5 so save battery. With my settings its working fine with nRF Connect Android app but not with nRF Connect Desktop tool.

3) As per my other ticket even there is issue with iPhone nRF Connect mobile app. If any issue with nRF Connect Desktop tool please check with your team.

https://devzone.nordicsemi.com/f/nordic-q-a/57945/connecting-to-nrf-connect-app-in-ipad

Thanks & Regards

Vishnu Beema

RE: Connection Timeout with nRF Connect Desktop tool

Sigurd — Mon, 24 Feb 2020 16:17:13 GMT

Hi,

[quote user=""]Then I selected “Pair…” with “IO Capability” as “No Keyboard, no display”. Now I am able to write/read. But once “Connection parameters updated for device” I am getting BLE_HCI_CONNECTION_TIMEOUT after 13sec.[/quote]

1) Does it work with these settings?

#define MIN_CONN_INTERVAL               MSEC_TO_UNITS(100, UNIT_1_25_MS)        /**< Minimum acceptable connection interval (0.1 seconds). */
#define MAX_CONN_INTERVAL               MSEC_TO_UNITS(200, UNIT_1_25_MS)        /**< Maximum acceptable connection interval (0.2 second). */
#define SLAVE_LATENCY                   5                                       /**< Slave latency. */
#define CONN_SUP_TIMEOUT                MSEC_TO_UNITS(7000, UNIT_10_MS)         /**< Connection supervisory timeout (7 seconds). */

2) Do you get any error-code on the nRF52 side? Any errors printed in the log from the nRF52(use Segger RTT or UART as logger backend)?