[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Grc RFNOC block error

From: Nikos Balkanas
Subject: Re: [Discuss-gnuradio] Grc RFNOC block error
Date: Sat, 12 Mar 2016 01:26:49 +0200

Thanks Jonathan,

That helps a lot. I still don't get a spectrum, but I get a nice fosphor panel and no timeout errors. A couple of questions:

1) You seem to be using 2 ffts: RFNoC FFT and RFNoC Fosphor. You can only do 1 FFT. What's the difference between those 2?
2) You start with an RFNoC Radio instead of a USRP source. Does that mean that the flow is intended to run from the FPGA? What is the meaning of the QT display in such a scenario?


On Sat, Mar 12, 2016 at 12:52 AM, Jonathon Pendlum <address@hidden> wrote:
Hi Nikos,

Have you tried running the example fosphor flowgraph in gr-ettus/examples/rfnoc?


On Fri, Mar 11, 2016 at 2:14 PM, Nikos Balkanas <address@hidden> wrote:
Upon closer inspection I do get a few runtime errors:

timeout on chan 0

Looks like smt is amiss in my flow. Any ideas about that?


On Sat, Mar 12, 2016 at 12:07 AM, Nikos Balkanas <address@hidden> wrote:
Tyvm Jason,

That did it. I don't actually need to set the X300's addr and type to anything. It defaults to the first one it finds, and I got only 1 ;-)
I got the top block running without any errors. Not much of a fosphor display, like I'm used to, but I'm happy i didn't get any errors:)


On Fri, Mar 11, 2016 at 5:13 PM, Jason Matusiak <address@hidden> wrote:
(accidentally sent original response to the wrong mailing list. sorry)

Nikos, All RFNoC scripts require a Device3 block.  If you look under UHD>RFNoC in GRC you will see Device3.  Just add that to your design (no connections needed) and if you are using an X310, set your device argument to "addr=xx.yy.zz.aa" and device address to "type=x300".

Make sense?

Discuss-gnuradio mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]