On 05/23/2019 05:39 AM, Vladica Sark via USRP-users wrote:
Hi again,
I found an easy way to reproduce the problem. I use two x310's and run
the tx_timed_samples as:
tx_timed_samples --args "addr0=192.168.50.2,addr1=192.168.130.2"
--secs 0.5 --nsamps 1000000
sometimes it fails, sometimes it works. I use larger number of samples
to be able to notice the LED blinking.
BR,
Vladica
Are you getting any under-run indication? What type of ethernet
interface are you using, and at what sample rates?
On 23.05.19 08:36, Vladica Sark wrote:
Hi folks,
I have 2x X310 connected to Octoclock (10 MHz + PPS), each with 2x
UBX frontends. I control them from a C/C++ program. Since there are 4
channels, I create 4 tx streamers in order to transmit timed samples
on each of them. The transmissions are not at the same time and this
is the reason for using 4 tx streamers. The problem is that when I
schedule timed transmissions on all of the channels (at the same time
for test), sometimes I do not get anything with recv_async_msg, i.e.
the timeout expires. This also happens even when I schedule only a
single transmission from single tx streamer (all 4 streamers are
created).
Sometimes it happens that everything is working without problems,
i.e. I make 200 transmissions on each of the channels and I get the
proper response from the recv_async_msg, but many times, restarting
the same program leads to just recv_async_msg with expired timeout. I
am using UHD 3.13.0.
I can probably use one streamer and transmitting 0's on the rest of
the channels, but I would like to avoid LO leakage in the air.
Best regards,
Vladica
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com