A possible generic solution to this is to acquire the filedescriptor for the device which is then used by the subsequent calls. Using this image, when I log in to the node, I > can go to the gnuradio folder by giving the following command: > > *cd gnuradio-uhd/gnuradio/* > > Thereafter, I Try typing my_usrp = findsdru into the MATLAB command window. I had followed http://gnuradio.org/trac/wiki/BuildGui \ de to bulid the GNU Radio. have a peek at this web-site
I can't find my USRP >>>> > with uhd_find_devices or lsusb, I've used both with and without >>>> > sudo. Rather, the issue is with >> your system. >> >> What USB controller are you using? I've also tried just about all the USB ports on my computer. >>>> > >>>> > The only thing I can think of is enabling USB 3 in my bios (if That's fine Read More https://lists.gnu.org/archive/html/discuss-gnuradio/2005-05/msg00158.html
Already have an account? If the second one is able to detect signals that the first cannot, it is likely that the first device needs replaced. FATAL: port number 1 exceeds max of 0 Trying to fill up 0 missing channel(s) with null source(s).
On *BSD this is not possible and is exactly the some problem as seen with the audio.sink() and audio.source() function that I hacked around. terminate called after throwing an instance of 'std::runtime_error' what(): throttle(53): insufficient connected output ports (1 needed, 0 connected) Aborted (core dumped) courtarro commented Apr 11, 2014 That makes sense. Could this be a udev issue >>> or does lsusb not have anything to do with udev? Owner csete commented Apr 11, 2014 By default gr-osmosdr presents the device arguments returned by uhd::device::find() and I guess it is just unfortunate that the default setup for the B210 is
This is the first time that I connect USRP board to PC. Computer Performance ↖top When running a simulation with an audio output, the audio sounds choppy or keeps cutting out If this is happening, it is likely that your computer is underruning. This can My computer equipes USB 1.1. > I use Fedora Core 7 + python 2.5 + gnuradio 3.0.3 to bulid the GNU Radio. > I had followed http://gnuradio.org/trac/wiki/BuildGuide to bulid the GNU http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2015-January/012122.html Feedback is welcome.
It almost seems like more of an osmocom bug since defaulting to enabling both outputs is likely to confuse many apps. Contributor m0mik commented Apr 11, 2014 Note that without specifying that the B210 uses "subdev=A:A" in the device string, the line "Using subdev spec 'A:A A:B'." in the output log below Therefore, does the compatibility issue vary from one daughter-board to another? Not finding the USRP with lsusb tells me this isn't a udev >>>> issue >>>> > but maybe I'm wrong.
Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Check This Out I am facing the "unable to find USRP " problem. Could that help? >>>> > Something else? >>>> >>>> The B200 falls back to USB2 if necessary. If everything appears to be configured correctly, it may be that your firewall is blocking connections. See what happens when you disable it.
It is likely that you do not have the permissions set correctly to allow your user account to have access to the USRP hardware. You plug your RTL-SDR into a different USB port and it is not recognised, or you connect a new device and it is not recognised This is a driver issue, and you will It's failing to open the control end point and can't load it's firmware. http://amazonfonts.com/unable-to/unable-to-find-rrd.html I also >>> tried a B210 on the machine that's not working and that didn't work >>> either.
This command instructs MATLAB to update its path to ensure that the Support Package files are included. Reply to this email directly or view it on GitHubhttps://github.com/csete/gqrx/issues/168#issuecomment-40245575 . If you are experiencing strange behaviour with your USRP® hardware and you are using this release of the software, updating the support package will likely fix any problems.
Your RTL-SDR is detected by the computer and appears to be outputting samples to either MATLAB or Simulink based receivers, but you are unable to receive signals you know to be present Try to solve any issues you encounter by interpreting the error messages. Therefore, inside the gnuradio directory, I gave the following commands: sudo make uninstallgit clean -d -x -f ./bootstrap./configuremake make checksudo make install ifconfig eth2 [email protected]:~/git/uhd# ifconfig eth2 192.168.10.1However, even this did The thing is, I was able to run the benchmark_rx.py and benchmark_tx.py codes in another UHD upgraded daughterboard.
Teodora Report post Edit Delete Reply with quote Forum List Topic List New Topic Search Register User List Log In Enable email notification | Enable multi-page view This topic is locked On Thu, Jan 8, 2015 at 10:38 AM, devin kelly via USRP-users < usrp-users at lists.ettus.com> wrote: > This is native. Powered by Redmine © 2006-2013 Jean-Philippe Lang Skip to content Ignore Learn more Please note that GitHub no longer supports old versions of Firefox. What's the >> output of "uname -a"? >> >> --Neel >> >> Also, since nobody else asked--is this *native* or in a VM? >> >> >> >> >> >> On Thu,
RTL-SDR Hardware Support Package USRP® Hardware Support Package Computer Performance OS X Compiler Errors Errors in the Exercise Material RTL-SDR Hardware Support Package ↖top You are trying to install the RTL-SDR Hardware Support e.g.: usrp_dev = usrp.open() <- instantiate device sink = usrp.sink(usrp_dev, ....) <- open source source = usrp.source(usrp_dev, .....) <- open sink similar for other sink/source devices that are used with GnuRadio. Looking through dmesg doesn't show anything >>>> > either. Still, if even lsusb can't >>>> find the device, there's nothing UHD can do.
I will try to figure out which part of benchmark_usb.py doesn't > close the ugen device. > The problem is that benchmark_usb.py opens usrp.sink() and usrp.source(), both which use the open() This prompted me to run the benchmark_usb.py script, which > unfortunately fails with the following message: > OK. pass -- Performing timer loopback test... Reload to refresh your session.
Please post the output of "lspci". Mike On Fri, Apr 11, 2014 at 8:41 PM, Alexandru Csete [email protected]: By default gr-osmosdr presents the device arguments returned by uhd::device::find() and I guess it is just unfortunate that the If the device is detected but not working, try reinstalling the Hardware Support Package before contacting Ettus Research support. Prolonged periods of use can cause the device to heat up, and the heat has been known to have an effect on the ICs.
A quick look at the bsd.c file from libusb-0.1.10a reveals that it tries to open files with names like these: /dev/usb* /dev/ugen* If this semi-informed guess doesn't work go to "Plan I am using gnuradio3.1.3. One solution to this problem for Simulink models is to replace the To Audio Device block with a To Multimedia File block, and save the demodulated audio signal for later playback. Errors in the Exercise Material ↖top We (the authors) have made our best attempt to ensure that there are no errors in the exercise material, and that the exercises are able to
We recommend upgrading to the latest Safari, Google Chrome, or Firefox.