IO will be your speed limiting factor. I've had SDRC running a full 30 MHz wide USB 3 link to a RX888 and an RX888 MKII receiver. I hacked a little and got SDRSharp to run happly on the MKII with a 60 MHz level bandwidth. Going much above that would probably be a problem with USB 3.1. I've not worked out the math, though. 120 million 16 bit samples per second is a bit under 2 GHz data rate. You'd need 10 gig Ethernet to handle it. And a 1 GHz net would possibly have problems with the full RX888 (not MKII) bandwidth. These days the Ethernet offered on most computers is "slow".

{^_-}

Ettus USRP N200 Test with Beta SDR Console 

=====================================

Ettus_USRP N200 with WBX board  fitted running under SDR console (Beta, Jan 2022) 

and UHD 4.0 driver

WBX Bandwith set to 25MHz (in older SDR console version settings of +/- 20 MHz were possible) 

Hardware performance as per SDR console:

Xeon E5-2690 CPU load                                       ~ 8%, 

GTX1650 (silent card ) load                                  43%

GHz Network  (Intel Pro 1000 dual card)               83% load

Conclusions:  

SDR console can easily handle the high data flow.generated by the USRP N200 

Reported Hickup's are likely from unsufficienet hardware performance and NOT from SDR console software. 

#########  Congratulations to SIMON ###############

The small s"carrier" below the qo100 NB transponder is likely a DC spike.

I would really like to test the USRP  X310 with one UBX 160 board, 

but need help as the default X310 setup is not recognised by SDR_Console..

73, Charly  DF5VAE

sdr_console -Ettus N200_networkload_k.jpg

sdr_console -Ettus N200_QO100_25MHz BW_k.jpg

sdr_console -Ettus N200_WBX_k.jpg

sdr_console -Ettus N200_X310.jpg