CorteXlab's Wiki

User Tools

Site Tools

Trace:
from_gnuradio_to_cortxlab_pico

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
from_gnuradio_to_cortxlab_pico [2016/12/13 10:12] – [tx_ofdm.grc] onicolasfrom_gnuradio_to_cortxlab_pico [2017/11/15 16:19] (current) – [Create the scenario] onicolas
Line 1: Line 1:
-# From GNU Radio to CorteXlab (Using PicoSDRs)+# From A to Z: GNU Radio with CorteXlab using PicoSDRs
  
 This tutorial goes through the process of executing an experiment on CorteXlab starting from an empty project on your computer (and is quite similar to [[from_gnuradio_to_cortxlab|this tutorial]], but this time we are using PicoSDRs). This tutorial goes through the process of executing an experiment on CorteXlab starting from an empty project on your computer (and is quite similar to [[from_gnuradio_to_cortxlab|this tutorial]], but this time we are using PicoSDRs).
  
-For practical purposes, we will use some GnuRadio examples instead of starting from a clean sheet, but it's exactly the same as if you had your own project you wanted to run on CorteXlab.+For practical purposes, we will use some GNU Radio examples instead of starting from a clean sheet, but it's exactly the same as if you had your own project you wanted to run on CorteXlab.
  
 ##Setup ##Setup
Line 138: Line 138:
  
 Then we need the same mandatory blocks as with tx\_ofdm, which are ''Carrier Perseus Board'', ''Radio420 RX'', ''Radio420 TX'' and three ''Custom Register''. We also use the same parameters as in [[#tx_ofdmgrc|tx_ofmd]]. (Pro tips : you can copy/paste a block from one graph to another). Then we need the same mandatory blocks as with tx\_ofdm, which are ''Carrier Perseus Board'', ''Radio420 RX'', ''Radio420 TX'' and three ''Custom Register''. We also use the same parameters as in [[#tx_ofdmgrc|tx_ofmd]]. (Pro tips : you can copy/paste a block from one graph to another).
- + 
 +We need to modify the frequency on the Tx block so as not to interfere with the transmitting node: 
 + 
 +* Radio420 RX (to set up RX radio front end)   
 +-> **TX frequency** : 2590000000   
 + 
 The next thing to do is to replace the encoding and transmission parts to put a ''RTDEX Source'' block instead. The parameters of this block are : The next thing to do is to replace the encoding and transmission parts to put a ''RTDEX Source'' block instead. The parameters of this block are :
 -> **Target ID** : nutaq\_carrier\_perseus\_0   -> **Target ID** : nutaq\_carrier\_perseus\_0  
Line 163: Line 169:
 ## Create the scenario ## Create the scenario
  
-The experiment description file called `scenario.desc` will be looked for and read by the experiment scheduler to get which nodes and what software will be used during the experiment. It also gives the necessary startup scripts and parameters that the user provides for his experiment.+The experiment description file called `scenario.yaml` will be looked for and read by the experiment scheduler to get which nodes and what software will be used during the experiment. It also gives the necessary startup scripts and parameters that the user provides for his experiment.
  
-Here is a simple example of a `scenario.desc` file:+Here is a simple example of a `scenario.yaml` file:
 <code> <code>
 # Example scenario description file # Example scenario description file
Line 174: Line 180:
 # Scenario textual description # Scenario textual description
 #   simple string (a one liner) #   simple string (a one liner)
-desc OFDM tx-rx example scenario for CorteXlab+description: OFDM tx-rx example scenario for CorteXlab
  
 # Experiment maximum duration # Experiment maximum duration
 #   Time after which the experiment is forced to stop #   Time after which the experiment is forced to stop
-#   integer (minutes) +#   integer (seconds) 
-durat 2+duration: 120
  
 # Node list # Node list
Line 185: Line 191:
 #   format: #   format:
 # #
-#   (machine): +#   nodes: 
-#   entry (entry point script relative to the task root) +#     (machine): 
-#   exit (exit point script relative to the task root. Use "none" for none) +#       command: (entry point script relative to the task root)
- +
-node29: +
-   entry rx_ofdm.py+
  
-node31: +nodes: 
-   entry tx_ofdm.py+  node29: 
 +    command: ./rx_ofdm.py 
 +  node31: 
 +    command: ./tx_ofdm.py
 </code> </code>
  
-This file uses its own syntax and is self-documented. Here the params line is mandatory even if it is not used (This will be changed in a future version). Adapt this example to suit your needs.+This file uses the yaml syntax and is self-documented. Adapt this example to suit your needs.
  
  
Line 207: Line 213:
 │   ├── tx_ofdm.py │   ├── tx_ofdm.py
 │   ├── rx_ofdm.py │   ├── rx_ofdm.py
-│   ├── scenario.desc+│   ├── scenario.yaml
 │   ├── tx_ofdm.grc │   ├── tx_ofdm.grc
 │   └── rx_ofdm.grc │   └── rx_ofdm.grc
Line 270: Line 276:
 <code> <code>
 you@srvairlock:~$ minus testbed status you@srvairlock:~$ minus testbed status
-Testbed status: +num total tasks:   2540 
-ID count so far: 6 +num tasks waiting: 0 
-Number of awaiting jobs: 0 +num tasks running: 0 
-ID of the running job: None (None means server is idle)+tasks currently running: 
 +  (none)
 </code> </code>
  
Line 301: Line 308:
 you@srvairlock:~/results/task_15$ cd node29 you@srvairlock:~/results/task_15$ cd node29
 you@srvairlock:~/results/task_15/node29$ ls you@srvairlock:~/results/task_15/node29$ ls
-rx_ofdm.grc  scenario.desc  stdout.txt   tx_ofdm.py+rx_ofdm.grc  scenario.yaml  stdout.txt   tx_ofdm.py
 rx_ofdm.py   stderr.txt     tx_ofdm.grc rx_ofdm.py   stderr.txt     tx_ofdm.grc
 </code> </code>
from_gnuradio_to_cortxlab_pico.1481620329.txt.gz · Last modified: 2016/12/13 10:12 by onicolas
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki