PACKET-SNIFFER-2 — SmartRF Packet Sniffer 2
the number of RSSI and LQI, for example are different from the number after "save " it and restore it.
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.
the number of RSSI and LQI, for example are different from the number after "save " it and restore it.
Hello Higuchi,
What CC2X3X device and hardware platform are you using? Can you share your sniffer log as well as before/after pictures of saving the sniffer session? Of the values listed, -70 makes more sense given that a typical Zigbee application has a threshold of -80 so I would not expect packets with RSSI as low as -90 to be processed by the sniffer. You can set up a test using Smart RF Studio to confirm the expected RSSI with a Continuous RX test. I further recommend reviewing the Zigbee Packet Sniffer FAQ E2E post for updated Zigbee sniffing solutions using Simplelink CC13XX/CC26XX devices.
Regards,
Ryan
Ryan Brown1 You can easily reproduce this issue. Just using CC2531EMK with Packet sniffer to sniff and save log. Before you close packet sniffer, remember the LQI in first packet and restart packet sniffer to open previous saved log to see the LQI in first packet which would be different from what you remembered.
Thanks YK. Based on my observations, the original LQI values convert to much more realistic RSSI numbers which are also more aligned with the LQI/RSSI readings I am recording using Ubiqua. This would lead me to believe that the restored values are incorrect. Unfortunately, Packet Sniffer has not been further developed for several years and there are no TI employees who continue to support this software solution. This is why I recommend that Ubiqua or a SimpleLink sniffer be used instead.
Regards,
Ryan
Ryan Brown1Yes, I understand TI no longer maintains packet sniffer and I always use Packet sniffer 2 with wireshark or Ubiqua as Zigbee sniffer. Just help to clarify this issue and don’t expect it to be fixed.