UHD readiness level?

Hi all-

Any estimate as to the readiness level of the UHD driver? (if
open-source
has such a concept…)
Back in April they were called “pre-alpha”. How are things progressing?
Do
you recommend use of it yet to people whose day-job would (lamentably)
prefer they be productive? :slight_smile:

As a checklist, could I use the UHD to:

-receive on a WBX card
-transmit on a WBX card
-alternate transmitting and receiving on a WBX card
-simultaneously receive with 2 WBXs in 1 USRP
-simultaneously receive with 1 WBX & 1 BasicRX on 1 USRP (even though
one
is quadrature and the other not)
-simultaneously receive with 4 WBXs in 2 USRPs
-transmit on a WBX while issuing tune commands to the card every 50ms to
perform freq hopping (could I expect more precise timing control over
the
hops than I had in python-land?)

Thanks, and keep up the good work!

Any estimate as to the readiness level of the UHD driver? (if open-source
has such a concept…)
Back in April they were called “pre-alpha”. How are things progressing? Do
you recommend use of it yet to people whose day-job would (lamentably)
prefer they be productive? :slight_smile:

The UHD is still being improved, and you can expect minor API changes
and additions. However, it is ready for production use and supports all
of the Ettus R. hardware as it stands now.

As a checklist, could I use the UHD to:

-receive on a WBX card

check

-transmit on a WBX card

check

-alternate transmitting and receiving on a WBX card

check

-simultaneously receive with 2 WBXs in 1 USRP

check

-simultaneously receive with 1 WBX& 1 BasicRX on 1 USRP (even though one
is quadrature and the other not)

This is a limitation of the mux in the FPGA fabric on USRP1. Unless you
specify a quadrature subdevice for the basic board, you will get this
warning:

“Mixing real and quadrature rx subdevices is not supported.\n”
“The Q input to the real source(s) will be non-zero.\n”

-simultaneously receive with 4 WBXs in 2 USRPs

There is nothing in the uhd to synchronize across USRP1s. But yes, you
can still do this with two independent source blocks each setup for dual
channel.

-transmit on a WBX while issuing tune commands to the card every 50ms to
perform freq hopping (could I expect more precise timing control over the
hops than I had in python-land?)

There is no “send a command at this time”. However, you do get greater
control of the tuning (and this applies to python land).

The tune_request struct allows for fine grained control of the tuning
across the RX and TX chains:
http://www.ettus.com/uhd_docs/doxygen/html/structuhd_1_1tune__request__t.html

So you can for example, tune by setting the DDC which is fast and
responsive and leave the daughter-board LO untouched which takes time to
settle.

-Josh

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs