next up previous contents
Next: 2 Introduction Up: 1 Quick Start Guide Previous: 1.1 Using the OSSIE   Contents


1.2 Running the OSSIE Demonstration Waveform

Once the OSSIE VMware image has booted up, open a terminal window by navigating to ApplicationsSystem ToolsTerminal. The first thing that needs to be started is the naming service. Type as root:
 # omniNames.sh

The terminal should look like this:

Image omniNames

The next service that needs to be started is the Node Booter. Open a new tab or a completely new terminal and type the commands in the listing below. You can press tab after the first couple of letters of a command, directory or filename to have it automatically completed, saving time and perhaps avoiding typos.

 $ cd /sdr/
 $ nodeBooter -D -d nodes/default_GPP_node/DeviceManager.dcd.xml

The terminal should look like this:

Image nodeBooter

Now load the waveform using wavLoader. In a third tab or terminal, type in:

 $ cd /sdr/waveforms/ossie_demo
 $ wavLoader.py ossie_demo_DAS.xml

The terminal should look similar to the following:

Image wavLoader

Select the first listing of the OSSIE demonstration waveform,
//waveforms/ossie_demo/ossie_demo.sad.xml

 Selection: 1

The tab or terminal window in which nodeBooter was started should now contain the output of the demonstration waveform. The lines will update with output similar to this:

 RxDemo errors:  X  / 1024
The X denotes the number of QPSK bit errors out of 1024 that have been detected by the RxDemo component. Here is an example output:
Image RxDemo

Congratulations! You have just run the QPSK demonstration waveform for OSSIE new to version 0.6.2. From here you may be interested in learning how to create your own waveforms using the OSSIE Waveform Developer (OWD) described in Section 5.


next up previous contents
Next: 2 Introduction Up: 1 Quick Start Guide Previous: 1.1 Using the OSSIE   Contents
2008-04-25