[USRP-users] Re: Continuous stream receive process

On 17/02/2023 20:45, Anil Gurses wrote: I think I found the answer. In this document , it states that "/As soon as streaming starts, the uhd::rx_streamer::recv() call needs to be called regularly to accept the incoming data. If recv() is not cal

[USRP-users] Re: Continuous stream receive process

I think I found the answer. In this document , it states that "*As soon as streaming starts, the uhd::rx_streamer::recv() call needs to be called regularly to accept the incoming data. If recv() is not called often enough, the device can overrun and

[USRP-users] Re: Saving TimeStamps and Metadata

On 17/02/2023 19:13, jmalo...@umass.edu wrote: Hello, I have an application where I collect I burst of samples from Rx ports, and stream the samples into my host computer. I would like to also store the timestamps from the packages onto the host computer, as well as store from which RX port

[USRP-users] Re: Saving TimeStamps and Metadata

Hi Joe, You need to create a stream first and set the stream mode, num_samps, and time spec (when to start receiving). After setting that, you need to receive samples from the stream object. By doing this, you will be providing rx_metada_t to recv function which will give you the information you n

[USRP-users] Saving TimeStamps and Metadata

Hello, I have an application where I collect I burst of samples from Rx ports, and stream the samples into my host computer. I would like to also store the timestamps from the packages onto the host computer, as well as store from which RX port the signal arrived so I may separate the data in d

[USRP-users] Re: Continuous stream receive process

On 17/02/2023 14:14, Anil Gurses wrote: Do you know any documentation about USRP continuous streaming? It might be more useful if I check those documents. I couldn't find anything about it in the UHD/USRP manual. A. When you create a streamer, you tell it what type of streaming you wish to d

[USRP-users] Re: Continuous stream receive process

Do you know any documentation about USRP continuous streaming? It might be more useful if I check those documents. I couldn't find anything about it in the UHD/USRP manual. A. On Fri, Feb 17, 2023 at 2:06 PM Marcus D. Leech wrote: > On 17/02/2023 14:00, Anil Gurses wrote: > > > Thanks for your

[USRP-users] Re: Continuous stream receive process

On 17/02/2023 14:00, Anil Gurses wrote: Thanks for your quick response! In general, your application absolutely, positively, needs to call recv() to consume samples as fast as they're produced, on average.    Short-term shortfalls are "soaked up" by buffers, but if your applicat

[USRP-users] Re: Continuous stream receive process

Thanks for your quick response! In general, your application absolutely, positively, needs to call > recv() to consume samples as fast as they're produced, on average. >Short-term shortfalls are "soaked up" by buffers, but if your > application cannot "keep up", no amount of buffering will sav

[USRP-users] Re: Continuous stream receive process

On 17/02/2023 13:34, Anil Gurses via USRP-users wrote: Hi all, I have a simple question about the continuous stream. As you all know, USRP RX lights indicate whether it's receiving samples or not. On continuous streaming, these lights are turned on if the recv function is called from the host

[USRP-users] Continuous stream receive process

Hi all, I have a simple question about the continuous stream. As you all know, USRP RX lights indicate whether it's receiving samples or not. On continuous streaming, these lights are turned on if the recv function is called from the host computer(stay on until the end of recv function call). In t

[USRP-users] USRP E320 DMA

Hi everyone, I have a problem with DMA. I am trying to build a custom RFNoC block which finds pulse parameters (pulse width, pulse repetition interval and frequency) and stores them in a block ram. I have built it and it worked in simulation. The problem is I wanna read those parameters from the ho