Compiler/LAUNCHXL-CC1310: packet sniffer

the pre-built file is  with rate of 50kbps while I am using 9.6kbs. also the preamble is different. I need to listen to 433.6Mhz each channel is 0.15Mhz offset with the image of 433 it not possible. maybe I am missing something here please advice.  

I am trying to configure the settings in rf studio and compile them with the sniffing project hoping to get same results I can see in rf studio packet rx.

I had small progress after reading in the manual I should remove the predefined symbol called FW_ID. now I am not getting the error message from TiWsPc2 but still cant see incoming messages. device configuration dialog box format is different then when using the pre-built images.

yes, I have removed the FW_ID symbol. now the TiWsPc2 error message is gone and I can see the device when clicking the device configuration button.

with the sniffer  supplied image I was able to set channel in the device configuration dialog box and the calculated frequency was seen in a read only text box.

with my settings I can not pick the channel 0-6 in the device configuration dialog box,  I need to enter the frequency manually into the text box.

it seems that even if I write down the exact frequency which another device is transmitting in the same time I can not see the incoming counter increments. ( for reference with RF studio same settings with same setup works fine and I can see the transmitter messages in the packet rx dialog box   )

I assume that it means procedure I have done is not complete. please advice.

Roy

You can sniff using SmartRF Studio @433.6MHz, but when using the sniffer firmware built with the same settings you cannot? I ran a quick test with the 868MHz band and was able to sniff using the custom sniffer without an issue. This is what I did:\

1. imported sniffer_fw_15_4_g project into CCS (by default the smartrf studio setting are for the 868MHz band)
2. undefined FW_ID from predefined symbols
3. built project and flashed
4. in TiWsPc2 I selected my sniffer and manually entered the frequency of my device on channel 1 (863.125MHz).
5. Start.

I was able to see packets coming in. Can you confirm your smartrf studio settings are correct? Also maybe confirm the device is sending on the right frequency by setting up another launchpad in packet rx mode in smartrf studio with the same settings.

Hi, 

I am able to see packet count in the tiwspc2 now.

next step is to see them in the wireshark app. I am following the manual but having problems.

I have installed wireshark version 2.0.15 as you requested to be in old version 2.0.x. do I need to install wcap with wireshark installation ?

I have added the  -i\\.pipe\tiwspc_data -k to the shortcut.

when I run wireshark and try to start i get a message the "system cannot find the device specified".

see attached file.

please advice ?

please advice.

Roy,

You can select how you want data to be outputted by selecting Data->Data Out in the TiWsPc2 menu bar. You can change pipe setting by going to Options->Pipe Config. If you are using the packet sniffer with the SimpleLink CC13x0 SDK v1.40 then Wireshark v2.2.x is required.

I have tried using both wireshark version 2.0.x and 2.2.x without success.

problem origin seems to be that even when pipe is configured it cannot be found by wireshark.

I have downloaded a tool called "process explorer". this tool can show what pipe were created by a specific process.

it seems the even after i have configured the pipe and clicked "start all" pipe is not created.

can you tell what can be the reason ? can you consult with someone ? ( btw, I also tried running TiPcWs2.exe as administrator)

Hi Guys,

Not sure if you have noted.

There is something wrong in the guide. It should be 

" -i\\.\pipe\tiwspc_data -k ", instead of

"-i\\.pipe\tiwspc_data –k".

If you look carefully, there is a '\' missing.

Thanks Yan,

This comment solved the issue. now I am able to see incoming messages in the wireshark.

After I add the ti plugin ti802154ge-x32-2x.dll in to the plugin folder and try to run I get the following error. I am trying with wireshark version 2.0.15 with 32 and 64 bit with no success. getting same message.

when I remove the ti plugin from folder wireshark runs fine and I can see the messages from the sniffer.

en using wireshark version 2.0.15 I get the following message:

Hi Roy,

My setup here is wireshark 2.4.2 (latest version, 64bit version), and windows 10 64bit version PC.

The guide mentioned wireshark version should be 2.4.x version. Maybe your 2.0.x version is too old.

