Hi Eesa
I am not sure if this will help, but in some of our code where we reuse the
USRP in another thread, I only create the handle once and pass that to both
threads (instead of calling multi_usrp::make in each thread), something like:
uhd::usrp::multi_usrp::sptr pUSRP = uhd::usrp::multi_usrp:
I had customized RFDC IP block in the past, but I have re-installed UHD since
to try and resolve this transmit issue. I had just compiled it with the default
settings, except for my custom yml file and custom block. The only difference
is when I run with vs without the GUI option, without transm
On 08/06/2023 07:16, Leon Wabeke wrote:
Hi Eesa
I am not sure if this will help, but in some of our code where we
reuse the USRP in another thread, I only create the handle once and
pass that to both threads (instead of calling multi_usrp::make in each
thread), something like:
|uhd::usrp::
Hi Rob,
Yes, 0.57 degrees is definitely within my measurement error. But, shouldn't
the N321 synchronize the phase of the LO's too?
Is there documentation available of how to repeat the results in the
"Measured Performance" section of
https://kb.ettus.com/USRP_N320/N321_LO_Distribution (e.g. code
On 08/06/2023 21:41, Michael Toussaint wrote:
Hi Rob,
Yes, 0.57 degrees is definitely within my measurement error. But,
shouldn't the N321 synchronize the phase of the LO's too?
If you're sharing LOs, there's no "synchronizing the LOs". A single LO
is shared through a switching matrix to each
