BLE 5 Advertisement packet not showing

[Domneck]

Hello,

We have already product with BLE 4 and now we are moving to BLE5. As per the example code we have updated our code to BLE 5 but we are not seeing advertisement packets but we are able to establish communication with different host/Central.  

Setup details:

SDK : nRF5_SDK_15.0.0_a53641a

Soft dev:s140_nrf52_6.0.0_softdevice

MCU: NRF52840.

Advertisement packet : Primary Phy:1M and secondary is: 2MPrimary Phy:1M and secondary is: 2M

Interesting observation is: BLE sniffer is able to show the advertisement packets but same we are not seeing with mobile, Our Gateway, and Laptop.

[Domneck]

Yes, I did one more experiment now by enabling central node on DK using BLE_APP_UART example.

Here I'm just printing the scanned data result to uart and I'm not seeing my device name but MAC I can see. 

But BLE 4 device I can see name & MAC both.

In debug mode I'm trying to capture memory contents now. 

[Einar Thorsrud]

I see. That makes sense, as the advertising name is in the AUX_ADV_IND packet, and that is only received by devices that support extended advertising. If you want to support legacy advertising as well you need two advertising sets as explained. That is only supported in the nRF Connect SDK, but an alternative if you use the nRF5 SDK is to reconfigure the advertising regularly and alternate between legacy advertising and extended advertising.

[Domneck]

I did one more experiment with examples given

• ble_app_rscs example code has support for BLE5 extended advertisement and for this I can see the device name in AUX_ADV_IND packet.
• ble_app_uart doesn't have support for BLE 5 and when I enable BLE 5 extended advertisement I don't see device name in AUX_ADV_IND, it's empty.

Plz suggest if I need to enable anything other than this below configuration:

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;

[Einar Thorsrud]

Hi,

I do not have any other suggestions than what I have already said, which is to alternate between extended and legacy advertising. That is how you can use and benefit from extended advertising while maintaining compatibility with legacy devices.

[Domneck]

I got it but I'm saying below things I tried as peripheral device and checking in BLE sniffer where I don't see the device name.

• ble_app_rscs example code has support for BLE5 extended advertisement and for this I can see the device name in AUX_ADV_IND packet.
• ble_app_uart doesn't have support for BLE 5 and when I enable BLE 5 extended advertisement I don't see device name in AUX_ADV_IND, it's empty.