experiment_usrp
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
experiment_usrp [2014/04/28 14:35] – bguillon | experiment_usrp [2016/05/18 17:09] – [Providing USRP programs] lbeseme | ||
---|---|---|---|
Line 1: | Line 1: | ||
======= Experimenting with the USRPs ======= | ======= Experimenting with the USRPs ======= | ||
- | (WORK IN PROGRESS) | + | ===== Providing USRP programs ===== |
- | Launching an experiment on the USRP board requires the following steps: | + | In CorteXlab, USRPs are programmed using the [[http:// |
- | | + | |
- | - Create a //Task// as a directory | + | Programming a USRP with GNURadio |
- | - Activate | + | to the [[http:// |
+ | |||
+ | For instance, in the '' | ||
< | < | ||
- | username@srvairlock: | + | $ benchmark_tx.py --antenna=" |
</ | </ | ||
+ | | ||
+ | The script called as the entry point could be anything, it is up to the user to decide what, the parameters, etc. The only constraint is that it should be able to run with the GNURadio toolchain deployed on CorteXlab. If the user wants to add more packages or libraries, he should put the files in the task directory upon creation of the task. | ||
- | This will result | + | For instance, |
- | - Launch | + | |
+ | Again, using the '' | ||
< | < | ||
- | username@srvairlock: | + | $ benchmark_rx.py --antenna=" |
</ | </ | ||
- | - Analyze the results | ||
- | |||
- | ====== Create a Task ====== | ||
- | |||
- | Creating a task for an experiment amounts in: | ||
- | - providing the programs targeted to each USRPs included in the experiment (explained in the [[experiment_usrp# | ||
- | - providing a '' | ||
- | |||
- | |||
- | ===== Providing USRP programs ===== | ||
- | |||
- | In CortexLab, USRP are programmed using the [[http:// | ||
- | |||
- | Programming a USRP with GnuRadio is not an easy task, the user should be familiar with that, and should refer | ||
- | to the [[http:// | ||
- | $ benchmark_tx.py --antenna=" | ||
| | ||
- | The command could be anything, it is up to the user to decide the name of the script, its parameters etc. The only constraints is that it should be able to run with the GnuRadio packages present on CorteXlab. It the user wants to add more packages or libraries, he should put the files in the Task directory. For instance, on the '' | + | /!\ The RX2 antenna |
- | + | ||
- | Again, using the '' | + | |
- | $ benchmark_rx.py --antenna=" | + | |
- | + | ||
- | Once the programs to be launched on each USRPs are set up, remains to indicate the time duration of the experiment. Minus will stop the experiment after this time duration, | + | |
- | ===== Providing a scenario file ===== | + | |
- | The scenario file is the Minus script that indicates to Minus which program will be launch on which USRPs and how long the experiment will last. For each node (i.e. each usrp), it should indicate: | + | |
- | - a command (or //entry//) which is the program executed on the PC connected to the USRP | + | |
- | - a commande line option (or // | + | |
- | - an exit script (optional) which is executed at the end of the experiment | + | |
- | + | ||
- | In addition with these information, | + | |
- | Below is a simple example used for the '' | + | |
- | + | ||
- | # Example scenario description file | + | |
- | desc base scenario for CorteXlab | + | |
- | # | + | |
- | # Experiment maximum duration | + | |
- | durat 3 | + | |
- | # | + | |
- | # Node list | + | |
- | # | + | |
- | node2: | + | |
- | entry benchmark_rx.py | + | |
- | | + | |
- | exit none | + | |
- | node1: | + | |
- | entry benchmark_tx.py | + | |
- | | + | |
- | exit none | + | |
- | + | ||
- | + | ||
- | + | ||
- | ====== Launch a Task ====== | + | |
- | + | ||
- | ======= Analyze the results ====== | + |
experiment_usrp.txt · Last modified: 2023/12/11 14:02 by cmorin