experiment_usrp
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
experiment_usrp [2014/04/10 10:26] – bguillon | experiment_usrp [2023/12/11 14:02] (current) – [Providing USRP programs] cmorin | ||
---|---|---|---|
Line 1: | Line 1: | ||
======= Experimenting with the USRPs ======= | ======= Experimenting with the USRPs ======= | ||
- | (WORK IN PROGRESS) | ||
- | |||
- | Launching an experiment on the USRP board requires the following steps: | ||
- | - Reserve a number of USRP nodes (not implemented yet) | ||
- | - Create a //Task// as a directory (say '' | ||
- | - Activate the task creation in Minus: | ||
- | $ create_task taskFolder | ||
- | This will result in the creation of a file '' | ||
- | - Launch the task with minus: | ||
- | $ submit taskFolder.job | ||
- | - 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 ===== | ===== Providing USRP programs ===== | ||
- | In CortexLab, USRP are programmed using the [[http:// | + | In CorteXlab, USRPs are programmed using the [[http:// |
- | Programming a USRP with GnuRadio | + | Programming a USRP with GNURadio |
- | to the [[http:// | + | 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 '' | + | |
- | Again, using the '' | + | For instance, in the '' |
- | $ benchmark_rx.py --antenna=" | + | < |
+ | $ benchmark_tx.py --antenna=" | ||
+ | </ | ||
| | ||
- | Once the programs to be launched on each USRPs are set up, remains | + | 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 |
- | ===== Providing a scenario file ===== | + | |
- | The scenario file is the Minus script | + | |
- | - a command (or //entry//) which is the program executed | + | |
- | - a commande line option (or // | + | |
- | - an exit script (optional) which is executed at the end of the experiment | + | |
- | In addition with these information, the scenario file should contain the description of the experiment and a duration in minute. The exact syntax of the scenario description file is presented [[http:// | + | For instance, in the '' |
- | Below is a simple example used for the '' | + | |
- | # Example scenario description file | + | Again, using the '' |
- | desc base scenario for CorteXlab | + | < |
- | # | + | $ benchmark_rx.py --antenna=" |
- | # Experiment maximum duration | + | </ |
- | durat 3 | + | |
- | # | + | |
- | # Node list | + | |
- | # | + | |
- | node2: | + | |
- | | + | |
- | | + | |
- | exit none | + | |
- | | + | |
- | entry benchmark_tx.py | + | |
- | | + | |
- | exit none | + | |
- | + | ||
- | + | ||
- | + | ||
- | ====== Launch a Task ====== | + | |
- | + | ||
- | ======= Analyze the results ====== | + |
experiment_usrp.1397118408.txt.gz · Last modified: 2014/05/21 15:45 (external edit)