On 10/23/2019 03:56 PM, Sam Reiter via USRP-users wrote:
Carlos,
You're correct that currently we can't currently use a TwinRX and a
UBX in the same chassis without running into sample rate / tick rate
conflicts. I would guess that this would extend to a chassis with UBX
boards and a chassis with TwinRX boards if they're encapsulated in the
same multi-usrp object AND streamer. I haven't tried it myself, but I
have a feeling that you might be able to run things correctly if you
split each X310 out into its own streamer (benchmark rate uses a
single streamer).
-Sam
Indeed, one of the inherent properties of a multi_usrp object is that it
does sample-timestamp alignment, which is not possible when the
samples in a stream have timestamps that originate in a different
timestamp tick-rate.
On Tue, Oct 22, 2019 at 9:33 AM Carlos Bocanegra via USRP-users
<[email protected] <mailto:[email protected]>> wrote:
Hi all,
Can we have daughterboards TwinRX and UBX working under the same
multiUSRP object? For instance, two TwinRX attached to one USRP
and two UBX attached to another USRP creating 6 synchronized and
phased aligned receiver channels?
The discussion below stated that the sampling rate mismatch
(100Msps for the TwinRX and 200Msps for the UBX) do not allow for
simultaneous operation under the same USRP. But what about
different USRPs?
https://lists.gnu.org/archive/html/discuss-gnuradio/2017-07/msg00021.html
If I try running the benchmark_rate having two TwinRX on the
address 70.2 and two UBX on the 60.2 like:
/>> sudo /usr/local/lib/uhd/examples/benchmark_rate --args
"addr0=192.168.70.2,addr1=192.168.60.2" --rx_channels 0,1,2,3
--rx_subdev "A:0 B:0" --rx_rate 1e6 --ref external --pps external/
I get the error:/
/
/RuntimeError: Conflicting tick rates: One neighbouring block
specifies 2e+08 MHz, another 1e+08 MHz./
/
/
I also tried changing the master clock rate to see if we can match
them, but then I get that the X310 can't change their master clock
rate at runtime, even when I set these parameters as "stream_args"
when I create the usrp_source object.
Thanks,
Carlos
_______________________________________________
USRP-users mailing list
[email protected] <mailto:[email protected]>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
