Looks like I failed to copy the list. To expand a little more on this -
setting decimation rates less than 8 with the current code on my machine
results in a screen-full of 'S’s, and I still see them occasionally
with decim = 8. Right now I’m experimenting with usrp2_rx_file.py to
record the 25MS/s to a dumpfile, and then try processing them offline.
-------- Original Message --------
Subject: Re: [Discuss-gnuradio] USRP2 - 25MS/s
Date: Fri, 05 Dec 2008 16:36:43 -0600
From: Douglas G. [email protected]
To: Matt E. [email protected]
References: [email protected]
Matt E. wrote:
25 MS/s is a very high data rate to keep up with. If you were to just
run a 40 tap FIR filter you would easily be eating up half of a
processor. I haven’t looked at it, but the 802.11b code is bound to use
more processing than the fft display does.
Does the bbn code accept other decimation rates? you could try 5 or 6.
Makes sense - I knew that was a lot of data. It does look like I’m using
70% of cpu with decim = 8. I’ll try decimation rates in-between - I
think the main thing that would need changing in that case is the
samples per bit.