Gr-airmodes with gnuradio. gr-osmosdr and bladerf

Hi,

gr-airmodes, gr-osmosdr, gnuradio and bladerf all with latest versions,
built directly from the repo.

modes_rx works just fine, the messages come through.

modes_gui throws this error, when switching insinde the gui to osmosdr:

[email protected]:~$ modes_gui
linux; GNU C++ version 4.6.3; Boost_104800;
UHD_003.005.003-164-g0c5099ab

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0
[bladeRF source] Using nuand LLC bladeRF #0 SN
8efd2b30699e61bec690a0b37cc5ad57 FW v1.5.3 FPGA v0.0.0
gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

The bladerf is flashed with latest fx3 image and latest fpga file into
the SPI flash.

All the involved packages itself work just fine.

Any ideas what there may be wrong?

Ralph A. Schmid
Mondstr. 10
90762 Frth
+49-171-3631223
[email protected]
http://www.bclog.de/

Does osmocom_fft work?

–n

Yes, works just fine, also other toolchains like gqrx gr-osmosdr
bladerf do not show any strange effects, so osmosdr seems to be OK.

Ralph

From: Nick F. [mailto:[email protected]]
Sent: Tuesday, 5 November, 2013 18:10
To: Ralph A. Schmid, dk5ras
Cc: GNURadio D.ion List
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and bladerf…

Does osmocom_fft work?

–n

On Tue, Nov 5, 2013 at 9:00 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

Hi,

gr-airmodes, gr-osmosdr, gnuradio and bladerf all with latest versions,
built directly from the repo.

modes_rx works just fine, the messages come through.

modes_gui throws this error, when switching insinde the gui to osmosdr:

[email protected]:~$ modes_gui
linux; GNU C++ version 4.6.3; Boost_104800;
UHD_003.005.003-164-g0c5099ab

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0
[bladeRF source] Using nuand LLC bladeRF #0 SN
8efd2b30699e61bec690a0b37cc5ad57 FW v1.5.3 FPGA v0.0.0
gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

The bladerf is flashed with latest fx3 image and latest fpga file into
the SPI flash.

All the involved packages itself work just fine.

Any ideas what there may be wrong?

Ralph A. Schmid
Mondstr. 10
90762 Frth
+49-171-3631223
[email protected]
http://www.bclog.de/

I’ve only tested osmocom in gr-air-modes with the HackRF. The relevant
code
is in python/radio.py lines 177-189. modes_gui does reinstantiate the
source block a couple of times (to populate the options boxes) – it’s
possible that this isn’t allowing gr-osmocom enough time to close/open
the
USB device, or maybe gr-osmocom doesn’t like reopening the device from
within the same process?

–n

On Tue, Nov 5, 2013 at 10:04 AM, Ralph A. Schmid, dk5ras

Im afraid I am not a programmer, so I do not know if I can find
something there, but I will have l look later or tomorrow J

Ralph.

From: Nick F. [mailto:[email protected]]
Sent: Tuesday, 5 November, 2013 19:14
To: Ralph A. Schmid, dk5ras
Cc: GNURadio D.ion List
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and bladerf…

I’ve only tested osmocom in gr-air-modes with the HackRF. The relevant
code is in python/radio.py lines 177-189. modes_gui does reinstantiate
the source block a couple of times (to populate the options boxes) –
it’s possible that this isn’t allowing gr-osmocom enough time to
close/open the USB device, or maybe gr-osmocom doesn’t like reopening
the device from within the same process?

–n

On Tue, Nov 5, 2013 at 10:04 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

Yes, works just fine, also other toolchains like gqrx gr-osmosdr
bladerf do not show any strange effects, so osmosdr seems to be OK.

Ralph

From: Nick F. [mailto:[email protected]]
Sent: Tuesday, 5 November, 2013 18:10
To: Ralph A. Schmid, dk5ras
Cc: GNURadio D.ion List
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and bladerf…

Does osmocom_fft work?

–n

On Tue, Nov 5, 2013 at 9:00 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

Hi,

gr-airmodes, gr-osmosdr, gnuradio and bladerf all with latest versions,
built directly from the repo.

modes_rx works just fine, the messages come through.

modes_gui throws this error, when switching insinde the gui to osmosdr:

[email protected]:~$ modes_gui
linux; GNU C++ version 4.6.3; Boost_104800;
UHD_003.005.003-164-g0c5099ab

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0
[bladeRF source] Using nuand LLC bladeRF #0 SN
8efd2b30699e61bec690a0b37cc5ad57 FW v1.5.3 FPGA v0.0.0
gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

The bladerf is flashed with latest fx3 image and latest fpga file into
the SPI flash.

All the involved packages itself work just fine.

Any ideas what there may be wrong?

Ralph A. Schmid
Mondstr. 10
90762 Frth
+49-171-3631223 tel:%2B49-171-3631223
[email protected]
http://www.bclog.de/

Just as a note, I also did not get the gui to work with my USRP1, the
error messages are different, but at least it did not receive.

Ralph.

From: Nick F. [mailto:[email protected]]
Sent: Tuesday, 5 November, 2013 19:14
To: Ralph A. Schmid, dk5ras
Cc: GNURadio D.ion List
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and bladerf…

