• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 17 subscribers
  • Views 426 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SmartRF Packet Sniffer Issue

mx_de
Prodigy 220 points

Hi All,

 I am using the SmartRF Packet Sniffer in conjunction with the CC1111 USB Dongle to monitor communication between CC1111 and CC430 everything was ok, I saved the PSD file of the complete communication and I was able to open it again and look at all the packets that were sent during that communication, but today, I tried opening the file and the packets show FCS = ERR and 2 Bytes of the payload are missing on all packets. How could that have happened? Isn't the PSD a static file which is just read by the Sniffer and print on screen? how can it change from 1 day to another?, I also tried opening other files which I had with packets, they all have the same problem, bytes missing from the payload and the ERR on the checksum.

 What could I be doing wrong? As I said I've opened all this files before and haven't had any problems, I didn't change the Packet Sniffer version, I loaded the same Radio Settings used to capture the packets (in case it was needed). Any shed of light you can bring?

  • 0
    Prodigy 220 points

    Hi,

     Just an update, the problem is gone after I started sniffing packets for communication, then I stopped the sniffer and tried again to open the saved PSD file and it shows correctly.

     The issue is still that, why before starting to sniff packets is the file not display correctly?.

    Regards,

       JC

  • 0 in reply to mx_de
    Prodigy 120 points

    Hi,

    I was about to ask the exact same question. Thanks to your answer I am now able to read saved data so thank you. But it would be great that TI does something about it.

    Regards,

    G.

     

  • 0 in reply to Gary1
    TI__Expert 4870 points

    Hi,

    The problem should have been solved in the latest version of the packet sniffer (2.12.3).
    The version used is not mentioned, but in earlier versions there was a problem that the packet sniffer didn't know how the packets in the PSD file was captured. The length field depend on the device. Some devices include the 2 status bytes (FCS) in the length field and others don't. It is correct that the PSD file is a static file, but unfortunately it doesn't contain any information about the capturing device (We have been thinking about changing this in the future). When you open the packet sniffer window and try to open a PSD file without first starting the sniffer, the sniffer would use a default value of the capturing device. This might not be the correct one and the display of the packet could be with 2 bytes less than what was originally saved in the PSD file.
    In the latest version of the packet sniffer you will be asked to specify the capturing device when you open a PSD file. See screen shot:

    Regards,

    Øyvind

  • 0 in reply to Øyvind K
    Prodigy 120 points

    Hi,

    Thank you for your answer. I was using version 2.12.0, I'll try the latest. I have one more question, I'd like to change the SYNC word but I dit not find where I can do it (in radio settings tab).

    Thanks again,

    G.