• State Verified Answer
  • Replies 7 replies
  • Subscribers 64 subscribers
  • Views 2805 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 111050
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF sniffer(1.0.1) only shows advertisements

msys_miyake

Dear team,

Our customer using "nRF51422 Development KiT8PCA10028)" with "ble-sniffer_nRF51822_1.0.1_1111_Sniffer.hex".

They can check advertising packets, but, they cannot check other packets. They confirmed by a production that 2 devices are communicating.

We know this phenomenon to have been improved in 0.9.6.

devzone.nordicsemi.com/.../

Is special setting somewhat necessary to get a packet besides the advertising packet?

Best Regards,

  • 0

    We are aware of some issues with nRF Sniffer. Please have a look at this.

  • 0

    Dear Mr.Petter,

    Thank you for your support.

    Our customer tried to the way by which mentioning was in developer zone as below.

    1.Start the sniffer 2.Put the slave/peripheral into advertising mode 3.Put the master/central into scanning mode (listening for broadcasts)

    However, unfortunetely, result didn't change.

    They executed the following steps. Would you please check and tell me any advices? step a) A pairing of Central (PC) and a peripheral device is released. After that Bluetooth of PC setting is turned off to make them suspend Central's (PC) scan. step b) They executed Sniffer. After that they started Wireshark by using with "w" key. * It's suitable for a procedure of the above 1. After starting, the state of Wireshark was changed into the packet capture state automatically. step c) The peripheral device is changed to a pairing mode and it's done in the advertising state. * It's suitable for a procedure of above 2. step d) Turn on the Bluetooth in Central(PC) setting and scan is begun. * It's suitable for a procedure of above 3. A peripheral device is chosen in a PC and executed a pairing. step e) After pairing completion, a packet of the user definition (data of a HOGP profile) is sent from a device. But this data can't be captured.

  • 0

    Are they selecting what peripheral device to follow? This procedure should be followed:

    1. Start the sniffer
    2. Start advertising
    3. Select what device the Sniffer should follow. There should be an x next to the device. It can be selected by using 0-9, or by using arrow keys+enter.
    4. Press w.
    5. Start scanning
    6. Now the sniffer should be able to follow the connection, and wireshark should show the packet transactions.
  • 0 in reply to Petter Myhre

    Dear Mr.Petter,

    Thank you for your support.

    They could get a packet correctly by the way you told us.

    I close this question.

  • 0 in reply to Petter Myhre

    Great! Then I would appreciate if you could accept my answer by clicking on the check mark next to it.

Related