I’ve only tested osmocom in gr-air-modes with the HackRF. The relevant
code is in python/radio.py lines 177-189. modes_gui does reinstantiate
the source block a couple of times (to populate the options boxes) –
it’s possible that this isn’t allowing gr-osmocom enough time to
close/open the USB device, or maybe gr-osmocom doesn’t like reopening
the device from within the same process?

–n

On Tue, Nov 5, 2013 at 10:04 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

Yes, works just fine, also other toolchains like gqrx gr-osmosdr
bladerf do not show any strange effects, so osmosdr seems to be OK.

Ralph

From: Nick F. [mailto:[email protected]]
Sent: Tuesday, 5 November, 2013 18:10
To: Ralph A. Schmid, dk5ras
Cc: GNURadio D.ion List
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and bladerf…

Does osmocom_fft work?

–n

On Tue, Nov 5, 2013 at 9:00 AM, Ralph A. Schmid, dk5ras
[email protected] wrote:

Hi,

gr-airmodes, gr-osmosdr, gnuradio and bladerf all with latest versions,
built directly from the repo.

modes_rx works just fine, the messages come through.

modes_gui throws this error, when switching insinde the gui to osmosdr:

[email protected]:~$ modes_gui
linux; GNU C++ version 4.6.3; Boost_104800;
UHD_003.005.003-164-g0c5099ab

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0
[bladeRF source] Using nuand LLC bladeRF #0 SN
8efd2b30699e61bec690a0b37cc5ad57 FW v1.5.3 FPGA v0.0.0
gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

The bladerf is flashed with latest fx3 image and latest fpga file into
the SPI flash.

All the involved packages itself work just fine.

Any ideas what there may be wrong?

Ralph A. Schmid
Mondstr. 10
90762 Frth
+49-171-3631223 tel:%2B49-171-3631223
[email protected]
http://www.bclog.de/

Ive used it quite lot with a variety of dongles, funcube and hackrf.
They
all work for me with variations on gain needed to produce reliable
results.
I did not try the interfaces to other programs such as google maps. I
found
that dump1090 gave me better data.

73,

Alan W6ARH

From: [email protected]n.invalid
[mailto:[email protected]n.invalid] On
Behalf Of
Ralph A. Schmid, dk5ras
Sent: Tuesday, November 05, 2013 9:52 PM
To: ‘Nick F.’
Cc: ‘GNURadio D.ion List’
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and
bladerf…

Just as a note, I also did not get the gui to work with my USRP1, the
error
messages are different, but at least it did not receive.

Ralph.

From: Nick F. [mailto:[email protected]]
Sent: Tuesday, 5 November, 2013 19:14
To: Ralph A. Schmid, dk5ras
Cc: GNURadio D.ion List
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and
bladerf…

I’ve only tested osmocom in gr-air-modes with the HackRF. The relevant
code
is in python/radio.py lines 177-189. modes_gui does reinstantiate the
source
block a couple of times (to populate the options boxes) – it’s possible
that this isn’t allowing gr-osmocom enough time to close/open the USB
device, or maybe gr-osmocom doesn’t like reopening the device from
within
the same process?

–n

On Tue, Nov 5, 2013 at 10:04 AM, Ralph A. Schmid, dk5ras
[email protected]
wrote:

Yes, works just fine, also other toolchains like gqrx gr-osmosdr
bladerf do not show any strange effects, so osmosdr seems to be OK.

Ralph

From: Nick F. [mailto:[email protected]]
Sent: Tuesday, 5 November, 2013 18:10
To: Ralph A. Schmid, dk5ras
Cc: GNURadio D.ion List
Subject: Re: [Discuss-gnuradio] gr-airmodes with gnuradio. gr-osmosdr
and
bladerf…

Does osmocom_fft work?

–n

On Tue, Nov 5, 2013 at 9:00 AM, Ralph A. Schmid, dk5ras
[email protected]
wrote:

Hi,

gr-airmodes, gr-osmosdr, gnuradio and bladerf all with latest versions,
built directly from the repo.

modes_rx works just fine, the messages come through.

modes_gui throws this error, when switching insinde the gui to osmosdr:

[email protected]:~$ modes_gui
linux; GNU C++ version 4.6.3; Boost_104800;
UHD_003.005.003-164-g0c5099ab

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0
[bladeRF source] Using nuand LLC bladeRF #0 SN
8efd2b30699e61bec690a0b37cc5ad57 FW v1.5.3 FPGA v0.0.0
gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

gr-osmosdr v0.1.0-40-ge1b699fd (0.1.1git) gnuradio
3.7.2git-149-g0993c1b0
built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf netsdr
[INFO] Instance: 0

FATAL: [bladeRF source] Failed to open bladeRF device libusb:instance=0

Trying to fill up 1 missing channel(s) with null source(s).
This is being done to prevent the application from crashing
due to a gnuradio bug. The maintainers have been informed.

The bladerf is flashed with latest fx3 image and latest fpga file into
the
SPI flash.

All the involved packages itself work just fine.

Any ideas what there may be wrong?

Ralph A. Schmid
Mondstr. 10
90762 Frth
+49-171-3631223 tel:%2B49-171-3631223
[email protected]
http://www.bclog.de/


Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3426 / Virus Database: 3222/6812 - Release Date:
11/05/13

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs