Re: [Discuss-gnuradio] DVB-T Reception Problem

A Series of D is usually even worse than O.
Does that happen, too, if you just record samples for later processing?
If it happens when recording, too, what about just connecting the USRP
source to a null sink?
Also: what is your network hardware (if you're on Linux, ask "lscie|grep
-i net")?

>dual core with 4gb of ram
hard to say. OFDM decoding and all the synchronization aren't trivial,
and "dual core" doesn't really say much. My 2007 dual core backup PC
sure won't be up to the job, whereas two cores of my current PC might be
sufficient. What's more important is that it's nearly impossible to
predict how well the flow graph will behave on your specific CPU/network
hardware/OS/network driver/... combination.
Personally, for software development, 4GB RAM sounds like a minimum, and
I'd have to look really hard to find a CPU that's not dual core nowadays.


Best regards,
Marcus

On 18.12.2015 08:00, ahsan.ali@studium.fau.de wrote:
> Hi all..Thanks Ron and Federico for your replies. Federico I am now using
> a USRP N210 to do the recording. The console doesn't outputs any 'O's but
> instead it outputs a series of 'D's. Now I am also getting synchronized
> when I use a live signal but after few samples my Gnu Radio's light is dim
> and my synchronization is also lost and there is a big series of 'D's on
> my console.Do you think its a problem of my machine?(dual core with 4gb of
> ram).
>
> Regards
> Ahsan
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio