Hi, I'm testing
-
nrf_sniffer_2.0.0-beta-1_51296aa
-
64-bit Windows 10 PC
-
J-Link v6.16c
-
64-bit Wireshark 2.4.3
-
PCA10031(v1.1.0, 2016.22, nRF51422 based dongle)
-
PCA10040 (flashed as NUS example to generate packets)
/////////////////////////////
- The good scenario
The LED LD1 shows the status of the dongle.
I observed that if the LD1 indicates purple only, Wireshark can detect the COMx interface.
After I select COM6, LD1 starts to blink like this. A white color was added periodically.
Looks like this indicates that the dongle is capturing packets.
So I can sniff packets with the dongle.
- Close Wireshark 2 and rerunning it
When LD1 was blinking, Wireshark 2 captured packets. I closed and reopened Wireshark 2.
Sadly, Wireshark cannot detect COM6 unless I plug the dongle out and connect it back.
- ETC: Timed out message
I connected my dongle and the PCA10040 which is flashed with the NUS (Nordic UART Service) example.
My iPhone was able to detect the PCA10040's advertisement.
Whereas Wireshark sometimes shows the above log message; Packet read timed out.
The dongle couldn't sniff anything when this message appears.
- ETC: Error by extcap pipe
or
When LD1 is white, Wireshark 2 cannot detect COMx interface.
However, in some cases, it detects COMx interface. When I start sniffing it, the above Python error is thrown.
Added 1/31 : After connection, Wireshark 2 doesn't capture discovery/characteristic packets
I flashed the modified BLE UART example; if the central sends data, the nRF52 echoes back.
I connected the Dongle at the USB hub to show this demo; the result was same if I connect the dongle at the back of my desktop directly.
After pairing, Wireshark 2 doesn't update captured packets anymore.
However, after disconnecting both devices, the ADV packets are captured.
//////////////////
In short
1.Do I always have to turn off and on the dongle before running Wireshark 2?
Without this off/on process, Wireshark 2 fails to find the COMx interface, regardless when the PCA10040 (COM5) was disconnected.
2.Is there a reason for observing the timed out message?
3.Although I have connected the dongle to the DELL' monitor's USB hub, is the hub a reason for creating that Python exception?
I wish to know the reason for this problem, too.
-Regards, MANGO
