On Wed, Feb 16, 2005 at 09:11:36PM -0600, David Carr wrote:
> Matt,
>
> >Yes, very true. It's not even the FFT part. That is really quick. Its
> >the
> >drawing of the graph. If anybody is interested, I think integrating
> >PGPlot
> >would help this issue a lot. It is supposed to be much fa
Matt,
Yes, very true. It's not even the FFT part. That is really quick. Its the
drawing of the graph. If anybody is interested, I think integrating PGPlot
would help this issue a lot. It is supposed to be much faster than wxPyPlot.
I just downloaded and installed PGPlot. The native interfa
Is it just me, or does anybody else think it would be a fine idea to
drop an in-line fuse into the power line along with bypassing the
soldered down fuse? Just in case there's actually a short somewhere in
the board that we really don't want to expose catastrophically.
On Wed, 2005-02-16 at
> Can I use any wire, or is there a specific gauge, etc., that I need to
> look for?
Any wire that can handle 3 amps.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
On Wed, Feb 16, 2005 at 12:57:17PM -0800, Matt Ettus wrote:
> Quoting Rahul Dhar <[EMAIL PROTECTED]>:
>>
>> The ohm meter says that nothing is going through the fuse. Is there a
>> special dance I can do to resurrect this thing?
>
>
> You must have shorted something. If you are certain you have
I've been working with fsk_tx and fsk_rx between a pair of usrp boards.
I've noticed that the fsk_tx has widely different behavior for different
settings.
On the nominal rx board, I run the fft display, expecting to see the same
fft as in the tx window.
What I see instead is pretty much noise.
Wh
Quoting Rahul Dhar <[EMAIL PROTECTED]>:
> On Tue, Feb 15, 2005 at 06:18:57PM -0800, Eric Blossom wrote:
> >
> > Pull out your trusty ohm meter and with the board unplugged from the
> > power supply, check continuity across the fuse F501. If you start at
> > the power connector and follow the trac
On Wed, Feb 16, 2005 at 03:42:00PM -0500, Rahul Dhar wrote:
> On Tue, Feb 15, 2005 at 06:18:57PM -0800, Eric Blossom wrote:
> >
> > Pull out your trusty ohm meter and with the board unplugged from the
> > power supply, check continuity across the fuse F501. If you start at
> > the power connector
> It would be useful to have a function that returned
> the as-aliased
> frequency for
> any given input frequency (up to the maximum input
> frequency of the A/D).
> Trivial, I suppose, but less opportunity for brain
> farts that way.
>
i tried with python but i'm better with php :)
here'
On Tue, Feb 15, 2005 at 06:18:57PM -0800, Eric Blossom wrote:
>
> Pull out your trusty ohm meter and with the board unplugged from the
> power supply, check continuity across the fuse F501. If you start at
> the power connector and follow the trace on the top, it's the first
> thing you run into.
Matt,
> Yes, very true. It's not even the FFT part. That is really quick. Its the
> drawing of the graph. If anybody is interested, I think integrating PGPlot
> would help this issue a lot. It is supposed to be much faster than wxPyPlot.
Because I like Tkinter more than wxPython I am playing
Quoting Marcus Leech <[EMAIL PROTECTED]>:
> It would be useful to have a function that returned the as-aliased
> frequency for
> any given input frequency (up to the maximum input frequency of the A/D).
> Trivial, I suppose, but less opportunity for brain farts that way.
A good idea.
Anyway
Quoting Achilleas Anastasopoulos <[EMAIL PROTECTED]>:
>
> I deactivated the three fftscopes that I had and now
> it works fine. The voice distortion was because the CPU
> could not handle the load. It is amazing how much CPU
> power the fftscopes consume...
>
Yes, very true. It's not even the FF
It would be useful to have a function that returned the as-aliased
frequency for
any given input frequency (up to the maximum input frequency of the A/D).
Trivial, I suppose, but less opportunity for brain farts that way.
Matt Ettus wrote:
Quoting mj <[EMAIL PROTECTED]>:
Am i missing somethi
I deactivated the three fftscopes that I had and now
it works fine. The voice distortion was because the CPU
could not handle the load. It is amazing how much CPU
power the fftscopes consume...
Thanks for the help
Achilleas
Eric Blossom wrote:
On Tue, Feb 15, 2005 at 07:59:45PM -0500, Achilleas Ana
Quoting mj <[EMAIL PROTECTED]>:
> > Am i missing something obvious?
> >
>
> Fixed it. the "freq1 = blah * 1e6" evaded me.
>
> Still not sure on how to receive 433Mhz if anyone
> knows.
As RF frequency rises from 0 to 32 MHz, the "digital" frequency goes from 0 to
32 MHz. As RF frequency goes fr
> >also... '31.3e6' is Radio2 here in the UK on
> 89.8MHz.
> >Is there an easy way to convert ddc into the actual
> >freq?
> >
> The freq is tuned to 5.75Mhz, so you might be
> getting
>
> 89.8 - 64 + 5.75 = 31.55 ?
>
> 64 Mhz is the usrp sample freq. 5.75 is the IF freq
> the script tunes to.
> Am i missing something obvious?
>
Fixed it. the "freq1 = blah * 1e6" evaded me.
Still not sure on how to receive 433Mhz if anyone
knows.
thanks.
> Also, the max ddc for usrp_fft.py is 32e6 so i'm
> assuming the maximum usrp rf frequency is 32Mhz???
> and
> the Radio2 wfm reception i'm receiv
thanks chuck. all sorted now.
mj
--- Chuck Swiger <[EMAIL PROTECTED]> wrote:
> At 01:57 AM 2/16/2005 -0800, you wrote:
> >Hey, can anyone shed some light on this? I can do
> air
> >captures to file and then listen to them, but I
> cannot
> >listen to the signal live. The first time I tried
> it
Hey, can anyone shed some light on this? I can do air
captures to file and then listen to them, but I cannot
listen to the signal live. The first time I tried it I
followed the instructions in the error about making a
/dev/parport0 to no effect.
./wfm_rcv.py 31.3e6
audio: using audio_alsa
usrp: fo
20 matches
Mail list logo
