| 1 | % ------------------------------------------------------------------ |
|---|
| 2 | % |
|---|
| 3 | % TITLE: OSSIE Quick Start Guide |
|---|
| 4 | % AUTHORS: Matt Carrick |
|---|
| 5 | % CREATED: |
|---|
| 6 | % REVISED: |
|---|
| 7 | % URL: http://ossie.wireless.vt.edu/ |
|---|
| 8 | % |
|---|
| 9 | % ------------------------------------------------------------------ |
|---|
| 10 | |
|---|
| 11 | \section{Quick Start Guide} |
|---|
| 12 | \label{section:quickstartguide} |
|---|
| 13 | The following is a quick start guide. It is meant to be a concise introduction |
|---|
| 14 | to OSSIE. While it assumes general computer |
|---|
| 15 | knowledge, it tries not to assume extensive knowledge of or familiarity with Linux or |
|---|
| 16 | OSSIE. The quick start guide is a compact version of much of the rest of |
|---|
| 17 | the guide. If you are interested in more in-depth coverage, we recommend you |
|---|
| 18 | fully read the pertinent sections of the guide. |
|---|
| 19 | The rest of this document should be able answer more of the questions that may arise |
|---|
| 20 | during installation and provide deeper insight into OSSIE. That |
|---|
| 21 | said, here is a short walkthrough to get you experimenting with |
|---|
| 22 | OSSIE in short order. |
|---|
| 23 | |
|---|
| 24 | \subsection{Using the OSSIE VMware Player Image} |
|---|
| 25 | The VMware Player application is needed to run the OSSIE demonstration waveform |
|---|
| 26 | using our VMware image. |
|---|
| 27 | |
|---|
| 28 | Unless VMware Player is already installed on your system, download it from \\ |
|---|
| 29 | \href{http://www.vmware.com/download/player/}{http://www.vmware.com/download/player/} |
|---|
| 30 | and install it. For detailed instructions, consult the VMWare Player User Guide~\cite{vmware:web}. |
|---|
| 31 | |
|---|
| 32 | Next, download the OSSIE VMware image at \\ |
|---|
| 33 | \href{http://ossie.wireless.vt.edu/trac/wiki/Downloads}{http://ossie.wireless.vt.edu/trac/wiki/Downloads}. |
|---|
| 34 | When the download is complete, unzip the image to another directory. We |
|---|
| 35 | recommend you keep the original zip file. It can serve as a useful backup |
|---|
| 36 | should you want or need to start from a fresh install and might save |
|---|
| 37 | time and bandwidth. |
|---|
| 38 | |
|---|
| 39 | Once the image is unpacked, boot it up in VMware Player. This quick start guide |
|---|
| 40 | will walk you though the process of running OSSIE and our demonstration |
|---|
| 41 | waveform. \describeossiedemo |
|---|
| 42 | |
|---|
| 43 | \subsection{Running the OSSIE Demonstration Waveform} |
|---|
| 44 | \label{section:quickstartguide:ossiedemo} |
|---|
| 45 | Once the OSSIE VMware image has booted up, open a |
|---|
| 46 | terminal window by navigating to Applications $\to$System |
|---|
| 47 | Tools$\to$Terminal. The first thing that needs to be started is the |
|---|
| 48 | naming service. Type as root: |
|---|
| 49 | %TODO: instructions on logging in as root |
|---|
| 50 | \begin{lstlisting}[] |
|---|
| 51 | # omniNames.sh |
|---|
| 52 | \end{lstlisting} |
|---|
| 53 | |
|---|
| 54 | %TODO: fix image to automagically start naming service |
|---|
| 55 | |
|---|
| 56 | The terminal should look like this: |
|---|
| 57 | \begin{center} |
|---|
| 58 | \includegraphics[scale=0.4]{figures/quickstart/omniNames.png} |
|---|
| 59 | \end{center} |
|---|
| 60 | |
|---|
| 61 | The next service that needs to be started is the Node Booter. Open a new tab or |
|---|
| 62 | a completely new terminal and type the commands in the listing below. You can |
|---|
| 63 | press tab after the first couple of letters of a command, directory or |
|---|
| 64 | filename to have it automatically completed, saving time and perhaps avoiding |
|---|
| 65 | typos. |
|---|
| 66 | \begin{lstlisting}[] |
|---|
| 67 | $ cd /sdr/ |
|---|
| 68 | $ nodeBooter -D -d nodes/default_GPP_node/DeviceManager.dcd.xml |
|---|
| 69 | \end{lstlisting} |
|---|
| 70 | |
|---|
| 71 | The terminal should look like this: |
|---|
| 72 | \begin{center} |
|---|
| 73 | \includegraphics[scale=0.4]{figures/quickstart/nodeBooter.png} |
|---|
| 74 | \end{center} |
|---|
| 75 | |
|---|
| 76 | Now load the waveform using wavLoader. In a third tab or terminal, type in: |
|---|
| 77 | \begin{lstlisting}[] |
|---|
| 78 | $ cd /sdr/waveforms/ossie_demo |
|---|
| 79 | $ wavLoader.py ossie_demo_DAS.xml |
|---|
| 80 | \end{lstlisting} |
|---|
| 81 | |
|---|
| 82 | The terminal should look similar to the following: |
|---|
| 83 | \begin{center} |
|---|
| 84 | \includegraphics[scale=0.4]{figures/quickstart/wavLoader.png} |
|---|
| 85 | \end{center} |
|---|
| 86 | |
|---|
| 87 | Select the first listing of the OSSIE demonstration waveform,\\ |
|---|
| 88 | {\tt //waveforms/ossie\_demo/ossie\_demo.sad.xml} |
|---|
| 89 | \begin{lstlisting}[] |
|---|
| 90 | Selection: 1 |
|---|
| 91 | \end{lstlisting} |
|---|
| 92 | |
|---|
| 93 | The tab or terminal window in which nodeBooter was started should now contain |
|---|
| 94 | the output of the demonstration waveform. The lines will update with output |
|---|
| 95 | similar to this: |
|---|
| 96 | \begin{verbatim} |
|---|
| 97 | RxDemo errors: X / 1024 |
|---|
| 98 | \end{verbatim} |
|---|
| 99 | The X denotes the number of QPSK bit errors out of 1024 that have been detected |
|---|
| 100 | by the RxDemo component. |
|---|
| 101 | Here is an example output: |
|---|
| 102 | \begin{center} |
|---|
| 103 | \includegraphics[scale=0.4]{figures/quickstart/RxDemo.png} |
|---|
| 104 | \end{center} |
|---|
| 105 | |
|---|
| 106 | Congratulations! You have just run the QPSK demonstration waveform for OSSIE |
|---|
| 107 | version 0.7.0. From here you may be interested in learning how to create |
|---|
| 108 | your own waveforms using the OSSIE Waveform Developer (OWD) described in |
|---|
| 109 | Section~\ref{section:owd}. |
|---|
| 110 | |
|---|
| 111 | |
|---|