Changes between Version 34 and Version 35 of WARPLab6


Ignore:
Timestamp:
Dec 9, 2009, 3:51:14 PM (14 years ago)
Author:
sgupta
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WARPLab6

    v34 v35  
    11[[TracNav(WARPLab/TOC)]]
    22
    3 == WARPLab Framework Overview ==
     3= WARPLab Framework Overview =
    44
    5 WARPLab is a framework which brings together WARP and MATLAB. With WARPLab, you can interact with WARP nodes directly from the MATLAB workspace and signals generated in MATLAB can be transmitted in real-time over-the-air using WARP nodes. This facilitates rapid prototyping of PHYsical (PHY) layer algorithms.
     5WARPLab is a framework which brings together WARP and MATLAB. With WARPLab, you can interact with WARP nodes directly from the MATLAB workspace and signals generated in MATLAB can be transmitted in real-time over-the-air using WARP nodes. This facilitates rapid prototyping of physical layer (PHY) algorithms.
    66
    7 The WARPLab framework provides the following.
    8 
    9  * WARPLab XPS Reference Design: The bitstream ('.bit' file) to program the WARP nodes and the WARPLab Xilinx Platform Studio (XPS) Reference Design to generate this bitstream are provided.
    10  * WARPLab Reference M-Code: M-Code functions that facilitate interaction with WARP nodes directly from MATLAB workspace are provided.
    11  * WARPLab Examples: M-Code examples that show how to use the WARPLab Reference M-Code are provided.
    12 
    13 The basic WARPLab setup is shown in the figure below. The basic WARPLab flow is the following.
     7The WARPLab setup is shown in the following figure.
    148
    159[[Image(WARPLab/Images:design_flow.pdf)]]
    1610
    17  * The user creates in MATLAB the samples to be transmitted.
     11The design flow for a new PHY is the following:
     12 * The user creates in MATLAB the samples to be transmitted as part of the custom PHY.
    1813 * The samples to be transmitted are downloaded to buffers in the nodes assigned as transmitters.
    1914 * 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.
    … …  
    2116 * Received samples are processed offline in MATLAB
    2217
    23 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/extend 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 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.
     18== Example Setup ==
    2419
    25 == Basic WARPLab Setup ==
    26 Two WARP nodes and a host computer running MATLAB are connected to a switch via Ethernet links.
     20Up to 16 WARP nodes and a host computer running MATLAB are connected to a switch via Ethernet links. The Ethernet links are used to transfer data to and from the WARP nodes. While the over-the-air transmission is real-time, the communication between the PC and the boards is significantly longer. Check the [wiki:WARPLab/Benchmarks benchmarks] page for its performance characterization.
    2721
    2822[[Image(WARPLab/Images:warplab_setup.pdf)]]
     23
     24== Resources ==
     25
     26In order to allow rapid prototyping, the WARPLab framework provides the following.
     27 * [wiki:WARPLab/RefDesign WARPLab XPS Reference Design]: The bitstream ('.bit' file) to program the WARP nodes and the WARPLab Xilinx Platform Studio (XPS) Reference Design to generate this bitstream are provided.
     28 * [wiki:WARPLab/Releases WARPLab Reference M-Code]: M-Code functions that facilitate interaction with WARP nodes directly from MATLAB workspace are provided.
     29 * [wiki:WARPLab/Releases WARPLab Examples]: M-Code examples that show how to use the WARPLab Reference M-Code are provided.
     30
     31The 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/extend 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 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. The vanilla architecture is described [wiki:WARPLab/Architecture here] and [wiki:WARPLab/ExtendingWARPLab extending WARPLab] describes the changes needed to modify the system. Specifications of the radio parameters controllable from M-code are listed [wiki:WARPLab/Specifications here].
    2932
    3033
    3134
    3235
     36