On Fri, Dec 6, 2024 at 9:44 AM Rob Kossler <rkoss...@nd.edu> wrote:
> > > On Fri, Dec 6, 2024 at 6:27 AM Nidhi Panda <nidhi.pa...@cyronics.com> > wrote: > >> I am currently working with a *USRP N300 device with uhd 4.7 and gnu >> radio v3.11.* I have created a simple loopback configuration in which >> the data flows through the following blocks: >> Rx_Radio > DDC > DMAFifo > DUC > Tx_Radio. >> However, I am encountering an issue where *only the receiver is working*, >> and the *transmitter is not starting*. My objective is to *receive data* and >> * transmit it back* without using *host-side streamers*, i.e., I intend >> to handle everything on the RFNoC hardware blocks directly. >> I have set the configuration for the transmitter using the RadioControl >> blocks >> (as shown in the attached script), but I am unable to start the >> transmitter. It seems that the transmitter is not getting activated or >> streaming, even though the receiver works correctly. >> >> You might want to look at the Ettus c++ example "rfnoc_radio_loopback". > You could also try just running it. Note that it does not include the > DMAFifo block but it does allow you to choose which Rx Radio and Tx Radio > block to use. After quickly reviewing your attachment, I would mention that > you shouldn't have to send Tx streaming commands. Once you send the Rx > streaming command, the data will flow. However, if you use a "timed" > receive command, then the streaming data will have a time tag such that > when it arrives at the Transmit radio, it will by definition be late. You > will need to do one of the following: either use non-timed receive > streaming commands or else create a custom RFNoC block that manipulates the > time tag to add some delay in order to account for the number of clock > cycles that it takes for the data to propagate from Rx to Tx. > > And, one question for the Ettus dev team: is there an easy way to configure this kind of graph such that the host will receive the "Late" messages? Since the host is not involved in the streaming, it's not obvious to the user that all of the streaming is arriving Late to the Tx radio as it would be in a host-based streaming application. But, it would be nice if the host did receive these Late (or Underrun) messages (at least in many situations).
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
