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

Sniffer won't track specific device

Hi, I have run into a problem with the nRF sniffer. I used it in late May and early June to debug a BLE connection between a nRF-DK and a HTC Desire 610 and it worked fine, but now for some reason I cannot get it to track the device - whenever I make a connection the sniffer remains in the advertising channel reporting on other devices, even though I've selected the correct device to sniff from the sniffer's menu. It seems that the sniffer is not tracking that specific device at all, in fact, I get advertising packets from both that and a few other peripherals in wireshark.

I have tried monitoring the connection for both my current application, the version of that application I used earlier, and the ble_app_template in order to see if it was caused by a problem on the device side. I have also re-downloaded and installed both the sniffer, the firmware and wireshark. Finally, I have used both a usb development dongle and a development kit as sniffers but to no avail.

Upon switching from using the dongle to using the board as a sniffer, I initially had one session were I could connect, disconnect, and reconnect and the sniffer would follow gracefully, but I have been unable to recreate it.

I compared my current results with some logs from my earlier debugging, and as far as I can tell the sniffer shouldn't report traffic from devices other than that which I requested that it monitor. Since this is apparently not the case, it would seem that something is off with that mode, or specifying which device to track.

I am aware that the sniffer will sometimes miss connections, and noted that it did so during my initial debugging a few months ago. However, the current error is on a completely different scale, I have made in the order of 50 or so attempts to connect, and apart from that one session where it worked, I have missed them all.

Anyone have any idea what could be causing this?

Related