Advertising Interval on SDK14

[muon]

Hi,

I have programmed my nRF52 DK using the ble_app_beacon example from SDK 14 along with S132 V5. I have set NON_CONNECTABLE_ADV_INTERVAL to 3000. I was expecting to see advertisements on 3 channels, then a 3 second delay, then 3 advertising packets, etc.

When verifying this using a nRF Sniffer my board is transmitting 1 packet every 3 seconds (38, 3s delay, 37, 3s delay 39)

Is this correct?

Thanks.

[endnode]

Isn't that only limitation of your sniffer? Note that these cheap sniffers link nRF5x DK have only one radio and antenna so they cannot listen on all channels. I guess nRF Sniffer FW tries to rotate the channels and also it tries to catch on 37 and then rush to 38 and then to 39 to see all 3 packets but not necessarily true and all the time...

[Daniel Wang]

I'm actually seeing the same thing here as muon, it works fine on sdk13(3 packet every 3 seconds, 37,38 and 39). On SDK 14 im getting 1 packet every 3 seconds(37,38,39).......

[endnode]

Interesting. Then it should be SD version, can you verify? I was looking in S132 V5.0.0 documentation if behavior of GAP Broadcaster/Peripheral was changed in this way but cannot find it. But I might be missing it or simply this change in stack behavior wasn't properly documented...

[muon]

I've been using S132 V5.0.0 with SDK 14.0.0 and I get 1 packet every 3 seconds as Daniel Wang is seeing.

I have also tried S132 V4.0.2 with SDK 13.0.0 which is working fine, 3 packs every 3 seconds.

I did consider the nRF Sniffer might be an issue however S132 V4.0.2/SDK 13.0.0 works as intended so I think I can rule this out.

[Hung Bui]

Hi,

I just tested with the sniffer on PCA10028 Jlink v5.12f and a PCA10040 running ble_app_hrs in SDK v14.

I don't see any thing strange, still see all 3 packets in an advertising event.

Maybe you need to check if the hoping sequence configuration on the Sniffer is something else, not 37 38 39 ?