| Version 1 (modified by hvolos, 5 years ago) |
|---|
OSSIE Frequently Asked Questions
This page lists questions and answers that were asked in the OSSIE discussion lists.
USRP
How to install USRP only drivers?
Answer: Get GNUradio from:
http://gnuradio.org/trac/wiki/Download
On the stable branch or 3.1.* tarballs this should work:
./configure --disable-all-components --enable-usrp make
On the trunk
./configure --disable-all-components \
--enable-usrp --enable-omnithread --enable-mblock --enable-pmt
make
Other pages:
OWD
How do I add devices to the node definition?
I'm trying to create a new node in with OWD from the 0.6.2 vmware image. How do I add devices to the node definition?
Answer: Right click the device in the device list
OSSIE
Is there a Windows implementation?
Answer:
There is not a Windows implementation, and there are currently no plans to make one in the future.
The best solution for Windows users who don't have a machine they can install Linux on is to download VMware Player and use the OSSIE VMs, available on the downloads section of our website.
"Failed to resolve NameService?" error when running nodeBooter
Answer: Make sure that omniNames is running
The error persits even after starting omniNames
Answer: It appears the naming service is not starting. Could you send the contents of your omniNames.sh file? As an alternative to using omniNames.sh, you can type the following from the command line:
killall omniNames omniNames -start -logdir /home/<your user directory>/logs &
If you get an error message referring to log files, try typing
rm /home/<your user directory>/logs/omninames*
before running omniNames
Follow-up:
Using the commands on the command line worked and I was able to get the device registered.
killall omniNames
omniNames -start -logdir /home/Oss/logs &
Earlier my omniNames.sh was
killall omniNames [omniEvents]
rm /home/Oss/logs/omninames*
omniNames -start -logdir /home/Oss/logs &
When I deleted the [omniEvents], the script also worked fine.
