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.

  • Resolved

LAUNCHXL-CC2650: SmartRF Sniffer Agent - Capture Filter- does not work as expected

Intellectual 310 points

Replies: 5

Views: 110

Part Number: LAUNCHXL-CC2650

Hello all,
i want to test the Capture Filter-function of the SmartRF Sniffer Agent (from PacketSniffer 2). I selected an example-filter and enabled the Filter, but as soon as i close the Capture Filter-Window, the Filter is disabled again.
I'm using Sniffer Agent v1.7.0. Buidling of the Filter code is successful.


Anybody tested this feature successfully and can tell me what step  i'm missing here?

Thanks al lot for help,
best regards,
Albert

  • Genius 12800 points
  • In reply to FI:

    yes, i know this documentation. To be able to mark the checkbox "Enable Capture Filtering", the capture device must be stopped before (otherwise the checkbox is shown grayed out). So i stop the capture and then select Options->Capture Filter->activate the checkbox.
    To be able to start the capture device again, the whole "Capture Filter"-window must be closed before... so i close this window...press Start All.... and then i would expect that my filter is applied (but no matter my filter expression is "true" or "false"), i always can see that ALL packets are forwarded to wireshark.

    When i want to examine if i unintentionally forgot to mark the checkbox by re-opening the Capture Filter window, i see that the checkbox IS ALWAYS NOT MARKED, even i'm sure that i had activated it before.... strange... for me it seems that the state of the checkbox is not saved in the GUI... and the filter always remains deactivated....

    btw, the online documentation is based on version 1.8.0 (software-dl.ti.com/.../revision_history.html), but this is not yet available at http://www.ti.com/tool/PACKET-SNIFFER.

    So please can you update the download for Packet Sniffer 2 from 1.7.0 -> 1.8.0. Maybe the new version has fixed this issue.
    Thank you,
    best regards Albert

  • In reply to a.poetsch:

    Hello a.poetsch,

    PACKET-SNIFFER-2 v1.8.0 can be accessed through the tool download page: http://www.ti.com/tool/download/PACKET-SNIFFER-2

    Can you please evaluate with this software version and confirm whether you are still experiencing the same issues?

    Regards,
    Ryan

    To better aid the community, please click on the "This Resolved my issue" button whenever a post answers your question!

  • In reply to Ryan Brown1:

    Hello Ryan,

    Thanks for your response. The activation (enable) of the capture filter now works in  the current PacketSniffer2-Agent Version v1.8.0.

    The only thing that is not quite clear to me is the value of the "data.Length"-field: It looks like it doesn't match the "Payload Length" field inside the "TI Radio Packet Info"-dissector in Wireshark (see screenshot).

    For example: the following filter

    (data.Length != 51)

    only passes frames which are displayed in Wireshark under TI Radio Packet Info-Payload length with 48 Bytes. Why?

  • In reply to a.poetsch:

    Hi,

    The reason is that the filter looks at the data message in an interal format, as it is read out from the RF Core. The message length includes a length byte, a status byte, RSSI byte, and two CRC bytes.I think that is the reason why the data length in the filter does not match exactly the payload length displayed in Wireshark.

    Regards,

    Bjørn

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.