Changes between Version 18 and Version 19 of WARPLab6


Ignore:
Timestamp:
Jan 13, 2009, 6:09:52 PM (15 years ago)
Author:
mduarte
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WARPLab6

    v18 v19  
    1919 * 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.
    2020
    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.
     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.
    2222
    2323
    … …  
    4040 * [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.
    4141 * [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 * [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.
    4243
    4344 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.