Changes between Version 12 and Version 13 of Tutorials/Wireless/Measurement Tool
- Timestamp:
- May 11, 2020, 1:02:24 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/Wireless/Measurement Tool
v12 v13 8 8 9 9 === Prerequisites === 10 In order to access the test bed, create a reservation and have it approved by the reservation service. Access to the resources are granted after the reservation is confirmed. Please follow the process shown on [wiki: cosmos_workflow the COSMOS work flow page] to get started.10 In order to access the test bed, create a reservation and have it approved by the reservation service. Access to the resources are granted after the reservation is confirmed. Please follow the process shown on [wiki:CosmosOverview/Workflow the COSMOS work flow page] to get started. 11 11 12 12 === Set up === 13 13 1. Sign up for a [https://cosmos-lab.org/portal-2/ COSMOS account] 14 14 2. [UserGuide/CreateRes Create a resource reservation on sandbox 1] 15 3. [ Documentation/Short/Login Login into your reserved domain.]16 4. Load merif.ndz .ndzon your resource. [UserGuide/OmfQuickStart - this is done via OMF commands.]15 3. [UserGuide/RemoteAccess/Console Login to your reserved domain.] 16 4. Load merif.ndz on your resource. [UserGuide/OmfQuickStart - this is done via OMF commands.] 17 17 18 18 * After loading the image, if utilizing a network based SDR radio (ie. ethernet with IP address) then follow the instructions [https://wiki.cosmos-lab.org/wiki/tutorials/n310_usage here to configure the network interface and detect the radio.] … … 27 27 28 28 Use the --help option to display all the variables ''rx_multi_receive'' accepts. 29 {{{ 29 {{{#!shell-session 30 30 root@node:~/RX_MULTI_RECEIVE# ./rx_multi_receive --help 31 31 UHD RX Multi Receive Allowed options: … … 55 55 56 56 To use ''rx_multi_receive'' standalone on an experiment server we can using the following options 57 {{{ 57 {{{#!shell-session 58 58 root@node:~/RX_MULTI_RECEIVE# ./rx_multi_receive --args="type=x300" --nsamps 1024000 --freq 2440e6 --rate 100e6 --gain 15 --dilv 59 59 }}} … … 67 67 68 68 Executing the application with only the above options will only configure the USRP's radio parameters and read in the specified number of samples. However the samples will be lost once the application exits. You should see output similar to the following. 69 {{{ 69 {{{#!shell-session 70 70 root@node:~/RX_MULTI_RECEIVE# 71 71 … … 136 136 Rerun the application with these and we'll see a few additional lines of output at the end indicating a connection to the OML database server. 137 137 138 {{{ 138 {{{#!shell-session 139 139 140 140 Writing FFT blocks into rx_multi_samples.sq3 @ 10.113.0.10:3003 … … 149 149 150 150 1. A handle to the radio is constructed and is used thoughout the source to make reference to the radio. 151 {{{ 151 {{{#!c++ 152 152 std::cout << std::endl; 153 153 std::cout << boost::format("Creating the usrp device with: %s...") % args << std::endl; … … 156 156 157 157 2. Use the handle to configure the radio paramters passed in from the command line. 158 {{{ 159 158 {{{#!c++ 160 159 //set the rx sample rate (sets across all channels) 161 160 std::cout << boost::format("Setting RX Rate: %f Msps...") % (rate/1e6) << std::endl; … … 176 175 usrp->set_rx_gain(gain,ch); 177 176 std::cout << boost::format("Actual RX Gain: %f dB...") % usrp->get_rx_gain() << std::endl << std::endl; 178 179 180 181 177 }}} 182 178 183 179 184 180 3. A receive streamer is created and a loop is used to read out complex samples into a large buffer that is used during post processing samples. 185 {{{ 186 181 {{{#!c++ 187 182 //setup streaming 188 183 std::cout << std::endl; … … 219 214 } // while() 220 215 221 222 216 }}} 223 217 … … 226 220 227 221 Inside this block, we create an object that performs 1024pt FFTs. 228 {{{ 222 {{{#!c++ 229 223 std::vector<std::complex<float> > time_buff( samps_per_buff ); 230 224 std::vector<std::complex<float> > freq_buff( samps_per_buff ); … … 239 233 240 234 We also construct an object for writing data to an OML server. Initialize the OML object with the OML options described above. 241 {{{ 235 {{{#!c++ 242 236 // OML object for sending data 243 237 CWriteOml oml; … … 246 240 247 241 Create keyed-values that will be sent for storage. Here we specify a string label (for the key, ie. a variable) with an OML data type. After all the keyed-value pairs have been defined, we start a connection with the OML service. 248 {{{ 242 {{{#!c++ 249 243 // Register measurement points 250 244 oml.register_mp("mboard_id", OML_STRING_VALUE); … … 272 266 Once all the keyed-valued pairs are updated with set_key(), they are sented over to the OML server by issuing the insert command. 273 267 This is done repeatedly until the entire buffer has been processed. 274 {{{ 275 268 {{{#!c++ 276 269 oml.set_mp("rx_id", (void*)usrp_info["rx_id"].c_str() ); 277 270 oml.set_mp("rx_subdev_name", (void*)usrp_info["rx_subdev_name"].c_str() ); … … 319 312 320 313 } // end for() 321 322 323 314 }}} 324 315 … … 352 343 353 344 We can recover the contents of the FFT data for each channel and save them into a binary file for viewing in octave. 354 {{{ 355 console >./db_parse --file /var/lib/oml2/rx_multi_samples.sq3 --blob2bin ch0_data.bin --ch 0 --table _mp__rx_multi_samples --key345 {{{#!shell-session 346 console:~$ ./db_parse --file /var/lib/oml2/rx_multi_samples.sq3 --blob2bin ch0_data.bin --ch 0 --table _mp__rx_multi_samples --key 356 347 Bins 357 348 … … 361 352 362 353 In the console we should have a binary file by the name ch0_data.bin. This can be loaded and viewed in ocatve. 363 {{{ 354 {{{#!octave 364 355 octave> mag0 = fReadBinaryFile('ch0_data.bin','single'); 365 356 octave> mag0 = reshape(mag0, 1024, length(mag0)/1024);
