BLE connection takes long time with SDK17.1.0 example

RE: BLE connection takes long time with SDK17.1.0 example

karanbakshi — Tue, 16 Nov 2021 10:16:28 GMT

Hi Simon,

Thanks for clarification and support.

Regards,

Bipin

RE: BLE connection takes long time with SDK17.1.0 example

Simonr — Tue, 16 Nov 2021 10:12:15 GMT

Setting scan interval and window to the same will increase the chance to discover advertising devices as it will effectively be scanning for the entire scan interval instead of just for part of it, which I assume is why this resolved it. What might have occurred is that you missed an advertising because the app stops scanning after receiving one advertisement.

Best regards,

Simon

RE: BLE connection takes long time with SDK17.1.0 example

karanbakshi — Mon, 15 Nov 2021 10:08:40 GMT

Hi Simon,

After changing scan window to similar to scan interval, delay issue in connection resolved. Now it is connected in couple of seconds. Earlier scan interval was 160 and window was 80 so I have made both equal to 160.

for my knowledge, if you know, Does this change in scan parameter affects in connection timing?

Regards,

Bipin

RE: BLE connection takes long time with SDK17.1.0 example

Simonr — Mon, 15 Nov 2021 07:08:33 GMT

[quote user="karanbakshi"]With this kind of advertisement, I am facing delay in connection via central.[/quote]

I assume this is pointing to the Dongle central you're using, and you only see this (3 minute) delay when using this central? Can you show me a snippet of how you handle advertisements in your central device? If possible, could you do a sniffer trace of this happening, so we can see what causes this delay on the air. If you don't have a dedicated sniffer device, check out the nRF Sniffer that can be used with one of our DKs or the Dongle

Best regards,

Simon

RE: BLE connection takes long time with SDK17.1.0 example

karanbakshi — Fri, 12 Nov 2021 07:16:39 GMT

Hi Simonr,

Let me explain my advertisement logic here as I have observed one thing regarding it.

Peripheral device advertise interval is 2sec. With sample code, using stack advertisement function, there is not much delay in connection. it is connected within 10 second maximum.

But I am using timer based advertisement means running 2 second timer, on timer interrupt start advertisement, on radio notification event stops advertisement and start it again on next 2sec timer interrupt. set radio notification on NRF_RADIO_NOTIFICATION_TYPE_INT_ON_INACTIVE.

With this kind of advertisement, I am facing delay in connection via central. but with phone app as a central, it connects within some seconds.

I am following timer based advertisement because I am also controlling other iBeacon and Eddystone frames using same kind of timer and radio notification event.

Regards,

Bipin Patel

RE: BLE connection takes long time with SDK17.1.0 example

Simonr — Thu, 11 Nov 2021 14:19:45 GMT

Just to make sure. Are you saying it takes more than 3 minues from NRF_SUCCESS until the Dongle connects to the other one? The connection supervision timeout should trigger way before that. Can you try any of the default examples (ble_app_uart and ble_app_uart_c for instance) in the SDK to check if you are able to connect within a reasonable timeframe there? It shouldn't take more than a few seconds from when they both are turned on. I have tested with Coded PHY myself and have not seen this amount of time for a connection to be initiated successfully.

Best regards,

Simon