@robin, I reset the usrp clock to zero right before creating my threads, I also
tried your suggestion of starting transmit much later, but once transmits
start, I get underflows, so same problem. It doesn't look like transmitting
later helps.
@marcus, i've tried running on UHD 3.10.2, but I
On 08/14/2017 08:27 PM, Jason W Zheng via USRP-users wrote:
I don't think the problem is in the metadata, unless I'm really doing
it wrong. I've tried the suggestion you put out earlier, modeling my
code after the example txrx_loopback_to_file. The first packet has a
startofburst = true and
I don't think the problem is in the metadata, unless I'm really doing it wrong.
I've tried the suggestion you put out earlier, modeling my code after the
example txrx_loopback_to_file. The first packet has a startofburst = true and
subsequent packets have the start_of_burst value and the
I think some of the issue here as well is the tx_metadata.
For continuous streaming, the first packet ONLY should have startofburst = true…
Further packets after the first one should have startofburst = false, cuz they
really are not start of burst, they are continuations of the initial
Hi Jason,
I have the same under-run problem with my project. I use x310 as well. I
don't have a solution. I'll appreciate it if anyone can figure out what is
causing this.
Regards,
Edwin
Jason W Zheng via USRP-users 于2017年8月14日周一
下午2:42写道:
> Hi Robin, Marcus
>
>
Willing to bet significant money your tx thread is being put on the physical
processor that does not have your NIC card attached to it...
Then, all data must go over QPI between processors.
NUMA is not good for this.
You can experiment with affinity to make sure things are all on the same
On 08/14/2017 02:48 PM, Jason W Zheng wrote:
Hi Marcus, Robin,
I've set the tx_metadata, yet the issue still occurs. There are
constant streams of underruns when receiving and transmitting on the
same channel.
I've attached the code
One thing I notice, and forgive me if I'm just missing
I'm running on a server with 2 Intel Xeon E5-2650 v4, CPU is listed here:
https://ark.intel.com/products/91767/Intel-Xeon-Processor-E5-2650-v4-30M-Cache-2_20-GHz
The network card I'm using is the recommended Intel X520-DA2
I also have over 500 gigs of ram, so that is not an issue
I don't think
How should I set the tx metadata? My application will essentially stream
continuously.
Thanks,
Jason
From: ROBIN TORTORA
Sent: Monday, August 14, 2017 11:17:07 AM
To: Jason W Zheng via USRP-users; Jason W Zheng
Subject: Re: [USRP-users]
I dont see you setting the tx metadata object members to any values, so you are
essentially going to tx with default metadata IF there is a constructor that
initializes all the members to a consistent value...
> On August 14, 2017 at 1:56 PM Jason W Zheng via USRP-users
>
What are the specs on your computer? What type of 10GiG interface card
are you using?
On 2017-08-14 13:56, Jason W Zheng via USRP-users wrote:
> Since I haven't gotten a response in a week, I thought some source code might
> help. I've removed any buffer dependencies leaving just the receive
Since I haven't gotten a response in a week, I thought some source code might
help. I've removed any buffer dependencies leaving just the receive thread and
transmit thread. The receive thread is constant receiving to a buffer, while
the transmit thread is constantly transmitting 0s from
Hi,
I'm building an application where I receive data from the x310, process the
data, then transmit it out. I have 3 separate threads running, one for each
task. The receive task is constantly receiving data from the x310 at 200MS/s
and putting it into a buffer. The process task takes data
13 matches
Mail list logo