Advertising type

[Aimek]

I was testing out the custom application from android studio, and have discovered that, for example, when using the rscs example my application does not see the device and when using the simple ble gatt or uart or proximity examples, the application does see the nRF52840 DK. 

I have later discovered that the possible reason for that might be the advertising type of the device (in rscs example the advertising type is Bluetooth 5, while in other examples its Legacy)

Can someone explain how to change the devices' advertising type, I have checked many other guides, but most of them are talking about switching from connectable to non-connectable advertising type? 

If I have missed the guide, where my problem is explained, mention it in the replies please.

[tesc]

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?

in rscs example the advertising type is Bluetooth 5, while in other examples its Legacy

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

[Aimek]

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.

 

[tesc]

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

[Aimek]

Hi,

works like a charm, thank you