ble-sniffer not capturing "my" advertising packets

RE: ble-sniffer not capturing "my" advertising packets

Torsten Robitzki — Thu, 27 Aug 2015 09:44:20 GMT

@David but it's this additional (I think broken) trailing zeros that the sniffer needs to be able to display the device ;-) I think there is a bug in the advertising package generated by the S310 softdevice and that the sniffer needs that bug to be able to display the data. But, even when it's not a bug in the advertising data, I would expect a sniffer to be more tolerant, as it is a tool to find bugs :-)

Anyway: Thank you very much for taking the time to look into this.

RE: ble-sniffer not capturing "my" advertising packets

David Edwin — Thu, 27 Aug 2015 09:33:07 GMT

Yes, I think the packet is being dropped since it does not fit the rule of len, type, data. I would suggest that you remove the trailing zeros and reduce the RF packet size or increase the AdvDAta length so that it fits the RF length.

RE: ble-sniffer not capturing "my" advertising packets

Torsten Robitzki — Thu, 27 Aug 2015 08:36:15 GMT

@David What do you think of my findings regarding the difference of both advertisings. Could this be the difference, we are looking for?

RE: ble-sniffer not capturing "my" advertising packets

Torsten Robitzki — Thu, 27 Aug 2015 07:48:48 GMT

I've attached the log. Looks like the sniffer is able to receive the GAP data but has problems with the content?

RE: ble-sniffer not capturing "my" advertising packets

David Edwin — Thu, 27 Aug 2015 07:25:10 GMT

Can you attach your log files that you get with the "s" option.

Do you have padding bytes in the advertising packet (AdvDAta) ? Can you remove the padding bytes as it is not following the Adv Data standard of (len, type, data)

RE: ble-sniffer not capturing "my" advertising packets

Torsten Robitzki — Wed, 26 Aug 2015 18:51:20 GMT

@David I've managed to get the Sniffer up and running under Windows, but with the very same result. A device with s310 was found (two times) and advertising open source implementation is not found. If you are interrested in reproducing this, I would be happy to give you the firmware ;-)

RE: ble-sniffer not capturing "my" advertising packets

Torsten Robitzki — Wed, 19 Aug 2015 09:59:45 GMT

Yes, I think I can get my hands on a windows box next week. I'll put a reminder in my calendar.

RE: ble-sniffer not capturing "my" advertising packets

David Edwin — Wed, 19 Aug 2015 07:27:54 GMT

The OS X sniffer frontend does not support this option "h". Can you check if the advertisements are viewable on the nRF master control panel on the PC or with the sniffer on a windows PC ?

RE: ble-sniffer not capturing "my" advertising packets

Torsten Robitzki — Tue, 18 Aug 2015 12:39:53 GMT

Silly me, I forgot to mention that I'm using the OS/X frontend for the sniffer (ble-sniffer-osx). I double checked, that my implementation is sending advertising packages on all 3 advertising channels. I can see them using ubertooth, but I can't see them using ble-sniffer-osx, nor can I see any advertising packages when I used the python example.py (mySniffer.getDevices() yield [])

RE: ble-sniffer not capturing "my" advertising packets

Torsten Robitzki — Mon, 17 Aug 2015 13:00:18 GMT

@David Thank you for the tip. I'm currently on vacation and forgot all the USB cables to work here :-( I'm quit sure, that my example is just advertising on channel 37. I will make more tests when I'm back in my office.

RE: ble-sniffer not capturing "my" advertising packets

David Edwin — Mon, 17 Aug 2015 10:03:54 GMT

If you are advertising only on one channel and using the Nordic sniffer, set the sniffer to use only one advertising channel by using the "h" option and then 7 7 7 Which will set the sniffer to use only channel 37. Let me know if this works for you.