discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] gnuradio LISBUSB error (but username is configure


From: Cinaed Simson
Subject: Re: [Discuss-gnuradio] gnuradio LISBUSB error (but username is configured for plugdev and USB use)
Date: Thu, 26 Jan 2017 15:41:55 -0800
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.6.0

On 01/26/2017 05:28 AM, Sonny Rajagopalan wrote:
> I made those changes and I still get the same error.

What changes? There was no grc file attached to this message.

> Should I be getting
> a LIBUSB error when I do something the HackRF doesn't approve?

If you can run

  hackrf_info

without any problem, then you have all the permissions you need to
communicate with the device.

Look at the end of the error messages - the error is:

  RuntimeError: list contains invalid format!

The libUSB error is a result of the parameters for the HackRF being
invalid - libUSB can't get started so it complains.

As long as you get the error message

   RuntimeError: list contains invalid format!

it's operator error.

-- Cinaed

> 
> On Wed, Jan 25, 2017 at 10:26 PM, Cinaed Simson <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     On 01/25/2017 02:01 PM, Sonny Rajagopalan wrote:
>     > Sorry didn't attach to group earlier.
>     >
>     > On Wed, Jan 25, 2017 at 4:19 PM, Cinaed Simson <address@hidden 
> <mailto:address@hidden>
>     > <mailto:address@hidden <mailto:address@hidden>>>
>     wrote:
>     >
>     >     On 01/25/2017 09:52 AM, Sonny Rajagopalan wrote:
>     >     > Hello,
>     >     >
>     >     > I have a hackrf board which I am able to use using gqrx
>     (using Ubuntu
>     >     > 14.04 LTS, gnuradio v3.7.10.1-182-g59136936). This, I guess,
>     confirms
>     >     > the permissions issue for accessing hackrf under my username.
>     >     >
>     >     > However, when I try to execute a flow graph I created using
>     >     > gnuradio-companion, it fails for the following reason:
>     >     >
>     >     > Generating:
>     >     '/mymachine/sdr/gnuradioProjects/flowGraphsFromGRC/top_block.py'
>     >     >
>     >     > Executing: /usr/bin/python2 -u
>     >     > /mymachine/sdr/gnuradioProjects/flowGraphsFromGRC/top_block.py
>     >     >
>     >     > linux; GNU C++ version 4.8.4; Boost_105400;
>     >     UHD_3.11.0.git-59-g52ca2e0b
>     >     >
>     >     > gr-osmosdr v0.1.x-xxx-xunknown (0.1.5git) gnuradio 3.7.10
>     >     > built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri
>     hackrf
>     >     > bladerf rfspace airspy soapy redpitaya
>     >     > Number of USB devices: 13
>     >     > USB device 1d50:0089: 0000000000000000909864c82c3a2fcf match
>     >     > Using HackRF One with firmware 2015.07.2
>     >     > gr-osmosdr v0.1.x-xxx-xunknown (0.1.5git) gnuradio 3.7.10
>     >     > built-in sink types: uhd hackrf bladerf soapy redpitaya file
>     >     > Number of USB devices: 13
>     >     > USB device 1d50:0089: 0000000000000000909864c82c3a2fcf match
>     >     >
>     >     > FATAL: Failed to open HackRF device (-1000) HACKRF_ERROR_LIBUSB
>     >     >
>     >     > Trying to fill up 1 missing channel(s) with null sink(s).
>     >     > This is being done to prevent the application from crashing
>     >     > due to gnuradio bug #528.
>     >     >
>     >     > Traceback (most recent call last):
>     >     >   File
>     >     "/mymachine/sdr/gnuradioProjects/flowGraphsFromGRC/top_block.py",
>     >     > line 128, in <module>
>     >     >     main()
>     >     >   File
>     >     "/mymachine/sdr/gnuradioProjects/flowGraphsFromGRC/top_block.py",
>     >     > line 117, in main
>     >     >     tb.start()
>     >     >   File
>     >     >
>     "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/top_block.py",
>     >     line
>     >     > 109, in start
>     >     >     top_block_start_unlocked(self._impl, max_noutput_items)
>     >     >   File
>     >     >
>     "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/runtime_swig.py",
>     >     > line 4879, in top_block_start_unlocked
>     >     >     return _runtime_swig.top_block_start_unlocked(*args,
>     **kwargs)
>     >     >
> 
>     The HackRF One is half duplex so it can't transmit and receive on the
>     same device at the same time.
> 
>     Also, the minimum RF frequency for the HackRF One I believe is roughly 1
>     MHz - you're trying to receive at 1 kHz in the osomcom source block.
> 
>     In addition, for the HackRF One, when receiving it's recommended you set
>     the RF gain to 0. To transmit, set it to 1.
> 
>     In other words, the RF gain is either off or on.
> 
>     See
> 
>        https://greatscottgadgets.com/sdr <https://greatscottgadgets.com/sdr>
> 
>     Lesson 5 is an introduction to the HackRF One.
> 
> 
> 
>     >     >
>     >     > Any help is appreciated.
>     >     >
>     >     > Thanks,
>     >     > Sonny.
>     >     >
>     >     >
>     >     > _______________________________________________
>     >     > Discuss-gnuradio mailing list
>     >     > address@hidden <mailto:address@hidden>
>     <mailto:address@hidden <mailto:address@hidden>>
>     >     > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>     >     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>>
>     >     >
>     >
>     >     You should post your grc file.
>     >
>     >     -- Cinaed
>     >
>     >     _______________________________________________
>     >     Discuss-gnuradio mailing list
>     >     address@hidden <mailto:address@hidden>
>     <mailto:address@hidden <mailto:address@hidden>>
>     >     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>     >     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>     <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>>
>     >
>     >
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]