root/documentation/ossie/user-guide-0.6.2/RunningWaveforms.tex @ 5931

% ------------------------------------------------------------------
%
%   TITLE: Running OSSIE Waveforms
% AUTHORS: 
% CREATED: 
% REVISED: 
%     URL: http://ossie.wireless.vt.edu/
%
% ------------------------------------------------------------------

\section{Running Waveforms}
\label{section:runningwaveforms}

\subsection{Start the naming service}
If you installed omniORB using {\tt rpm} and
have since restarted your machine chances are the naming service is running.
If not, you will need to run {\tt omniNames.sh} (see
Appendix~\ref{appendix:omninamessh}).

\subsection{Run nodeBooter}
Open a new terminal and execute the following
\begin{lstlisting}[]
 $ cd /sdr
 $ nodeBooter -D -d nodes/default_GPP_node/DeviceManager.dcd.xml
\end{lstlisting}
It is important that {\tt nodeBooter} be run from the {\tt /sdr} directory.

\subsection{Load a waveform}
The 0.6.2 release supports two options for loading a waveform
\begin{enumerate}
\item Using the Python command-line {\tt wavLoader.py} script (discussed
below)
\item Using the Python graphical tool ALF (see Section~\ref{section:alf})
\end{enumerate}

Load the waveform using wavLoader. In a new terminal execute
\begin{lstlisting}[]
 $ cd /sdr/waveforms/MyWaveform
 $ wavLoader.py MyWaveform_DAS.xml
\end{lstlisting}

One or more SAD files (ending in {\tt .sad.xml}) will be listed.  To load the
waveform, enter the number that corresponds to {\tt MyWaveform.sad.xml}.  If
this file is listed twice, choose the first listing ({\tt
//MyWaveform.sad.xml}).

Finally, enter {\tt s} to start the waveform.