On Timeslot API, SoftDevice, and locked bytes

RE: On Timeslot API, SoftDevice, and locked bytes

leo_91 — Thu, 11 Feb 2016 16:42:07 GMT

...You know when you overlook a byte thinking it is part of the specification of non connectable advertising? That's totally what I did! I feel so dumb right now. The issue was solved with just that! Thanks!

RE: On Timeslot API, SoftDevice, and locked bytes

run_ar — Thu, 11 Feb 2016 16:17:35 GMT

0x16 -> seems like the length is wrong? 0x16 = 22 bytes?

RE: On Timeslot API, SoftDevice, and locked bytes

leo_91 — Wed, 10 Feb 2016 10:44:22 GMT

Edited the main post, now there should be the screenshot of the nRF Master Control Panel, togethet with the raw packet data. From the raw packet it is missing the 0x42 and the MAC address (the original, not the example one I used above).

RE: On Timeslot API, SoftDevice, and locked bytes

run_ar — Wed, 10 Feb 2016 10:30:57 GMT

Usually there would also be some additional data in the ad packet. Can I see what you receive on the scanner to check what is there?

RE: On Timeslot API, SoftDevice, and locked bytes

leo_91 — Wed, 10 Feb 2016 10:25:55 GMT

I agree with you run_ar, thanks. Yet what bugs me is that the floating byte is on the 25th position, not the 32nd, therefore I'm supposedly within the valid packet length.. with "25th" I mean w.r.t. the BLE packet structure, i.e. we send something like

0x42 0x16 - 0xFF 0xEE 0xDD 0xCC 0xBB 0xAA - 0x03 0x09 0xAC 0xAB - 0x16 0xFF 0x15 0x16 0x17 0x18 0x19 0x20 0x21 0x22 0x23 0x24 0x25 0x26 0x27 0x28 0x29 0x30 0x31 0x32

and the 0x25 byte is floating. I would expect the 0x32 (th) to be floating or undefined, in case of maximum packet size exceeded. Am I right?

It could be that maybe I'm not accounting for some additional packet length, and hence the 25th is instead the 32nd?

RE: On Timeslot API, SoftDevice, and locked bytes

run_ar — Mon, 08 Feb 2016 09:01:36 GMT

So, as you say; the maximum size of the advertisement data packet is 31 bytes. If you try to send longer ad packets than this I would not expect the scanner to understand it.