This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Why advertising packet length in BLE sniffer is different with LL packet length ?

Dear experts..

I'm currently developing and testing nRF52832 application with nRF52-DK.

This are three questions about "actual" advertising packet length on air.


First > I wonder about that why the advertising packet length is 54 bytes in my application?

As attached below, i used BLE sniffer v1.0.1 and used BLE dongle and Wireshark v2.4.2.

Also, I confirmed that my information in the packet. There were 22 bytes of PDU

However, i can not understand that why advertising packet length is 54 bytes?

LL packet format in BLE v4.2 is

=> Preamble (1 bytes) + Access address (4 bytes) + Adv PDU (up to 37 bytes) + CRC (3 bytes)

I thought that in the advertising event, the packet length couldn't extend 45 bytes (1 Mbps and uncoded case)

In my application, it should be 30 bytes (1+4+22(PDU)+3).

When the 24 bytes come from?

Is there anybody know about this?


Second > if BLE advertising on-air data is 54 bytes (not 30 bytes) is true, then...

when i consider the current consumption in Radio, is TX time also calculated using 54 bytes data?

I have found many questions in this blog about current consumption or effective throughput, but

nobody consider about that. They only calculate those values based on LL packet size.


Third > Lastly, This is also related to BLE sniffer packet.

My application broadcasts 54 bytes of advertising data (I currently don't know about this) in about 1 second, through 3 channel.

However, I don't know about the certain data. As attached below, there are other data having 31 bytes of size.

Is there anybody know about this packet (?) or data(?)

In addition, the size of this data has changed timely (e.g. 29...->... 30...-> 31... 30.. 31..)

At least, I want to know that what kinds of data it is.

Thanks for reading...! and please answer the above questions...!

- DaeWoong Kim

Parents Reply
  • It's OK. I think 16 bytes of data might be BLE sniffers information (such as, measurement time, RSSI level, etc.).

    So, those packet length is same with expected length!.

    After connection, I could see the empty packet having data length of 26 bytes, which consisted of 16 bytes of BLE

    sniffer info- packets + 10 bytes of BLE LL packets (preamble + access address + LL header + CRC = 10).

    Anyway, thank you for your reply Slight smile

Children
Related