From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

USRP Software Radio

cancel
Showing results for 
Search instead for 
Did you mean: 

USRP-2953R with RX-Tx Finite Sync2011.vi

Hi, I'm new to Labview 2018 and the USRP-2953R (CBX-120)

 

Communicating with the 2953R over 10Gbps Ethernet with the TX1/RX1 output directly connected to the RX2 input of RF0. Because I'm not using the PCIe interface, I'm unable to run the RIO examples.

 

I have been checking out the example given in https://forums.ni.com/t5/Software-Defined-Radio/Single-USRP-Synchronized-TX-and-RX-Finite/ta-p/35056... and trying to get it to work with the 2953R as well as trying to understand the code.

 

Straight-off, I had to change the carrier frequency to 2GHz as the default 915MHz was out of band for this USRP. 

 

Seeking some understanding for:

1. why there would be an underflow error from the TX as the "end of data?" input to the TX write VI was wired True. When probed, the input to the TX write VI was 2000 elements.

2. (this sounds really stupid) where the data for the TX is coming from? In the block diagram, it's wired from a cluster named "delay-sinewave-delay" but for the life of me I can't see to find how/where the sine wave is generated or is it a constant that is hard-coded into the VI?

 

Thanks!

0 Kudos
Message 1 of 3
(2,082 Views)

Hi, Krazyk1d

 

1. What is your front panel configuration? I did the same code with USRP-2954R. There is no problem for my case.

2. Can you get the ping response from USRP?

3. You can see the double data type array in a cluster named "delay-sinewave-delay". The array has values for the sine wave. As a result, the sine wave is hardcoded.

 

Thanks.

0 Kudos
Message 2 of 3
(2,033 Views)

Hi Chan82,

 

Thanks. I found out why my USRP TX was getting under-runs. The default sinewave array had a length of 2000. However, the optimum lengths using the 10Gbps Ethernet link is 1992 with Jumbo Frames of 9000 bytes so I had to change the sinewave to have an integer number of 1992 bytes per TX write call. That solved the under-run.

 

Thanks 

0 Kudos
Message 3 of 3
(1,998 Views)