Connecting to a device that advertises infrequently

RE: Connecting to a device that advertises infrequently

Kenneth — Tue, 11 Jul 2023 07:52:09 GMT

You should look at using multiple advertisment sets to achieve this:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/multiple_adv_sets/README.html

Kenneth

RE: Connecting to a device that advertises infrequently

Frog — Mon, 10 Jul 2023 23:18:22 GMT

So the picture becomes a little more complicated...

What if I were to transmit one advertisement followed by a second after a short delay (maybe 200ms) with the intention that the 52840 sees the first advertisement and connects during the T_IFS period of the second?

From a power management point of view it would be ideal to keep the rx open only during the T_IFS of the second advertisement and not the first. Is there a way to coerce the BLE stack to transmit a first advertisement that is marked as connectable but doesn't wait for a connection, and then a second that isn't marked as connectable but does in fact allow a connection?

To complicate things a little further, I'd like to do this periodically (maybe once per minute) and advertise as non-connectable in between, although this may be more straightforward to do.

I'm using Zephyr and the 2.4.0 SDK.

RE: Connecting to a device that advertises infrequently

Kenneth — Tue, 09 May 2023 11:15:18 GMT

[quote user=""]My question is whether it is possible for the nRF52840 to receive an advertisement, decide (somehow) that it's appropriate to connect, and start to open a connection within that T_IFS period, or whether any attempt to connect will always result in the nRF52840 waiting for the next advertisement from the chosen device.[/quote]

Yes and no;

Yes, if you use the connect api to connect to a known peer device (e.g. you know the address of the peer).

No, if you plan for the application to analyze the content of the advertisment and try to connect immediately.

Kenneth