This works a bit more effeciently in matching a usrp to the atsc code
(either all 0.9, or part 0.9 and part 2.x):
Instead of: collect data with usrp decim = 8, then interp by 5 (8Msps
to 40) then decim by 2 (40Msps to 20) while upshifting to 5.75MHz -
just collect data with decim = 10, then
On Wed, 2006-05-17 at 15:52 -0400, Charles Swiger wrote:
just collect data with decim = 10, then interp by 3 (6.4Msps to
19.2Msps), then upshift. The 0.9 code need two changes, one to
Some more fat can be squeezed out of the pipeline if the 'upshift
to 5.75MHz' and FPLL could be combined.
They also conveniently forget to deal with all the bane of all wideband
SDRs -- interfering signals in one band will, at best, decrease sensitivity
in other bands. 80dB SNDR is nowhere near enough to simultaneously
receive, say, GPS data and process CDMA phone calls without something like
a
sorry...can anyone tell me what is the specific meaning of the code
u0u0u0u0u0u0u0u0u0u0u0u.
that often appears in terminal when gr applications do not behave
properly.
thanks
vincenzo
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
--
Matt Ettus [EMAIL PROTECTED]
---BeginMessage---
Code:
u = usrp
a = audio
U = Underrun
O = Overrun
uU = USRP underrun -- Your TX application isn't sending data to the USRP
fast enough
uO = USRP overrun -- You RX application isn't receiving data from the
USRP fast enough
aO = audio
gr-usrp/src/usrp1_source_base.cc:106: fputs (uO, stderr);
This is generated by the USB, via a USRP source, when incoming data
can't be read fast enough and thus there is an overflow.
On Wednesday, May 17, 2006, at 09:02 PM, Vincenzo Pellegrini wrote:
sorry...can anyone tell me what is
[EMAIL PROTECTED] wrote:
On Wed, May 17, 2006 at 04:33:05PM -0700, Matt Ettus wrote:
SDR Forum is running a competition for university teams in software
radio. There are monetary prizes, and it looks like you get Matlab and
Simulink for free.
In other words, they think software radio is
