https://devzone.nordicsemi.com/f/nordic-q-a/49906/10s-advertising-interval-and-connectionHi ENV: nrf52 + SES + SDK15 I have a scenario where the nrf52 peripheral can be advertising at the maximum interval allowed (~10s) . During the advertising it is also broadcasting useful and changing data using the manuf reserved zone of the broadcasteden-USTelligent Community 13Thu, 07 Nov 2019 15:18:17 GMThttps://devzone.nordicsemi.com/thread/219116?ContentTypeID=1Thu, 07 Nov 2019 15:18:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c65cbe91-cb37-4155-846e-ef17c8414c6ekrog1<p>I have a similar issue, in that faster advertising intervals will connect OK, and slower ones will consistently not. Specifically, a min-max of 0x1100-0x1250 works, but 0x1200-0x1400 doesn&#39;t, as well as larger values of course. I don&#39;t have any problem connecting to the peripherals with nRF Connect on Android, regardless of the advertising interval, so I thought that it was something I was doing on the Central.</p> <p>Looking at the traces on the central (I&#39;m using a pca10090 dev board), it&#39;s finding the device OK in the scan, and the call to bt_conn_create_le() returns OK, but I get a connection failure callback with error 2, which appears to be BT_HCI_ERR_UNKNOWN_CONN_ID in hci_core.c. It looks like this is coming all the way from the softdevice on the nrf52840, but I didn&#39;t confirm with the debugger.</p> <p>Since the device was found on the scan, I didn&#39;t think it was the scan parameters, but I tried several different options just in case. I&#39;m not even sure this is the same issue, but the working/not working interval times are similar, so I posted here rather than opening a new thread.</p> <p>I&#39;m using v1.14.99-ncs1 of NCS for both the peripheral and central.</p> <p>Thanks,</p> <p>Chris.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/198907?ContentTypeID=1Wed, 17 Jul 2019 09:27:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b6ee4217-67b2-4aac-806b-82977aa6e825Alex Co<p>Thanks a lot!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/198896?ContentTypeID=1Wed, 17 Jul 2019 09:07:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fe4c1d28-baad-4c66-afb7-041e1720e0dbJ&#248;rgen Holmefjord<p>Hi,</p> <p>I tested 10 seconds advertising interval in ble_app_blinky example (set APP_ADV_INTERVAL to 16000), towards stock ble_app_blinky_c example. It does connect, but it can sometimes take some advertising intervals before the central receives the advertising packet (3 tests showed 2, 7 and 4 intervals). The scan interval and scan window configuration of the central will affect the probability of receiving the advertising packet from the peripheral. Please have a look at <a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/bluetooth-smart-and-the-nordics-softdevices-part-1">this blog post</a> for details about how advertising and scanning work.</p> <p>Best regards,<br />Jørgen</p><div style="clear:both;"></div>