Changes between Version 6 and Version 7 of WARPLab/Reference/Commands
- Timestamp:
- May 6, 2013, 4:34:07 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WARPLab/Reference/Commands
v6 v7 4 4 WARPLab commands are classified according to the subsystem in a WARP node that they affect. 5 5 6 == [wiki:. ./Reference/Commands/Node Node Commands] ==6 == [wiki:./Node Node Commands] == 7 7 Node commands are responsible for node-level actions like blinking LEDs or reading the serial number from the WARP node. 8 8 9 == [wiki:. ./Reference/Commands/Interface Interface Commands] ==9 == [wiki:./Interface Interface Commands] == 10 10 Interface commands relate to radio interface actions like tuning center frequencies. 11 11 12 == [wiki:. ./Reference/Commands/Baseband Baseband Commands] ==12 == [wiki:./Baseband Baseband Commands] == 13 13 Baseband 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. 14 14 15 == [wiki:. ./Reference/Commands/Transport Transport Commands] ==15 == [wiki:./Transport Transport Commands] == 16 16 Transport commands are for interacting with the subsystem that is responsible for communicating with the host PC. 17 17 18 == [wiki:. ./Reference/Commands/TriggerManager Trigger Manager Commands] ==18 == [wiki:./TriggerManager Trigger Manager Commands] == 19 19 Trigger Manager commands are for handling the many different ways of triggering WARPLab nodes: Ethernet, Energy Detection, and hardware pins on the board.
