Re: [Discuss-gnuradio] RuntimeError: bad lexical cast: source type value could not be interpreted as target

2010-12-02 Thread Tobias Schmid
Hello, sorry I had been out of office for some days. When I run uhd_usrp_probe the error doesn't occur. And using uhd.single_usrp_source doesn't occur either. The complete output of the terminal is: linux; GNU C++ version 4.4.1 [gcc-4_4-branch revision 150839]; Boost_103900; UHD_0001.20101124

Re: [Discuss-gnuradio] usrp_fft.py question and benchmark related question

2010-12-02 Thread John Andrews
Got it. Saw the earlier message too. Thanks On Thu, Dec 2, 2010 at 12:12 PM, John Andrews wrote: > > > On Wed, Dec 1, 2010 at 5:14 PM, Eric Blossom wrote: > >> On Wed, Dec 01, 2010 at 04:57:11PM -0600, John Andrews wrote: >> > Hi, >> > Can we change the DDC value to 0 in usrp_fft.py? Why is th

Re: [Discuss-gnuradio] costas_loop_cc ()

2010-12-02 Thread John Andrews
Of course its the same file. If you are making any changes in the C++ file then you must compile it before you can see those changes. Did you do "make" and "make install" after your changes? On Thu, Dec 2, 2010 at 10:45 PM, Guanbo Zheng wrote: > Hi, > > I found that for CFO compensation, there i

Re: [Discuss-gnuradio] EEPROM Burning for WBX_NG

2010-12-02 Thread Marcus D. Leech
Now, I have done complete new installation of Fedora-13, and installed all the dependencies as mentioned in build guide. After that i have run git and cloned gnuradio to get latest source. after that i have run # ./bootstrap # ./configure # make # make check # sudo make install I have coll

[Discuss-gnuradio] costas_loop_cc ()

2010-12-02 Thread Guanbo Zheng
Hi, I found that for CFO compensation, there is the module named "costas_loop_cc ()" Use it in this way: gr.costas_loop_cc(alpha, beta, max_freq, min_freq, order) where I can find this C++ file? I search the files, only found one "gr_costas_loop_cc.cc" in ~/gnuradio-3.2.2/gnuradio-core/src/lib

Re: [Discuss-gnuradio] EEPROM Burning for WBX_NG

2010-12-02 Thread Sanjay Singh
Now, I have done complete new installation of Fedora-13, and installed all the dependencies as mentioned in build guide. After that i have run git and cloned gnuradio to get latest source. after that i have run # ./bootstrap # ./configure # make # make check # sudo make install I have collected

Re: [Discuss-gnuradio] always a spike on the FFT at the center frequency

2010-12-02 Thread Matt Ettus
On 12/01/2010 01:16 PM, William Cox wrote: Whenever I run the userp_fft.py script (USRP1, Ubuntu 10.04 and 10.10), there's almost always a large spike (10-20 db above the noise floor) at the center frequency. This is the same for all the daughter boards I've tried (WBX, LFRX, and BasicRX). Why is

Re: [Discuss-gnuradio] EEPROM Burning for WBX_NG

2010-12-02 Thread Jason Abele
On Thu, Dec 2, 2010 at 9:03 AM, Sanjay Singh wrote: > I have done complete new installation of Ubuntu 9.04 Jaunty and installed > Binary packege of GNURADIO(3.2.2). > Can any one tell me why wbx_ng daughterbord ID is missing. > Because GNUradio 3.2.2 was released before the WBX ... you will need

Re: [Discuss-gnuradio] USRP2 + WBX How to use a 32 MHz signal band?

2010-12-02 Thread Josh Blum
You should be able to setup an interpolating FIR filter to interpolate by two and to shift your signal up or down by fs. Run each channel though a filter (one up, one down) and add the resulting streams. The resulting stream will have 2fs of bandwidth. -Josh On 12/02/2010 03:05 PM, Vladutzzz wrot

Re: [Discuss-gnuradio] USRP2 + WBX How to use a 32 MHz signal band?

2010-12-02 Thread Vladutzzz
NIck, What do you mean by "mix one sideband up and the other down"? How would that go? Thanks Vlad. Nick Foster-4 wrote: > > On Wed, 2010-12-01 at 13:53 -0800, Vladutzzz wrote: >> The problem is that I am in the middle of a project, time is of the >> essence >> and I don't have time to start

Re: [Discuss-gnuradio] usrp_fft.py question and benchmark related question

2010-12-02 Thread John Andrews
On Wed, Dec 1, 2010 at 5:14 PM, Eric Blossom wrote: > On Wed, Dec 01, 2010 at 04:57:11PM -0600, John Andrews wrote: > > Hi, > > Can we change the DDC value to 0 in usrp_fft.py? Why is this not 0 as one > > would expect to input the center frequency same as the baseband > frequency; > > i.e. if I

Re: [Discuss-gnuradio] Invalid EEPROM error message with the WBX board

2010-12-02 Thread Marcus D. Leech
> > I have a USRP board with a WBX daughter board and when I run > ./usrp_benchmark_usb.py or any grc application like ./usrp_nbfm_ptt.py > > these warning messages appear: > Testing 2MB/sec... > Warning: Treating daughterboard with invalid EEPROM contents as if it > were a "Basic Tx." > Warning

[Discuss-gnuradio] EEPROM Burning for WBX_NG

2010-12-02 Thread Sanjay Singh
I have done complete new installation of Ubuntu 9.04 Jaunty and installed Binary packege of GNURADIO(3.2.2). I have checked under usrpm folder usrp_dbid.py file. Following are the lines in the file # # Machine generated by gen_usrp_dbid.py from usrp_dbid.dat # Do not edit by hand. All edits will

Re: [Discuss-gnuradio] Gnu-radio + USRP problem

2010-12-02 Thread Thunder87
About this topic about increasing DSP speed with FFTW optimization: http://elinux.org/BeagleBoard/GSoC/2010_Projects/FFTW#Build_Instructions three things are bothering me at the moment: a) topic is for http://gitorious.org/gsoc2010-fftw-neon source, but there is a newer http://gitorious.org/~tjz

[Discuss-gnuradio] Re: ofdm decoder problem on USRP2

2010-12-02 Thread Guanbo Zheng
I have found out the meaning of "S" and "Time out": >From here: http://www.ruby-forum.com/topic/203035 Thank you Tom! :) On Wed, Dec 1, 2010 at 8:39 PM, Guanbo Zheng wrote: > Hi, > > I am trying to build the OFDM decoder on GRC based on the FTW 802.11a/g > encoder. > > At the USRP2 receiver,

[Discuss-gnuradio] Invalid EEPROM error message with the WBX board

2010-12-02 Thread Daniel Keler
I have a USRP board with a WBX daughter board and when I run ./usrp_benchmark_usb.py or any grc application like ./usrp_nbfm_ptt.py these warning messages appear: Testing 2MB/sec... Warning: Treating daughterboard with invalid EEPROM contents as if it were a "Basic Tx." Warning: This is almost ce