Changes between Version 4 and Version 5 of ALOEOFDMDemo

Timestamp:

08/06/12 18:22:33 (12 years ago)

Author:

ismael (IP: 90.163.39.25)

Comment:

--

ALOEOFDMDemo

@@ -11 +11 @@
  * Run-time reconfiguration
  * '''E2E Latency: 4 ms''' (constant and non-random)
- * Distributed processing (tested with 2 processors and GigaEthernet)
+ * Distributed processing (tested with 2 processors and Gigabit Ethernet)
  * GUI: signal visualization, execution time monitoring, etc.
+
+This version is unstable. Therefore, please don't hesitate to send your questions or comments to our [http://groups.google.com/group/flexnets Maillist]. 
 
 == Download and install ==
@@ -50 +52 @@
 sudo runcf -t NOFCORES 1000000
 }}}
-replacing NOFCORES with the number of cores in your processor. For example, in a quad-core you would type:
+replacing NOFCORES with the number of cores in your processor (the second parameter tells the MAC-TEST to run one million MAC operations). For example, in a quad-core, type
 {{{
 sudo runcf -t 4 1000000
 }}}
 
-And you will see something like this:
+and you get:
 
 {{{
@@ -93 +95 @@
 
 == USRP ==
-If the [http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki/ UHD] driver is installed before running ALOE's configure script, the option 
+If the [http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki/ UHD] driver is installed before running ALOE's configure script, the OFDM waveform will send the samples to the USRP. In the configuration file '''/usr/local/etc/platform.conf''' (need root privileges) you'll see something like this:
+
 {{{
-dac=uhd
+## DAC SELECT. Use dac_tx/dac_rx modules to send/recv samples to dac's.
+# Available dacs:
+#       x5-400: use the pci-e x5-400 daughterboard from innovation logic
+#       soundcard: use jack libraries to access soundcard's dac
+#       udh: use Universal Hardware Driver to access USRP
+#       none: disable dac   
+
+dac {
+        name=none
+        dac_drives_clock=no
+        #Select dac configuration file. Read dac's documentation.
+        cfg_dac=usrp.conf
+}
+
 }}}
-in '''/usr/local/etc/platform.conf''' file allows ALOE to send samples to the USRP. 
+Just change the field '''name=none''' by
+{{{
+name=uhd
+}}}
 
-Now run the OFDM-128 waveform as described in the previous section. The device sampling frequency is automatically configured by ALOE. Since not all devices can work with the same sampling frequencies, the execution period (time-slot) can differ slightly from one set-up to another.
+Now you need to choose the transmit center frequency, which depends on your device. Edit the file '''/usr/local/etc/usrp.conf''' and look for the section
+{{{
+tx {
+        samp_freq=1777778
+        freq=2400000000
+        gain=30.0
+        bw=0.0
+        blocksize=960
+}
+}}}
+Only the '''freq''' and '''gain''' options needs to be configured. The rest of the parameters define the initial working mode. The OFDM application, however, modifies the sampling frequency and blocksize at runtime, depending on the transmission mode. 
+ 
+Now run again the core framework (''sudo runcf'' command) and from the command prompt, load, init and run the OFDM application as described in the previous section. 
 
-You may experience with different sampling frequencies and time-slots editing the file /usr/local/etc/usrp.conf. By setting different sampling frequencies
+Try again to change the fftsize and you should observe in an spectrum analyser that the transmitter is using more or less bandwidth.   
 
 == Distributed Processing ==
+
+In a distributed environment, one of the processors acts as the MASTER. The MASTER node runs the so called Manager Daemons. The aloe-ctss package already provides the configuration for running the demo with two computers connected by an Ethernet. 
+
 1) Download and install ALOE in two computers
 
 2) Setup your network, making sure you have full TCP and UDP connectivity between both computers.
 
-3) Edit file /usr/local/etc/xitf1.conf and replace 192.168.1.1 by the ip address of your MASTER node.
+3) In the SLAVE node, edit file /usr/local/etc/xitf1.conf and replace 192.168.1.1 by the ip address of your MASTER node.
 
-4)
+4) In the MASTER node, run the core framework
+{{{
+sudo runcf
+}}}
+
+5) In the SLAVE node, run the core framework indicating that the configuration file is platform1.conf:
+{{{
+sudo runcf -c hw_api/lnx/cfg/platform1.conf
+}}}
+
+6) In the MASTER node, you should see messages indicating that the new processor has been detected. 
+
+7) In the MASTER node, enter the load/init/run command sequence to begin start the waveform. Use 
+{{{
+execinfo ofdm128
+}}}
+command to check whether the waveform modules have been mapped to the two processors or not. If the waveform only uses one processor, try loading the '''ofdm512''' application (which requires more computing resources).