Extended advertising stops after connection gets established in nRF Connect SDK

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Levig — Wed, 07 Feb 2024 13:30:33 GMT

Hi Sukriti! Could you share with me how you could solve this?

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Sukriti — Fri, 15 Jul 2022 10:31:02 GMT

Hi Simon, thanks for the help. The issue got resolved, you can close the ticket!

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Sukriti — Fri, 15 Jul 2022 07:38:57 GMT

Oh, I'm sorry, yes you're right. I got confused while typing, wanted to say something else. I actually wanted to say that the connectable advertising set resumes only after getting disconnected. You said that i should be able to start the same advertising set after getting connected to a device. But I had already tried doing that, and i got the errors that i attached.

And in the sample, the second advertising set starts once the device gets connected (not the same set). The same set starts only after getting disconnected. I hope I'm able to convey where I'm getting stuck.

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Simonr — Fri, 15 Jul 2022 07:24:23 GMT

[quote user="Sukriti "]If use two sets (as used in the sample) and I make the second advertising set connectable, would it mean allowing two simultaneous connections[/quote]

Yes, you should be able to connect to two devices with different advertising sets.

You say that the multiple advertising sets sample only starts the second advertising after disconnection? That is not what the sample does by default though, it creates both advertising sets one at a time, starting one and creating the next adv. set afterwards. It should not be necessary to connect/disconnect at all to see both advertising sets started.

	err = non_connectable_adv_create(); //advertising set 1
	if (err) {
		return;
	}

	printk("Non-connectable advertising started\n");

	err = connectable_adv_create(); //advertising set 2
	if (err) {
		return;
	}

	printk("Connectable advertising started\n");

Best regards,

Simon

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Sukriti — Wed, 13 Jul 2022 16:27:35 GMT

[quote userid="75734" url="~/f/nordic-q-a/89864/extended-advertising-stops-after-connection-gets-established-in-nrf-connect-sdk/376800"]Alternatively if you want to use the same advertising set it's possible to start advertising with that also after connecting to the first device[/quote]

Exactly what I tried doing using the advertising connected callback (bt_le_ext_adv_cb), but I got the errors mentioned in the first thread. I'm unable to figure out how it can be achieved taking the multiple advertising sets sample as a reference, because this sample only starts the second set after the first one gets disconnected.

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Sukriti — Wed, 13 Jul 2022 16:22:17 GMT

Thanks Simon. So basically, while the peripheral is connected to one device, it is only "visible" to other devices (in a non-connectable mode) and can not connect to them. I'm not sure how the same set can be used with this approach, but I'll give it a try.

If use two sets (as used in the sample) and I make the second advertising set connectable, would it mean allowing two simultaneous connections (using disconnected callbacks for both the sets)?

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Simonr — Wed, 13 Jul 2022 13:58:40 GMT

One way to go about this would be to implement multiple advertising sets. This lets you start another advertisement once connected to one device for example, either similar or different to the first advertising set. We have a sample application available here. Alternatively if you want to use the same advertising set it's possible to start advertising with that also after connecting to the first device. Similar procedure to what is done in the advertising sets sample I think.

Best regards,

Simon

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Sukriti — Tue, 12 Jul 2022 13:21:58 GMT

Hi Simon,

I have attached both main files.. "adv_connected_cb" throws error, while "disconnected" resumes extended advertising after the peripheral gets disconnected.

The application has a custom service which contains readable (long) characteristic value. Notifications are also enabled. The same data is transferred to the connected device through both notification and read request/response. Notifications are sent out at intervals of 10 ms. I used nRF Connect Mobile App for Android as Central. This application is just a modified version of the Zephyr Peripheral example. I made changes to the prj.conf file, which I already mentioned in the previous thread.

/cfs-file/__key/communityserver-discussions-components-files/4/disconnected_5F00_cb.c

/cfs-file/__key/communityserver-discussions-components-files/4/adv_5F00_connected_5F00_cb.c

RE: Extended advertising stops after connection gets established in nRF Connect SDK

Simonr — Tue, 12 Jul 2022 13:01:31 GMT

What exactly does your application do after you connect to a device? Do you tell it to start advertising again after it has connected to the first central device? Can you show me your main file?

Best regards,

Simon