[Discuss-gnuradio] crude compiler for WaveData

2005-04-15 Thread Larry Doolittle
Guys - I took a first stab at an FX2 WaveData compiler, since I don't touch Microsoft-only software (GPIFTool) with a 3.048 meter pole. This attempt is good enough to recreate the WaveData definition in usrp1_gpif.c from the following "source code": -- cut here -- // GPIF Ctrl Outputs CTL 0

Re: [Discuss-gnuradio] _gnuradio_swig_python import error on Mac OS X

2005-04-15 Thread Eric Blossom
On Fri, Apr 15, 2005 at 04:58:17PM -0700, Jonathan Jacky wrote: > > I build gnuradio-core from the 2.5 tarball on Mac OS X. > > After make and make install completed without error messages, > I tried make check in my gnuradio-core-2.5. (I learned here in January > that on OS X, make install must

[Discuss-gnuradio] _gnuradio_swig_python import error on Mac OS X

2005-04-15 Thread Jonathan Jacky
I build gnuradio-core from the 2.5 tarball on Mac OS X. After make and make install completed without error messages, I tried make check in my gnuradio-core-2.5. (I learned here in January that on OS X, make install must precede make check). Every one of the qa_*.py checks fails with this same tr

Re: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Deqiang chen
From: Eric Blossom <[EMAIL PROTECTED]> To: Deqiang chen <[EMAIL PROTECTED]> CC: Discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec Date: Fri, 15 Apr 2005 12:52:54 -0700 On Fri, Apr 15, 2005 at 07:38:32PM +, Deqiang chen wrote: > Thanks, guys! >

Re: [Discuss-gnuradio] No module named wx - another data point

2005-04-15 Thread LRK
On Fri, Apr 15, 2005 at 01:44:52PM -0700, Eric Blossom wrote: > On Fri, Apr 15, 2005 at 02:33:38PM -0500, LRK wrote: > > > > Probably a clue here somewhere. > > > > 'import wx' fails but 'import wxversion' works > > > > Then I can select the version and get a different error: > > > > OK. D

Re: [Discuss-gnuradio] No module named wx - another data point

2005-04-15 Thread Eric Blossom
On Fri, Apr 15, 2005 at 02:33:38PM -0500, LRK wrote: > > Probably a clue here somewhere. > > 'import wx' fails but 'import wxversion' works > > Then I can select the version and get a different error: > OK. Does the version of python that the wxPython binary was built against match the ver

Re: [Discuss-gnuradio] USRP need antenna?

2005-04-15 Thread Eric Blossom
On Fri, Apr 15, 2005 at 01:41:08PM -0500, Suvda Myagmar wrote: > From FAQ on Ettus website I understood that one doesn't need rf > front-end to run basic experiments on USRP hardware. Is that correct > assumption? I have usrp main board and RX, TX daughterboards. I > thought this hw can tune int

RE: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Deqiang chen
note that I actually want to realize an eye diagram. And the previous email is how I like to realize it. Does anyone have others ways to realize an eye diagram? From: "Deqiang chen" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] CC: Discuss-gnuradio@gnu.org Subject: RE: [Discuss-gnuradio] Re: FSK now

Re: [Discuss-gnuradio] No module named wx - another data point

2005-04-15 Thread Ilia Mirkin
In my limited experience with this stuff, DO NOT install multiple versions of wxPython. Just have 2.5. -Ilia On Fri, 2005-04-15 at 14:33 -0500, LRK wrote: > Probably a clue here somewhere. > > 'import wx' fails but 'import wxversion' works > > Then I can select the version and get a differ

Re: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Eric Blossom
On Fri, Apr 15, 2005 at 07:38:32PM +, Deqiang chen wrote: > Thanks, guys! > Now I have another problem about how to use split the dat stream. > I would like to split a data stream, put it into parallel streams and > show these streams on > screen. Note that I would like to show these data stre

RE: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Deqiang chen
Thanks, guys! Now I have another problem about how to use split the dat stream. I would like to split a data stream, put it into parallel streams and show these streams on screen. Note that I would like to show these data streams together in a single window. Could any one give me a hint about how

[Discuss-gnuradio] No module named wx - another data point

