- COSMOS Testbed Overview
- Getting Started
- User Guide
- Resources, Services and APIs
- Hardware Info
- RF Policies & Compliance
802.11ad Preamble Processing blocks on COSMOS SandBox1
This tutorial describes how to use RFNoC 802.11ad preamble processing blocks with Sivers 60GHz front-ends on COSMOS SandBox1. RFNoC 802.11ad preamble processing blocks demonstrated in this tutorial were developed by researchers at IMDEA networks institute, Spain, as an extension for EU project ORCA https://www.orca-project.eu/orca-at-the-imec-technology-forum. The extension was named MIllimeter wave SDR based Open experimentation platform (MISO), and the focus was on developing hardware/software for mmWave experimentation on SDRs. Specifically FPGA modules for processing 802.11ad(SC) preamble at scaled down bandwidth were designed and integrated with RFNoC, GNURadio, to be used on USRP X310s. Detailed information about the project can be found at https://www.orca-project.eu/millimeter-wave-open-experimentation-platform/.
Setup for the experiment is shown in the figure above. In the benchtop 60GHz setup of SandBox1, either USRP X310 or RFSoC ZCU111 can be used for baseband processing. RF Switch boxes as shown in the figure are used to select between X310 and RFSoC. RF switch commands are explained at wiki:/Resources/Services/RFSwitch . To select X310s as baseband processing units, all the switches in the RF switch boxes are configured to port 1.
This experiment uses USRP X310s for baseband processing. Sivers control software on srv3, srv4 talk to the mmWave front-ends over USB links. Host GNURadio applications on srv3, srv4, send/receive data samples to/from the X310s over 10G Ethernet links. 802.11ad single carrier frames at reduced bandwidth (200MHz) are transmitted over 60GHz mmWave link, and channel impulse response is computed on the receive end.
In order to access the test bed, create a reservation and have it approved by the reservation service. Access to the resources is granted after the reservation is confirmed. Please follow the process shown on the COSMOS work flow page to get started.
2 servers srv3-lg1, srv4-lg1, 2 USRP X310s rfdev3-1, rfdev3-2, and both the Sivers platforms rfdev3-5, rfdev3-6 on COSMOS SB1.
Follow the steps below to gain access to the sandbox 1 console and set up nodes with appropriate images.
- If you don't have one already, sign up for a COSMOS account
- Create a resource reservation on sandbox 1
- Login into sandbox 1 console (console.sb1.cosmos-lab.org) with two SSH sessions.
- Make sure all the nodes and devices used in the experiment are turned off:
omf tell -a offh -t srv3-lg1,srv4-lg1,rfdev3-1,rfdev3-2,rfdev3-5,rfdev3-6
- The image rfnoc_wigig.ndz has aforementioned RFNoC 802.11ad preamble processing blocks and Sivers control software installed.
Load rfnoc_wigig.ndz on srv3,srv4.
omf load -i rfnoc_wigig.ndz -t srv3-lg1,srv4-lg1
- Turn all the required resources on and check the status
omf tell -a on -t srv3-lg1,srv4-lg1,rfdev3-1,rfdev3-2,rfdev3-5,rfdev3-6
omf stat -t system:topo:allres
- Make sure the RF switch boxes are configured to use X310s (all switches set to port 1)
root@console:~# curl am1.cosmos-lab.org:5054/rf_switch/status?name=rfsw1.sb1.cosmos-lab.org,rfsw2.sb1.cosmos-lab.org <response status="OK"> <rf_switch name="rfsw1.sb1.cosmos-lab.org" num_of_switches="4"> <switch number="1" port="1"/> <switch number="2" port="1"/> <switch number="3" port="1"/> <switch number="4" port="1"/> </rf_switch> <rf_switch name="rfsw2.sb1.cosmos-lab.org" num_of_switches="4"> <switch number="1" port="1"/> <switch number="2" port="1"/> <switch number="3" port="1"/> <switch number="4" port="1"/> </rf_switch> </response>
- If some or all the ports are set to "2", set them to port "1"
- ssh to the nodes, use option -Y for using GUI.
Find and prepare USRPs
- The IP addresses for Ethernet Port 1(10G) on the X310s rfdev3-1 and rfdev3-2 were hard-coded to 10.115.6.1 and 10.115.6.2 respectively. To access them from srv3-lg1 or srv4-lg1, configure the network interface enp1s0 of srv3-lg1 to 10.115.1.3 and srv4-lg1 to 10.115.1.4, as follows
root@srv3-lg1:~# ip link set enp1s0 mtu 9000 up root@srv3-lg1:~# ip addr add 10.115.1.3/16 dev enp1s0 root@srv3-lg1:~# ip addr show dev enp1s0 4: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000 link/ether f4:52:14:83:b9:30 brd ff:ff:ff:ff:ff:ff inet 10.115.1.3/16 brd 10.115.255.255 scope global enp1s0 valid_lft forever preferred_lft forever inet6 fe80::f652:14ff:fe83:b930/64 scope link valid_lft forever preferred_lft forever
- Run uhd_find_devices to check if the X310s can be reached
root@srv3-lg1:~# uhd_find_devices --args="addr=10.115.6.1" [INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; UHD_184.108.40.206-release -------------------------------------------------- -- UHD Device 0 -------------------------------------------------- Device Address: serial: 31B6FFA addr: 10.115.6.1 fpga: XG name: rfdev3-1 product: X310 type: x300
- Check which RFNoC blocks are loaded on the X310s, by running uhd_usrp_probe
root@srv3-lg1:~# uhd_usrp_probe --args="addr=10.115.6.1"
- Following is the list of RFNoC blocks required for the experiment
| | | RFNoC blocks on this device: | | | | | | * DmaFIFO_0 | | | * Radio_0 | | | * Radio_1 | | | * PacketDetector_0 | | | * CFOC_0 | | | * DDC_0 | | | * DUC_0 | | | * FIR_0 | | | * SymbolTiming_0 | | | * BoundaryDetector_0 | | | * CIR_0 | | | * FIFO_0 | | | * FIFO_1
- If the required RFNoC blocks are not found, load X310 with MISO_IMAGE_x300.bit
root@srv3-lg1:~# uhd_image_loader --args="addr=10.115.6.1,type=x300" --fpga-path="ORCA_MISO_PROJECT/FPGA_IMAGES/MISO_IMAGE_x300.bit"
- Power cycle X310 to use the new image, and run uhd_usrp_probe to check RFNoC blocks.
root@console:~# omf tell -a offh -t rfdev3-1
root@console:~# omf tell -a on -t rfdev3-1
Prepare Sivers 60GHz front-ends
- To demonstrate the experiment here, we use Sivers front-end SN0240 as transmitter and SN0243 as receiver
|SN0240 as transmitter||SN0243 as receiver|
|root@srv4-lg1:~/ederenv# ./start_mb1.sh —gui SN0240||root@srv3-lg1:~/ederenv# ./start_mb1.sh —gui SN0243|
|Click "TX enable" and "LO leakage Cal"||Click "RX enable"|
Run the experiment
- Open transmit application TX_TEST.grc on transmit node(srv4-lg1). This application transmits 802.11ad frames over rfdev3-2(10.115.6.2), at 200MSPS, by reading samples from a pre-generated file.
- Open receive application RADIORX_CIR.grc on receive node(srv3-lg1). This application receives and processes samples over rfdev3-1(10.115.6.1) as seen in the grc model below. Channel impulse response computed for every frame is written into a file on the host node.
|root@srv4-lg1:~# gnuradio-companion ORCA_MISO_PROJECT/examples/TX_TEST.grc||root@srv3-lg1:~# gnuradio-companion ORCA_MISO_PROJECT/examples/RADIORX_CIR.grc|
- Run TX applications followed by the RX application.
- Launch octave and plot the CIR using ORCA_MISO_PROJECT/examples/CIR_read_out_file.m
- Shown below are the CIR plots obtained for TX beam angles set to 0 and -5 degrees.
|TX beam angle 0||TX beam angle -5|
- Sivers_TX_GUI.jpg (174.4 KB ) - added by 7 months ago.
- Sivers_RX_GUI.jpg (126.9 KB ) - added by 7 months ago.
- Sivers_RX_SN0243.jpg (128.2 KB ) - added by 7 months ago.
- Sivers_TX_SN0240.jpg (162.6 KB ) - added by 7 months ago.
- radiorx_cir_grc.jpg (204.4 KB ) - added by 7 months ago.
- tx_test_grc.jpg (165.9 KB ) - added by 7 months ago.
- CIR_0.jpg (33.2 KB ) - added by 7 months ago.
- CIR_neg5.jpg (32.8 KB ) - added by 7 months ago.
- MISO_tutorial.jpg (256.2 KB ) - added by 7 weeks ago.
Download all attachments as: .zip