Changes between Version 10 and Version 11 of ALOEOFDMDemo
- Timestamp:
- 08/07/12 01:34:05 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ALOEOFDMDemo
v10 v11 67 67 }}} 68 68 69 Now edit the ''mops'' field in /usr/local/etc/platform.conf, choosing the minimum MMACS otained in the test, and adjst the ''nof_cores'' accordingly.69 Now change the ''mops'' field in /usr/local/etc/platform.conf to contain the number of MMACS of child 0 as otained in the test. 70 70 71 71 == Running the Demo application == … … 94 94 statset ofdm128 source fftsize 512 95 95 }}} 96 Which set the fft size to 256 and 512 tones respectively (4 and 8 MHz bandwidth). By default, the framework will use one processor only from your computer. If you have a multi-core processor, edit the 'nof_cores' option in /usr/local/etc/platform.conf file. In our tests, the OFDM application runs perfectly in a 2.5 GHz Intel processor using one core only. The 512 mode produces frequent real-time faults (printed stdout). This mode works correctly in a dual-processorenvironment.96 to change the fft size to 256 and 512, respectively (4 and 8 MHz bandwidth). By default, the framework will use one processor only from your computer. If you have a multi-core processor, edit the 'nof_cores' option in /usr/local/etc/platform.conf file. The OFDM application should runs perfectly on a 2.5 GHz Intel Dual-core processor using one core only. The 512 mode produces frequent real-time faults (printed stdout). This mode works correctly on a Dual-core environment. 97 97 98 98 == USRP ==