One trick with the FFT block I think is that the packet size needs to match
the FFT size. Try something like:
radio = uhd.rfnoc.RadioControl(graph.get_block("0/Radio#0"))
radio.set_properties("spp=" + str(fft_size))
Wade
On Sat, Jan 7, 2023 at 12:11 PM Piotr Krysik <[email protected]> wrote:
> Hello,
>
> Does anybody have a working example of usage of FFT RFNoC block on X410?
>
> Recent example for other USRP i.e. X310 would also be quite good.
>
> I followed the description here:
> https://kb.ettus.com/Getting_Started_with_RFNoC_in_UHD_4.0
> to add the fft block (I've attached my changed RFNoC's YML).
> Here are my additions to stock rfnoc image core yml
> (x410_200_rfnoc_image_core.yml):
>
> stream_endpoints:
> ep_fft:
> ctrl: False
> data: True
> buff_size_bytes: 32768
>
> noc_blocks:
> fft0:
> block_desc: 'fft_1x64.yml'
>
> connections:
> # FFT Blocks Connections
> - { srcblk: ep_fft, srcport: out0, dstblk: fft0, dstport: in_0 }
> - { srcblk: fft0, srcport: out_0, dstblk: ep_fft, dstport: in0 }
>
> clk_domains:
> - { srcblk: _device_, srcport: radio_2x, dstblk: fft0, dstport:
> ce }
>
> When I use FFT block I don't get any samples (checked with Wireshark)
> - I get only timeout errors and information about overflows.
>
> I've attached an example Python code. The same result is obtained in GNU
> Radio.
>
> Probably there is something wrong with the FFT block, but I don't know
> what it might be exactly. I've tried to use different clock rate
> ('radio' clock)
> but without success.
>
> --
> Best Regards,
> Piotr Krysik
> _______________________________________________
> USRP-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
