Changes between Version 5 and Version 6 of WARPLab/Reference/Commands


Ignore:
Timestamp:
May 6, 2013, 4:32:48 PM (11 years ago)
Author:
murphpo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WARPLab/Reference/Commands

    v5 v6  
    1 [[TracNav(WARPLab7/TOC)]]
     1[[TracNav(WARPLab/TOC)]]
    22
    33= Reference Design Commands =
    44WARPLab commands are classified according to the subsystem in a WARP node that they affect.
    55
    6 == [wiki:/WARPLab7/Reference/Commands/Node Node Commands] ==
     6== [wiki:../Reference/Commands/Node Node Commands] ==
    77Node commands are responsible for node-level actions like blinking LEDs or reading the serial number from the WARP node.
    88
    9 == [wiki:/WARPLab7/Reference/Commands/Interface Interface Commands] ==
     9== [wiki:../Reference/Commands/Interface Interface Commands] ==
    1010Interface commands relate to radio interface actions like tuning center frequencies.
    1111
    12 == [wiki:/WARPLab7/Reference/Commands/Baseband Baseband Commands] ==
     12== [wiki:../Reference/Commands/Baseband Baseband Commands] ==
    1313Baseband commands are for interacting with the design running in the FPGA fabric. For example, a baseband command allows reading received I and Q values from the board that are stored in a buffer.
    1414
    15 == [wiki:/WARPLab7/Reference/Commands/Transport Transport Commands] ==
     15== [wiki:../Reference/Commands/Transport Transport Commands] ==
    1616Transport commands are for interacting with the subsystem that is responsible for communicating with the host PC.
    1717
    18 == [wiki:/WARPLab7/Reference/Commands/TriggerManager Trigger Manager Commands] ==
     18== [wiki:../Reference/Commands/TriggerManager Trigger Manager Commands] ==
    1919Trigger Manager commands are for handling the many different ways of triggering WARPLab nodes: Ethernet, Energy Detection, and hardware pins on the board.