Advdata packet sequence

RE: Advdata packet sequence

pltv — Mon, 22 Jun 2015 16:59:41 GMT

Just a small additional comment that the manuf specifc data has first 2 bytes as the company identifier. Spent some time to figure this out

RE: Advdata packet sequence

pltv — Mon, 22 Jun 2015 16:58:03 GMT

Thanks. that covers it. Upgraded this to an answer

RE: Advdata packet sequence

Ulrich Myhre — Mon, 22 Jun 2015 13:40:09 GMT

It is always [Length (1 byte), Type (1 byte), Data ( bytes)] repeated over and over. The length byte is not included in the total length. The example you posted would be read as 9 bytes, type 8 (Shortened Local Name), (9-1) bytes of name in non-null-terminated UTF-8 "HHHHHHHH". The next part is 3 bytes long, type 25 (Appearance), 2 bytes of appearance (0x0000 = Unknown), etc. Go by the numbers found here and the descriptions found in the Core Spec Supplement.

RE: Advdata packet sequence

pltv — Mon, 22 Jun 2015 13:20:36 GMT

Which code you are referring to that i should look at? Is there any documentation of the standard encode sequence

Also if i have the below advdata, how would i decode it?

9 8 72 72 72 72 72 72 72 72 3 25 0 0 2 1 6 3 3 13 24 5 255 89 0 42 125

RE: Advdata packet sequence

RK — Mon, 22 Jun 2015 13:02:12 GMT

You can put it in any order you like. If you want to see the order in which the standard Nordic encoded encodes it, look at the code.

I've always thought it rather odd that it doesn't encode, or at least give you the option to encode, the name at the end instead of the start, as that would at least give it the option to fill most of the packet up and then use a short name instead of a full one if there wasn't room. But it doesnt.