Changes between Version 2 and Version 3 of Tutorials/Wireless/Outdoor Spectrum Usage

Timestamp:

Jun 4, 2020, 5:37:22 PM (4 years ago)

Author:

nilanjan

Comment:

—

Tutorials/Wireless/Outdoor Spectrum Usage

@@ -102 +102 @@
 
  Keep track of these two terminals. The sdr application will output text as it detected the radios on both transmitter and receiver. When both radios are ready, output similar to the following is shown
-{{{
+{{{#!shell-session
 :
 Number mboards        = 1
@@ -165 +165 @@
 
  On the transmit side the output should have rows of ''INFO'' statements similar to the following.
-{{{
+{{{#!shell-session
 :
 [INFO] [tx_data_link_0]   [sent]   seq_num: 62  pkt_len: 29
@@ -182 +182 @@
         
  On the receive side a similar output is expected
-{{{
+{{{#!shell-session
 :
 [INFO] [rx_data_link_0]   [rcvd]  pkt: OK  seq_num: 55  pkt_len: 18  corr_strength: 18131.3
@@ -204 +204 @@
 {{{#!shell-session
 user@console:~$ curl "am1.cosmos-lab.org:5054/rf_control/set_tx_path?node=sdr2-s3-lg1.bed.cosmos-lab.org&rf_port=0&power_amp=off"
+<response status="OK">
+  <message>OK</message>
+</response>
 }}}
 
  11. Execute the run script again and verify that no packets are received. The transmitters output will show the radio trying to send packets but since the power amplifier is turned on nothing is actually sent over the air. On the receiving end, the radio will still listen for packets however the summary should show 0 packets received.
-{{{
+{{{#!shell-session
 :
 [INFO] [rx_data_link_0] Receive complete - summary:
@@ -219 +222 @@
 ====  Run script details ====
  View the run_data_script.sh file. A python script is used to remotely configure the sdr application on both the receiving and transmitting side from the console. 
-{{{#!shell-session
+{{{#!shell
 user@console:~$ cat run_data_script.sh
+## DESCRIPTION
+##  Performs one way data transfer over the air using x310 USRPS.
+##  sdrapp daemon must be running on the nodes specified under CONFIGURABLES.
+
+## Python is used to script the sequence of commands issued to the sdrapp daemon.
+## Usage:
+##   python rc.py <MACHINE_NAME> <PORT> <sdrapp sub-command>
+##
+##     <MACHINE_NAME> is hostname of machine running sdrapp daemon
+##     <PORT>         command listening port
+## Format of python sub-commands are described below.
+## Sub-commands have a companion handler in the sdrapp daemon.
+
+## Note: This script can be run multiple times while sdrapp is running.
+## However this is subject to the following known gotchas:
+##  1) if the <rate> parameter is changed in the set up section
+##     then the sdrapp must be restarted.
+##  2) when rerunning this script the running handlers in sdrapp
+##     must finish and exit first.
+
+
 }}}
 
  The ''CONFIGURABLES'' section must have the target node variables pointing at the appropriate   devices:
-{{{
+{{{#!shell
 ## CONFIGURABLES
 export TXNODE=sdr2-s3-lg1.bed.cosmos-lab.org
@@ -231 +255 @@
 
  The radio parameters are set up with the following lines.
-{{{
+{{{#!shell
 ## SET UP RADIO PORTION HERE
 ##  Script is set up for x310 which has 2 daughter cards hence 2 channels: {0,1}
@@ -254 +278 @@
 
  After the set up is done, the sdr applications begin streaming data. The receiving end is started first with the specified runtime of 20 seconds. At the same time the transmitting end starts sending packets for 20 seconds at intervals of 250 milliseconds.
-{{{
+{{{#!shell
 ## BEGIN data transfer
 ##  Invoke receive handler
@@ -265 +289 @@
 python rc.py $TXNODE 5180 "txsig_data 20000 250"
 
-}}}
-
-
-In the [next part of this tutorial] we'll add onto the receiving sdr application and recording measured data into InfluxDb.
-
+echo "DONE!"
+}}}
+
+ After the run script initiates the receive and transmitter handlers on the sdr applications, the script will exit out back to the console but the sdr application handlers should be running for the specified run times. This script can be rerun only after the handlers exit.
+
+
+In the [next part of this tutorial] we'll edit the the receiving sdr application to store measured data to a remote network Influx database.
+