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

Sniffer unable to capture NUS and HRM data

I had setup nRF sniffer with below software and hardware, but the Wireshark seen unable capture BLE data.

 

  • nRF Sniffer software nrf_sniffer_2.0.0-beta-1_51296aa.zip
  • nRF sniffer firmware “sniffer_pca10040_51296aa.hex” with nRF52 Development Kit (PCA10040) nRF52832.
  • Wireshark v2.4.2
  • SEGGER J-Link v6.16c
  • Windows 10 (64 bit)

 

I had built up the testing environment with Nordic Example as below list

  1. 1 x DUT “HRM” Heart Rate Application, DUT always update data to “Relay”, “Relay ” will forward data to iOS nRF ToolBox.

log : Console_log_HRM_20180831.txt

  1. 1 x DUT “NUS” UART/Serial Port Emulation over BLE, I have add peer management and paring with “Relay”, iOS nRF ToolBox able to transmit data ‘hello’, “Relay” will forward to DUT “NUS”.

Log: Console_log_NUS_20180831.txt

  1. 1 x DUT “Relay” BLE Relay Example, which add one more NUS service. It will take the data forwarding between DUT “NUS”/ “HRM” and iOS nRF ToolBox.

log : Console_log_Relay_20180831.txt

 

I can capture the device name "Nordic_HRM" \ "Nordic_UART" \ "Relay" with sniffer, but I can monitor any data for WireShark. Below Show my sniffer log.

 "Sniffer_Relay_NUS_HRM_20180831.pcapng"

Did I miss anything, I hope I can capture the data, because I have to looking the bug about I send the string once from nRF Toolbox to “Relay”, and forward to “NUS”, but those device had received twice. (confirm the console debug message from DUT “Relay” and “NUS”.)

Related