| 17 | | * Version 2: Posted on April 2008. Supports SISO and MIMO (2x2) communication and allows continuous transmission mode. This was the version used at the Sixth WARP Workshop held at Nile University on April 16-17 2008. Two bitstreams are provided, one bitstream to program the boards in the SISO configuration and another bitstream to program the boards in the 2x2 MIMO configuration. The MATLAB Reference functions support both SISO and 2x2 MIMO. |
| | 15 | * The user creates in MATLAB the samples to be transmitted. |
| | 16 | * The samples to be transmitted are downloaded to buffers in the nodes assigned as transmitters. |
| | 17 | * The user sends a trigger to transmitter and receiver nodes. Upon reception of this trigger, samples are transmitted over-the-air and captured in real-time. |
| | 18 | * The user reads captured samples from the receiver nodes to the MATLAB workspace. |
| | 19 | * Received samples are processed offline in MATLAB |
| 19 | | * Version 3: Posted on July 2008. Supports MIMO 4x4 communication and allows continuous transmission mode for 2x2 MIMO. This was the version used at the Seventh WARP Workshop held at Rice University on July 14-15 2008. Two bitstreams are provided, one bitstream to program the boards in the 2x2 MIMO configuration and another bitstream to program the boards in the 4x4 MIMO configuration. Continuous transmission mode and reading of RSSI values is supported by the 2x2 MIMO bitstream but not by the 4x4 MIMO bitstream. When the boards are programmed with the 4x4 MIMO bitstream 2x2 MIMO communication is possible but continuous transmission mode and reading of RSSI values is not possible. The MATLAB Reference functions support both 2x2 and 4x4 MIMO bitstreams. |
| 20 | | |
| 21 | | * Version 4: Posted on November 2008, modified January 2009. The WARPLab MIMO 2x2 and 4x4 Reference Designs have been updated to version 10 of the Xilinx tools. The update required some changes in the Sysgen model resulting in minor changes in the Reference M code. The Capture Offset parameter has been changed to a Transmitter Delay parameter (look at the warplab_defines.m code and the WARPLab examples), the Capture Offset was a receiver parameter, the Transmitter Delay is a transmitter parameter and should be downloaded to the transmitter node. Two bitstreams are provided, one bitstream to program the boards in the 2x2 MIMO configuration and another bitstream to program the boards in the 4x4 MIMO configuration. Reading of RSSI values is supported by the 2x2 MIMO bitstream but not by the 4x4 MIMO bitstream. Continuous transmission mode is supported by both the 2x2 and 4x4 bitstreams. When the boards are programmed with the 4x4 MIMO bitstream 2x2 MIMO communication is possible but reading of RSSI values is not possible. The MATLAB Reference functions support both 2x2 and 4x4 MIMO bitstreams. |
| 22 | | |
| 23 | | * '''Version 5''': Posted on September 2009. The WARPLab MIMO 2x2 and 4x4 Reference Designs have been updated to include Automatic Gain Control (AGC). Previous versions of WARPLab required Manual Gain Control (MGC), the user was required to set receiver gains manually. In this new Version 5 release the user can choose between AGC or MGC mode using simple m-code functions. Two bitstreams are provided, one bitstream to program the boards in the 2x2 MIMO configuration and another bitstream to program the boards in the 4x4 MIMO configuration. AGC and MGC are supported by both bitstreams. Reading of RSSI values is supported by the 2x2 MIMO bitstream but not by the 4x4 MIMO bitstream. Continuous transmission mode is supported by both the 2x2 and 4x4 bitstreams. When the boards are programmed with the 4x4 MIMO bitstream 2x2 MIMO communication is possible but reading of RSSI values is not possible. The MATLAB Reference functions support both 2x2 and 4x4 MIMO bitstreams. |
| | 21 | The WAPLAB framework facilitates experimental evaluation of PHY layer algorithms. However, some novel algorithms may require features not provided in the WARPLab framework. Users are encouraged to modify the WARPLab XPS Reference Design and WARPLab Reference M-Code if this is required in order to meet experiment requirements. For example, if part of the signal processing cannot be done offline in MATLAB but must to be done in real-time, then this signal processing can be implemented in FPGA logic by modifying the WARPLab XPS Reference Design. Depending on the experiment, the users may also have to modify the WARPLab Reference M-Code. |
| 26 | | == Getting Started == |
| 27 | | 1. Install Peter Rydesäter's open-source TCP/UDP toolbox for MATLAB (get it free from [http://www.mathworks.com/matlabcentral/fileexchange/loadFile.do?objectId=345 MATLAB Central]). |
| 28 | | 2. Download the WARPLab Reference M code to your PC. The instructions are available [wiki:edk_user_repository here]. In the final step you can choose the appropriate version to add to the path. |
| 29 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLAB_SISO/M_code Version 1 of the Reference M code]. |
| 30 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_SISO_MIMO2x2/M_Code Version 2 of the Reference M code]. |
| 31 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4/M_Code_Source Version 3 of the Reference M code]. |
| 32 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R04/M_Code_Source Version 4 of the Reference M code]. |
| 33 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R05/M_Code_Reference Version 5 of the Reference M code]. |
| 35 | | 3. Connect your PC and two WARP boards to a common Ethernet switch. Ideally, nothing else should be connected to the same switch. |
| 36 | | 4. Set your PC's IP address to 10.0.0.200 |
| 37 | | 5. Set the DIP switches on two boards to 0 and 1 |
| 38 | | 6. Download the WARPLab bitstream to both boards. |
| 39 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLAB_SISO/warplab_siso.bit SISO bitstream] that works with version 1 of the Reference M code |
| 40 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_SISO_MIMO2x2/warplab_siso_v02.bit SISO bitstream] that works with version 2 of the Reference M code. |
| 41 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_SISO_MIMO2x2/warplab_mimo_2x2_v02.bit 2x2 MIMO bitstream] that works with version 2 of the Reference M code. |
| 42 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4/warplab_mimo_2x2_v03.bit 2x2 MIMO bitstream] that works with version 3 of the Reference M code. |
| 43 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4/warplab_mimo_4x4_v03.bit 4x4 MIMO bitstream] that works with version 3 of the Reference M code. |
| 44 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R04/warplab_mimo_2x2_v04.bit 2x2 MIMO bitstream] that works with version 4 of the Reference M code. |
| 45 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R04/warplab_mimo_4x4_v04.bit 4x4 MIMO bitstream] that works with version 4 of the Reference M code. |
| 46 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R05/warplab_mimo_2x2_v05.bit 2x2 MIMO bitstream] that works with version 5 of the Reference M code. |
| 47 | | * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R05/warplab_mimo_4x4_v05.bit 4x4 MIMO bitstream] that works with version 5 of the Reference M code. |
| | 25 | == Basic WARPLab Setup == |
| | 26 | Two WARP nodes and a host computer running MATLAB are connected to a switch via Ethernet links. |
