How to perform Extended advertisements with an advertising set for legacy advertising PDUs

[TilakL]

Hi,

Based on the below extract:

"Because older devices that don’t support Bluetooth 5 will not be able to discover extended advertisements, an advertising set with legacy advertising PDUs for older scanning devices should also be used, at least until Bluetooth 5 supported hardware is commonplace in the market." from https://blog.nordicsemi.com/getconnected/bluetooth-5-advertising-extensions

Kindly suggest a suitable example for how to set this extended advertisements with an advertising set with legacy advertising PDUs. I want to understand the power consumption in this configuration when compared to exclusive switching between Ext. Adv only and legacy advertising only.

Thanks,
Tilak

[ovrebekk]

Hi Tilak

I believe the Multiple Advertising sets sample in the nRF Connect SDK can be used for this. It sets up both a non connectable beacon style advertising using legacy advertising, and a connectible extended advertising set in parallel. 

For the nRF5 SDK I don't think we have any example for this. 

Best regards
Torbjørn

[TilakL]

Thank you very much Torbjörn.

[ovrebekk]

You welcome Tilak

[TilakL]

Hej Torbjörn,

Finally, I was able to install NCS and try the example you suggested. It looks like this example does not perform "Extended Advertising". Any pointers on how to do this would be great.

Meanwhile, it looks like it is not supported (3 years ago). Is this still true?

Thanks,
TIlak
ps: I have unmarked the above as "verified answer", as that example does not perform Extended Advertising, just regular beacons.

[ovrebekk]

Hi Tilak

You are correct, my apologies. Looking a bit closer I realize the bt_adv_ext API allows you to do extended advertising, but it supports legacy advertising also. 

Fortunately it seems the broadcaster_multiple sample uses proper extended advertising. In order to leverage the longer payload capabilities of extended advertising you just need to increase the value of the CONFIG_BT_CTLR_ADV_DATA_LENGTH_MAX parameter in the project configuration, and it should scale the size of the advertising payload accordingly. 

Best regards
Torbjørn