Changes between Version 15 and Version 16 of WARPLab6


Ignore:
Timestamp:
Nov 13, 2008, 7:34:54 PM (15 years ago)
Author:
mduarte
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WARPLab6

    v15 v16  
    1313There are three versions of the WARPLab files. FOR NEW USERS WE RECOMMEND USING VERSION 3. Versions 1 and 2 will be deprecated soon.
    1414
    15  * Version 1: Posted on November 2007. Supports SISO communication. This was the version used at the Fourth WARP Workshop (held at Rice on Nov 1-2 2007) and the Fifth WARP Workshop (held at IIT Madras on Dec 1-2 2007).
     15 * Version 1: Posted on November 2007. Supports SISO communication. This was the version used at the Fourth WARP Workshop held at Rice on Nov 1-2 2007 and the Fifth WARP Workshop held at IIT Madras on Dec 1-2 2007.
    1616
    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.
     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.
    1818
    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.
     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, this was the version used at the eighth WARP workshop held at Rice University on November 13-14 2008. The WARPLab MIMO 2x2 Reference Design has been updated to version 10 of the Xilinx tools. This 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. The WARPLab MIMO 4x4 Reference Design has not been updated to version 10 of the Xilinx tools but will be updated soon.
    2022
    2123
     
    2628 * [source:/ResearchApps/PHY/WARPLAB/WARPLab_SISO_MIMO2x2/M_Code Version 2 of the Reference M code].
    2729 * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4/M_Code_Source Version 3 of the Reference M code].
     30 * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R04/M_Code_Source Version 4 of the Reference M code].
     31
    2832 3. Connect your PC and two WARP boards to a common Ethernet switch. Ideally, nothing else should be connected to the same switch.
    2933 4. Set your PC's IP address to 10.0.0.200
     
    3539 * [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.
    3640 * [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.
     41 * [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.
     42
    3743 7. Try one of the examples. The GUI (warplab_mimo_2x2_GUI and the warplab_siso_example_TxRx) are the best ones to start with.
    3844 * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4/M_Code_Examples WARPLab examples] that work with version 3 of the Reference M code.
     45 * [source:/ResearchApps/PHY/WARPLAB/WARPLab_MIMO2x2_MIMO4x4_R04/M_Code_Examples WARPLab examples] that work with version 4 of the Reference M code.
    3946
    4047== XPS Reference Design ==