2005-04-15 Thread LRK
Probably a clue here somewhere. 'import wx' fails but 'import wxversion' works Then I can select the version and get a different error: gr% python Python 2.4.1 (#2, Apr 12 2005, 10:46:06) [GCC 3.4.2 [FreeBSD] 20040728] on freebsd5 Type "help", "copyright", "credits" or "license" for more i

[Discuss-gnuradio] USRP need antenna?

2005-04-15 Thread Suvda Myagmar
From FAQ on Ettus website I understood that one doesn't need rf front-end to run basic experiments on USRP hardware. Is that correct assumption? I have usrp main board and RX, TX daughterboards. I thought this hw can tune into frequency spectrum up to 50 MHz, which means I can listen AM radio

[Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Eric Blossom
On Fri, Apr 15, 2005 at 03:37:27PM +, Deqiang chen wrote: > hello, Eric, > > I remembered there is an annoucement that FSK can work at 100kbps. > So I dig it out and take a look at the source code for the FSK ( > fsk_rx.py) . I am a little surprised > that there are no time recovery there. >

Re: [Discuss-gnuradio] No module named wx

2005-04-15 Thread Robert McGwier
Fails at work on my SUSE 9.2 install and succeeds at home on my SUSE 9.2 install. Running python 2.3.4 at home and Python 2.4.1 at work. However, I just installed 2.4.1 at work. I got the same error messages before today with 2.3 first in the path. Having 2.4.1 first seems not to have helped (

Re: [Discuss-gnuradio] No module named wx

2005-04-15 Thread John Clark
Angilberto Muniz Sb wrote: Similar situation down here in Brazil, but after adding the softlink it complains with "file not found..." or something similar... Any tips on where to put some break code to help debug the issue? Rgrds, Angilberto. While I don't have any further specific information, I h

Re: [Discuss-gnuradio] Basic Tx works with USRP and usrp_siggen.py

2005-04-15 Thread Matt Ettus
Quoting Anastasopoulos Achilleas <[EMAIL PROTECTED]>: > I hooked up an analog osciloscope on the Basic Tx daughterboard and tested > the usrp_siggen.py. It seems to work! > > A couple of questions: > > 1) what are the units of amplitude? (the default is 16e3) The signal into the USRP is a 16-bit

[Discuss-gnuradio] Basic Tx works with USRP and usrp_siggen.py

2005-04-15 Thread Anastasopoulos Achilleas
I hooked up an analog osciloscope on the Basic Tx daughterboard and tested the usrp_siggen.py. It seems to work! A couple of questions: 1) what are the units of amplitude? (the default is 16e3) 2) why does the amplitude change if I change the frequency? I guess it is related to a constant mult

Re: [Discuss-gnuradio] No module named wx

2005-04-15 Thread Eric Blossom
On Fri, Apr 15, 2005 at 06:22:23AM -0700, Angilberto Muniz Sb wrote: > Similar situation down here in Brazil, but > after adding the softlink it complains with > "file not found..." or something similar... > > Any tips on where to put some break code to help debug > the issue? > > Rgrds, > > Ang

Re: [Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Matt Ettus
Quoting Deqiang chen <[EMAIL PROTECTED]>: > hello, Eric, > > I remembered there is an annoucement that FSK can work at 100kbps. > So I dig it out and take a look at the source code for the FSK ( fsk_rx.py) > . I am a little surprised > that there are no time recovery there. My understanding is tha

[Discuss-gnuradio] Re: FSK now (really) working at 100kbit/sec

2005-04-15 Thread Deqiang chen
hello, Eric, I remembered there is an annoucement that FSK can work at 100kbps. So I dig it out and take a look at the source code for the FSK ( fsk_rx.py) . I am a little surprised that there are no time recovery there. My understanding is that for fsk, if you use noncoherent demodulation, you w

Re: [Discuss-gnuradio] still no luck with FM reception on 4937

2005-04-15 Thread Matt Ettus
Quoting Anastasopoulos Achilleas <[EMAIL PROTECTED]>: > > As I mentioned in a previous email, > using the "tv_wfm_rcv.py" from the latest tarballs > I get an error when decim=250 saying > > usrp_standard_rx::set_decim_rate: WARNING rates > 128 result in incorrect > gain. Ignore that in this case,

[Discuss-gnuradio] still no luck with FM reception on 4937

2005-04-15 Thread Anastasopoulos Achilleas
As I mentioned in a previous email, using the "tv_wfm_rcv.py" from the latest tarballs I get an error when decim=250 saying usrp_standard_rx::set_decim_rate: WARNING rates > 128 result in incorrect gain. Now I changed the decimation to decim = 100 (which is a "valid" decimation rate according to

Re: [Discuss-gnuradio] No module named wx

2005-04-15 Thread Angilberto Muniz Sb
Similar situation down here in Brazil, but after adding the softlink it complains with "file not found..." or something similar... Any tips on where to put some break code to help debug the issue? Rgrds, Angilberto. --- [EMAIL PROTECTED] wrote: > I fixed it by adding the following softlink: >

Re: [Discuss-gnuradio] failed to find urb in pending_rqsts: (nil)

2005-04-15 Thread Harald Welte
Thanks for your response, Eric. On Thu, Apr 14, 2005 at 04:05:49PM -0700, Eric Blossom wrote: > > Does anyone have an idea what's going on? > > Haven't seen this before. seems to be a kernel bug in 2.6.12-rc2, where REAPURB[NDELAY] can return NULL pointers. Greg KH's kurrent patchest on top of