Piotr Krysik wrote: > W dniu 05.05.2015 o 20:36, Martin Braun via USRP-users pisze: > > > On 04.05.2015 12:51, Piotr Krysik via USRP-users wrote: > > > > > Hi Martin, > > > > > > Do you maybe know what is the source of the problem? > > > > > > I remember that for example USRP N200 has a mechanism that turns off Tx > > > channel when the device don't get any data to transmit from the > > > controlling PC. After implementing a signal generator inside of FPGA it > > > caused problems. Workaround was to transmit some data to the device. > > > > > > Is the problem of similar nature in this case? > > > No, this is something else entirely. In essence, the radios used predate > > > RFNoC, so they behave differently than the other RFNoC blocks. We need > > > to change that, which we will do together with several other changes. > > > That should fix this issue. > > > > Cheers, > > Martin > > > > --- > > > > USRP-users mailing list > > USRP-users@lists.ettus.com > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > Hi all, > > I've hacked the FPGA code according to Ian's advice. In what I've done > DDC output (sample_rx) is feeded to DUC input. With simple > gnuradio-companion flowgraph that receives signal from the device and > sends any signal that will be replaced by DDC output - it works. Many > thanks Ian for pointing this signals to me. > > The hardest part was getting Xilinx tools to compile the FPGA code - the > outputted error messages tend to be rather cryptic (which is only one of > their multiple drawbacks btw.). > > Best Regards, > Piotr Hello This is very old thread but I would like to let anyone who might see it know that what is said in it “that you can’t make connection Rx -> Tx in RFNoC without hacking it” is no longer (for few years already) the case. Look at rfnoc_radio_loopback that does the Rx->Tx connection. Best Regards,\ Piotr Krysik