|Version 4 (modified by cdietric, 5 years ago)|
OSSIE Frequently Asked Questions
This page lists questions and answers that were asked in the OSSIE discussion lists or other venues.
What do I do if I can't get the omniORB source RPM from fourpalms?
Answer: The fourpalms site is occasionally unavailable. If this happens, try getting the file from http://opensource.nederland.net/omniORB/downloads/4.1.0/SRPMS/omniORB-4.1.0-1.src.rpm , and continue just as you would with the file from fourpalms. (added to 0.6.2 user guide 4/11/08)
How to install USRP only drivers?
Answer: Get GNUradio from:
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
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
Is there a Windows implementation?
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
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.