Re: [Discuss-gnuradio] fft sink x-axis units

2006-12-01 Thread Dan Halperin
Eric Hill Matlis wrote: Thanks for the response. I guess my question is: where is that information carried? Is it in the definition of the source? The two definitions of the sinks look virtually identical to me: am_rcv.py: pre_demod = fftsink.fft_sink_c (self, panel,

Re: [Discuss-gnuradio] fft sink x-axis units

2006-12-01 Thread Eric Hill Matlis
Thanks for the response. I guess my question is: where is that information carried? Is it in the definition of the source? The two definitions of the sinks look virtually identical to me: am_rcv.py: pre_demod = fftsink.fft_sink_c (self, panel, title="Pre-Demodulation"

Re: [Discuss-gnuradio] fft sink x-axis units

2006-12-01 Thread Eric Blossom
On Fri, Dec 01, 2006 at 03:53:36PM -0500, Eric Hill Matlis wrote: > I'm trying to figure out how the x-axis units work on the fftsinks. In > the application "am_rcv.py", the first plot shows the incoming data > plotted as an fft, however the units are centered about 0 kHz. In another > applica

[Discuss-gnuradio] fft sink x-axis units

2006-12-01 Thread Eric Hill Matlis
I'm trying to figure out how the x-axis units work on the fftsinks. In the application "am_rcv.py", the first plot shows the incoming data plotted as an fft, however the units are centered about 0 kHz. In another application, say usrp_wfm_rcv_pll.py the units are centered about the actual fre

Re: [Discuss-gnuradio] Transmit Frequencies

2006-12-01 Thread Thomas Schmid
From Ettus Inc.'s FAQ you can read that the BasicTX goes only up to about 50MHz because the DACs in the USRP run at 128MS/s. You would need some other hardware to upsample your output to 70MHz. Thomas On 12/1/06, Scott Meuleners <[EMAIL PROTECTED]> wrote: I am working on a project for a class

[Discuss-gnuradio] Transmit Frequencies

2006-12-01 Thread Scott Meuleners
I am working on a project for a class, and we have been using the FM transmit functions included with the examples, and we've run into a problem where we are unable to transmit on frequencies from about 40 to 80 MHz, the problem is that we would like to transmit at 72MHz. The errors amount to som

Re: [Discuss-gnuradio] SWIG 1.3.31 now required on the trunk

2006-12-01 Thread Eric Hill Matlis
And for those who want rpms, particularaly Fedora Core people, I've got binaries and source rpms at: www.nd.edu/~ematlis/z.gnuradio thanks, eric On Thu, 30 Nov 2006, Eric Blossom wrote: We've decided to require SWIG 1.3.31 to compile the trunk. We try to avoid upping the mininum rev level o

[Discuss-gnuradio] Transmitting Frequency

2006-12-01 Thread Scott Meuleners
I am working on a project for a class, and we have been using the FM transmit functions included with the examples, and we've run into a problem where we are unable to transmit on frequencies from about 40 to 80 MHz, the problem is that we would like to transmit at 72MHz. The errors amount to som

Re: [Discuss-gnuradio] SWIG 1.3.31 now required on the trunk

2006-12-01 Thread Eric Blossom
On Thu, Nov 30, 2006 at 06:22:30PM -0500, Lamar Owen wrote: > On Thursday 30 November 2006 18:01, Eric Blossom wrote: > > We've decided to require SWIG 1.3.31 to compile the trunk. > > Really. This makes support on anything older than bleeding edge very > difficult. No, not very difficult. You

Re: [Discuss-gnuradio] Scanning/Detecting Wifi

2006-12-01 Thread Berndt Josef Wulf
G'day Greg, I've updated pkgsrc/ham/gnuradio-core to 3.0.2nb1. It fixes a bug that I encountered in gr.firdes.band_reject() function. At least it returns the expected result :-) cheerio Berndt ___ Discuss-gnuradio mailing list Discuss-gnuradio@g