u5isniffer-win-0.0.1
| index.html .............................. this file
+---images
| *.png ............................... documentation graphics
|
+---CDM 2.04.06 ............................. FTDI driver with modified inf files
| ftdibus.inf
| ftdiport.inf
| ...
|
+---firmware
| sniffer_psk*.hex .................... Atmel ATAVRRZ541
| sniffer_stb*.hex .................... DE Sensor Terminal Board
|
+---sniffer
+---bin
| ieee802154.exe .................. uracoli-wireshark bridge script
| ... (after py2exe conversion)
+---src
ieee802154.py ................... pythons source code
... (requires packages pyserial and pywin32)
2.1. Start the uracoli-wireshark bridge script
The uracoli-wireshark bridge script will be started by clicking on the program icon ieee802154.exe in the folder sniffer. Since there are no command line options passed to the programm, you get prompted to enter the serial port, where the sniffer plattform is connected. You can get this information from the hardware manager. The program 802154.{py,exe} runs in a text window, where you can type commands. Type help to view a list of the available commands.
Command line options
The program ieee802154.{py,exe} can be started with the following options.
-p PORT Name of the serial port where the sniffer plattform
is connected, e.g. /dev/ttyUSB0 or COM1.
-r CAPFILE Name of a capture file which is read @c mytrace.dat.
-i PIPE Name of the named pipe.
On a Linux system, PIPE can be a absolut path name, e.g.
/tmp/ieee802154. On a Windows system PIPE is a name in a
special pipe directory, e.g. foo maps to \\.\pipe\foo.
[ieee802154]
-c CHAN IEEE802.15.4 channel number
-R RATE IEEE802.15.4 data rate
-v increase verbose level
-h show help and exit.
-V print version and exit.
Note:
* -r and -p can be used only exclusively,
* -c works only with -p.
Interactive Commands
reopen - reopens the named pipe and places a pcap header,
so that wireshark can reconnect.
chan <n> - set new channel to sniff.
rate <r> - set IEEE 802.15.4 data rate (e.g. BPSK20, OQPSK100, ...)
devrst - reinitialize the sniffer device
debug - start python debugger
info - show status of sniffer DEVIN
quit - end session and terminate all threads
help - show command help
2.2. Start wireshark
If wireshark is running, select in the menu Capture/Options or just type Ctrl-K, enter \\.\pipe\ieee802154 in the Interface field and confirm the dialog with START
Alternatively you can create a batch file/shell script, which starts wireshark directly with the option -i ieee802154.
Now capture can be started by clicking this icon:
2.3. Closing and Reopening a Session
If you want to save a packet capture logfile, you have to close the current session by selecting "Capture→Stop" or "Ctrl-E". After "Capture→Start", the wireshark window stays gray shaded. Switch to the ieee802154.{exe,py} window and type reopen. This will place the data of a pcap file header in the named pipe and will allow wireshark to proceed with the frame capturing.
2.4. Changing Channels and Modulation in a Capture Session
In the ieee802154.{exe,py} you can change channel (chan) and rate/modulation (rate) of the transceiver at any time without restarting the wireshark session. NOTE: In the wireshark logfile there is no information about the channel or rate/modulation setting stored.