Wireless Testbench Radio Setup fails at the loopback test for USRP X300

Hello.

I'm trying to setup a X300 USRP to use with the MATLAB Wireless Testbench Add-On. After running the radioSetupWizard command, I get the following error when performing the validation:

---

Output argument "status" (and possibly others) not assigned a value in the execution with "wt.internal.hwsetup/RadioToneValidationHSP/loopbackTone" function.

---

I'm using MATLAB R2025a, with all the add-ons the the installation of MATLAB itself up to date. Also, I'm running uhd_usrp_probe version 4.6.0.0. I'm able to ping the USRP at the default address 192.168.10.2 in the terminal, and uhd_usrp_probe can find and display info about the USRP both in the windows terminal and in the MATLAB command window using findsdru('192.168.10.2'). I also tried turning the firewall on and off again in the control pannel in windows since I saw that suggested in another question here and in the Common Problems and Fixes documentation, but it didn't help.

Any help would be greatly appreciated. Thanks!

[Martin Enderwitz]

Hello,

So that we can investigate this further, can you run the following command and provide the output here?

probesdru('192.168.10.2')

Thanks,

Martin

[Theodor-Corneliu]

Hi,

I ran the command you provided, and got this result, as expected.

'[INFO] [UHD] Win32; Microsoft Visual C++ version 1936; Boost_108100; UHD_4.6.0.0-vendor

[INFO] [X300] X300 initialization sequence...

[INFO] [X300] Maximum frame size: 1468 bytes.

[WARNING] [X300] For the 192.168.10.2 connection, UHD recommends a send frame size of at least 1472 for best

performance, but your configuration will only allow 1468.This may negatively impact your maximum achievable sample rate.

Check the MTU on the interface and/or the send_frame_size argument.

[WARNING] [X300] For the 192.168.10.2 connection, UHD recommends a receive frame size of at least 1472 for best

performance, but your configuration will only allow 1468.This may negatively impact your maximum achievable sample rate.

Check the MTU on the interface and/or the recv_frame_size argument.

[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a

[INFO] [X300] Radio 1x clock: 200 MHz

_____________________________________________________

/

| Device: X-Series Device

| _____________________________________________________

| /

| | Mboard: X300

| | revision: 11

| | revision_compat: 7

| | product: 30817

| | mac-addr0: 00:80:2f:22:34:e4

| | mac-addr1: 00:80:2f:22:34:e5

| | gateway: 192.168.10.1

| | ip-addr0: 192.168.10.2

| | subnet0: 255.255.255.0

| | ip-addr1: 192.168.20.2

| | subnet1: 255.255.255.0

| | ip-addr2: 192.168.30.2

| | subnet2: 255.255.255.0

| | ip-addr3: 192.168.40.2

| | subnet3: 255.255.255.0

| | serial: 31563CE

| | FW Version: 6.1

| | FPGA Version: 39.2

| | FPGA git hash: 6a990d9

| | RFNoC capable: Yes

| |

| | Time sources: internal, external, gpsdo

| | Clock sources: internal, external, gpsdo

| | Sensors: ref_locked, gps_gpgga, gps_gprmc, gps_servo, gps_time, gps_locked

| _____________________________________________________

| /

| | RFNoC blocks on this device:

| |

| | * 0/DDC#0

| | * 0/DDC#1

| | * 0/DUC#0

| | * 0/DUC#1

| | * 0/Radio#0

| | * 0/Radio#1

| | * 0/Replay#0

| _____________________________________________________

| /

| | Static connections on this device:

| |

| | * 0/SEP#0:0==>0/DUC#0:0

| | * 0/DUC#0:0==>0/Radio#0:0

| | * 0/Radio#0:0==>0/DDC#0:0

| | * 0/DDC#0:0==>0/SEP#0:0

| | * 0/Radio#0:1==>0/DDC#0:1

| | * 0/DDC#0:1==>0/SEP#1:0

| | * 0/SEP#2:0==>0/DUC#1:0

| | * 0/DUC#1:0==>0/Radio#1:0

| | * 0/Radio#1:0==>0/DDC#1:0

| | * 0/DDC#1:0==>0/SEP#2:0

| | * 0/Radio#1:1==>0/DDC#1:1

| | * 0/DDC#1:1==>0/SEP#3:0

| | * 0/SEP#4:0==>0/Replay#0:0

| | * 0/Replay#0:0==>0/SEP#4:0

| | * 0/SEP#5:0==>0/Replay#0:1

| | * 0/Replay#0:1==>0/SEP#5:0

| _____________________________________________________

| /

| | TX Dboard: 0/Radio#0

| | ID: CBX (0x0066)

| | Serial: 3168A3A

| | Revision: 1

| | _____________________________________________________

| | /

| | | TX Frontend: 0

| | | Name: CBX TX

| | | Antennas: TX/RX, CAL

| | | Sensors: lo_locked

| | | Freq range: 1200.000 to 6000.000 MHz

| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB

| | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz

| | | Connection Type: QI

| | | Uses LO offset: No

| _____________________________________________________

| /

| | RX Dboard: 0/Radio#0

| | ID: CBX (0x0067)

| | Serial: 3168A3A

| | Revision: 1

| | _____________________________________________________

| | /

| | | RX Frontend: 0

| | | Name: CBX RX

| | | Antennas: TX/RX, RX2, CAL

| | | Sensors: lo_locked

| | | Freq range: 1200.000 to 6000.000 MHz

| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB

| | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz

| | | Connection Type: IQ

| | | Uses LO offset: No

| _____________________________________________________

| /

| | TX Dboard: 0/Radio#1

| | ID: CBX (0x0066)

| | Serial: 3168A3D

| | Revision: 1

| | _____________________________________________________

| | /

| | | TX Frontend: 0

| | | Name: CBX TX

| | | Antennas: TX/RX, CAL

| | | Sensors: lo_locked

| | | Freq range: 1200.000 to 6000.000 MHz

| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB

| | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz

| | | Connection Type: QI

| | | Uses LO offset: No

| _____________________________________________________

| /

| | RX Dboard: 0/Radio#1

| | ID: CBX (0x0067)

| | Serial: 3168A3D

| | Revision: 1

| | _____________________________________________________

| | /

| | | RX Frontend: 0

| | | Name: CBX RX

| | | Antennas: TX/RX, RX2, CAL

| | | Sensors: lo_locked

| | | Freq range: 1200.000 to 6000.000 MHz

| | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB

| | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz

| | | Connection Type: IQ

| | | Uses LO offset: No

[Martin Enderwitz]

Thanks for providing this information. At this stage, I'd suggest reaching out to Technical Support so we can provide further assistance on this issue. You can get in touch here.

Answer 1

[Martin Enderwitz]

Please reach out to Technical Support so we can provide further assistance on this issue. You can get in touch here.