Advertising type

RE: Advertising type

Aimek — Thu, 22 Sep 2022 14:25:02 GMT

Hi,

works like a charm, thank you 👍

RE: Advertising type

tesc — Thu, 22 Sep 2022 14:03:47 GMT

Hi,

Thank you for the explanation.

The following lines in main.c, in the function advertising_init(), enables features requiring extended advertising from Bluetooth 5:

    init.config.ble_adv_primary_phy      = BLE_GAP_PHY_1MBPS;
    init.config.ble_adv_secondary_phy    = BLE_GAP_PHY_2MBPS;
    init.config.ble_adv_extended_enabled = true;

Removing (or commenting out) those lines should make the device go back to only use Bluetooth 4 features. It should then appear as "Advertising type: Legacy" in the nRF Connect app.

Regards,
Terje

RE: Advertising type

Aimek — Thu, 22 Sep 2022 09:48:54 GMT

so is there a way to change the advertising type or no?

Forgot to mension, I am working with segger embeded

RE: Advertising type

Aimek — Wed, 21 Sep 2022 13:24:11 GMT

Hi,

I see this with the nRF5 SDK, version 17.1 and 16 and I am not sure, but if I am not mistaking anything but this happens also while using version 15.2

And about elaborating, here are some screenshots and in the field called "advertising type" it says either "Legacy" or "Bluetooth 5" and the issue is that I would like to know how to change the advertising mode to the legacy from the bluetooth 5, because I would like to figure out whether changing this setting would fix the issue of my application not being able to see discover the device.

RE: Advertising type

tesc — Wed, 21 Sep 2022 13:05:15 GMT

Hi,

Do you see this with the RSCS example from nRF5 SDK, or from nRF Connect SDK, and which version of the given SDK are you using?

[quote user=""]in rscs example the advertising type is Bluetooth 5, while in other examples its Legacy[/quote]

I am not quite sure what you mean by this, can you elaborate? E.g. what is advertising type in this context, how do you see it, and what other examples show a different behaviour?

Regards,
Terje