I tried reformatting the xml file based off the uhd_rfnoc_adder.xml file; 
however, I still get the same error. I’m not trying to throw any packets away 
so I cannot ignore the error. My block is expecting to take in a complex 32bit 
floats and output a 32 bit float.

From: USRP-users <usrp-users-boun...@lists.ettus.com> on behalf of Lars Kuger 
via USRP-users <usrp-users@lists.ettus.com>
Reply-To: Lars Kuger <l...@inets.rwth-aachen.de>
Date: Friday, August 2, 2019 at 10:14 AM
To: "usrp-users@lists.ettus.com" <usrp-users@lists.ettus.com>
Subject: Re: [USRP-users] Error 'Timeout on Chan 0'


Hello Kirsten,

I remember getting the same error message while developing a custom RFNoC 
block. I found the problem to be caused by the corresponding xml file which is 
located in the grc folder. I am not sure what part of the file exactly caused 
the error message (maybe the ordering of the parameters or tags within the 
parameters) but I eventually solved it by replacing the file with the xml file 
from a working block and modifying that one.

Best regards,
Lars


On 02.08.19 15:50, Leong, Kirsten - 0551 - MITLL via USRP-users wrote:
Hello,

I am using a USRP X310 and am using gnuradio companion to test a custom block. 
The current diagram flows as follows: File Source->RFNoC FIFO->custom 
block->complex to image->frequency sink. However, when I try to execute, I get 
the error ‘timeout on chan 0’. My testbench passes all 5 cases; I can read 
signals on the inputs and outputs of the noc block and the flow graph works 
once I remove my custom block. Where else should I be looking?

Thanks,
Kirsten



_______________________________________________

USRP-users mailing list

USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com>

http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Attachment: fmdemod_fmdemod.xml
Description: fmdemod_fmdemod.xml

_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to