You can try download the latest wireshark, uninstall the old version entirely, meanwhile also uninstall smartrf sniffer 2, make a clean new installation of the latest wierlshark and smartrf sniffer 2. At least that's what i did, and it worked.

Hello,

I have installed the "simplelink_cc13x0_sdk_1_50_00_08" and under "C:\ti\simplelink_cc13x0_sdk_1_50_00_08\tools\ti154stack"  the folder "TiWsPc2" seems to be missing.

Where can I find the sniffer programming file as I would like to use one of the CC1310 Launchpad boards to evaluate the Collector/Sensor example in FH mode.

Thank you,
Admir

You should download and install PACKET-SNIFFER-2. You can find related files under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\SmartRF Packet Sniffer 2 after you install PACKET-SNIFFER-2.

hi Admir,

"TiWsPc2.exe" is actually "sniffer_agent.exe".

There is no longer "TiWsPc2.exe" in1_50 version SDK, it only exists in old version SDK.

You need to download & install packet sniffer 2 from ti.com and you will get your "sniffer_agent.exe".

Hello guys,

Thank you both for pointing me in the right direction.

I have installed packet sniffer 2, flashed the Launchpad with "sniffer_fw_slr_5kbps_868_915.hex", as I am using the Collector/Sensor example in a long range mode.

The sniffer agent recognizes the device and I have configured Wireshark to use TI 802.15.4GE protocol.

Everything looks great but I don't see any data captured in my Wireshark. It just says 0 packets captured.

My further 4 questions:

1. Since I have only 2 Launchpad boards, I am using one as the collector and the other one as a sniffer. Is this a valid setup, to see collector data only over the air in wireshark, or do I need a  third board that runs a sensor as well?

2. Default Collector/Sensor example setting is I think using the encryption security: in config.h ->

/*! Security Enable - set to true to turn on security */

define CONFIG_SECURE true

The Wireshark section of the user guide says "If you use secured packets, add a decryption key and static address pairings (for pairing short address and PAN-ID with long addresses for decryption)"

What and where is my decryption key and  PAN-ID with long addresses located?

Note: I tried setting the CONFIG_SECURE to false, but had same results: no packed capture in Wireshark.

3. In Sniffer Agent - Device Configuration, I am not sure which Ch# to select?

I thought when in FH mode, the DH1CF function would jump over all 129 channels with example default settings below:

*/

#define CONFIG_FH_CHANNEL_MASK { 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, \

0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, \

0xFF, 0xFF, 0xFF, 0xFF, 0xFF }

I am sorry for so many questions, I am just still new to the stack.15.4.

4. I also get this message after about 10-15sec of running Wireshark:

The capture session on "\\.\pipe\tiwspc_data" timed out during pipe open: The semaphore timeout period has expired.
 (error 121).

I assume that's because of the no captured packets but not sure 100%.

Thank you again kindly for any response.

Admir 

Hey Admir,

I recommend starting a new thread next time. To answer your questions:

1. Yes, you will need at least one sensor device to see traffic OTA in non-beacon mode. If you would like to just confirm your sniffer setup is working you can put the collector device into beacon mode (set CONFIG_MAC_BEACON_ORDER <14 and set CONFIG_MAC_SUPERFRAME_ORDER = CONFIG_MAC_BEACON_ORDER). Or you can flash a sensor device in non-beacon mode. I suggest reading the TI 15.4-Stack Users guide on the difference between the two modes. In general non-beacon mode is asynchronous and sensor devices initiate communication.
2. The decryption key is KEY_TABLE_DEFAULT_KEY in config.h, PAN ID is also set here (0xFFFF is wildcard meaning it will assign itself the lowest available value, usually 0x1).
3. I recommend reading the users guide on channel selection
4. Yes, this is because no packets are sent over the pipe. This will go away after packets are sniffed.

Hello Brocklobsta,

can we use same setup for sniffing Contiki packets.Please reply asap as my project is in critical phase.

Thank you

Rohit Sawa.