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

My question is pertaining to running of sniffer to show my device name

50 MHz, 500 M Samples [16].logicdatamainc.txt(/attachment/98d67704ad9c5affad8d5bce2ef93315)(/attachment/f20245cb8f1c01edb4b17875b6eedc4b)01200555.pdfI am using the radio with ppi to transmit as well as receive packets through the same code. I need to record the time events.I have enabled a special button functionality to distinguish between the transmit and receive events.

I am attaching the mainc file under. I have thoroughly checked the address, and other values that i put in the packet. If you could let me know what could be the problem behind my device named "Raghav" not being showed on sniffer, even though the code is built and run properly. I even try to set break point at timer init and commented out 'app button is pushed' function but no change occurs.

I am attaching my mainc file .

Parents
  • i am using radio with ppi functionality, since i am using harware timers to capture events and do need CPU intervention. i would be seeing the packet receive times in wireshark corresponding to my device. That would be advertising ind packets. Then i ought to see the toggle event times on the analyser. I am using the button functionality as u see in my code to distinguish between transmit and receive events.

    I am just using wireshark and analyser for verification. Ofcourse i can't rely on their time samples, as i don't know which clocks they are using. But i would be using Segger RTT viewer to communicate with my board and then Pynrfjprg interface to transfer the data from the board to the PC. i AM USING THE STANDARD NRF Bluetooth smart sniffer from nrf51 downloads

    Earlier the sniffer was running okay at the initial stages and my device showed up, but lately i had to modify the functionality to load the timestamp in the packet prior to it being sent as well as calling the function app button is pushed in the main function which represents a transmit event. So i think the address and the payload values i loaded in the mesh demo packet are same as earlier, but now after everything seems okay in the code, i can't see my device. If u could analyse the problem and get back to me.

Reply
  • i am using radio with ppi functionality, since i am using harware timers to capture events and do need CPU intervention. i would be seeing the packet receive times in wireshark corresponding to my device. That would be advertising ind packets. Then i ought to see the toggle event times on the analyser. I am using the button functionality as u see in my code to distinguish between transmit and receive events.

    I am just using wireshark and analyser for verification. Ofcourse i can't rely on their time samples, as i don't know which clocks they are using. But i would be using Segger RTT viewer to communicate with my board and then Pynrfjprg interface to transfer the data from the board to the PC. i AM USING THE STANDARD NRF Bluetooth smart sniffer from nrf51 downloads

    Earlier the sniffer was running okay at the initial stages and my device showed up, but lately i had to modify the functionality to load the timestamp in the packet prior to it being sent as well as calling the function app button is pushed in the main function which represents a transmit event. So i think the address and the payload values i loaded in the mesh demo packet are same as earlier, but now after everything seems okay in the code, i can't see my device. If u could analyse the problem and get back to me.

Children
No Data
Related