Periodic advertising data

RE: Periodic advertising data

Amanda Hsieh — Mon, 24 Feb 2025 22:11:06 GMT

Hi,

The BT_DATA_MANUFACTURER_DATA is set to the periodic advertising data by this line and shown as

-Amanda H.

RE: Periodic advertising data

DanisXZ — Sun, 23 Feb 2025 13:34:29 GMT

Hi Sigurd ,

Please find the sniffer file attached herewith. Device address is C4:C1:82:92:F3:CAdevzone.nordicsemi.com/.../5023.wireshark.pcapng

RE: Periodic advertising data

Sigurd — Wed, 27 Nov 2024 13:25:54 GMT

Hi!

Could you save and upload the sniffer file?

RE: Periodic advertising data

DanisXZ — Sun, 24 Nov 2024 14:11:27 GMT

Thank you Amanda Hsieh for your reply.

Why am I not seeing the periodic adv data in the sniffer ?

RE: Periodic advertising data

Amanda Hsieh — Mon, 18 Nov 2024 21:17:53 GMT

Hi,

1. The periodic_adv example starts Extended Advertising with the device name package, so it comes with the AUX_ADV_IND. See this line. Then BT_DATA_MANUFACTURER_DATA is set to the periodic advertising data with this line, so it comes with the AUX_SYNC_IND.

2. You can replace BT_LE_EXT_ADV_NCONN with BT_LE_EXT_ADV_NCONN_IDENTITY.

diff --git a/samples/bluetooth/periodic_adv/src/main.c b/samples/bluetooth/periodic_adv/src/main.c
index a927c82e16c..425eccdbae3 100644
--- a/samples/bluetooth/periodic_adv/src/main.c
+++ b/samples/bluetooth/periodic_adv/src/main.c
@@ -31,7 +31,8 @@ int main(void)
        }

        /* Create a non-connectable advertising set */
-       err = bt_le_ext_adv_create(BT_LE_EXT_ADV_NCONN, NULL, &adv);
+
+       err = bt_le_ext_adv_create(BT_LE_EXT_ADV_NCONN_IDENTITY, NULL, &adv);
        if (err) {
                printk("Failed to create advertising set (err %d)\n", err);
                return 0;

3. When you select a device in Wireshark, you're essentially synchronizing with its periodic advertising train. The sniffer follows the periodic advertising and subscribes to the subevent, which is why you're seeing the AUX_SYNC_IND packets nRF Sniffer for Bluetooth LE guide.

Regards,
Amanda H.