Thanks a lot!


On 11-Aug-2017, at 12:20 AM, "<>" 
<<>> wrote:

It's default to internal anyway.   IF this is a single motherboard, then no 
external clock sync is required, but you still need the use timed-commands on 
the tuning.

If this is multiple USRP units, then, yes, you'll need to use an external 
synchronization source in addition to the above--this will allow for a common 
clock, and clock synchronization via 1PPS.

It's often instructive to look at the code generated by GRC, even if ultimately 
you aren't going to use Gnu Radio, but just "raw" UHD.

On 2017-08-10 14:40, Snehasish Kar wrote:

Thanks for explaining the commands, it is of real help. One more point if set 
the clock and time source as internal, will it bring the two receivers in sync, 
as I did the same thing with uhd_source in gnuradio and the two boards were in 
sync. What's your opinion on this?


On 10-Aug-2017, at 10:48 PM, "<>" 
<<>> wrote:

You can use rx_multi_samples as an example  -- the source code is freely 

You'll need to use the "set_rx_freq" (and/or "set_tx_freq") function that is 
part of any  multi_usrp object, also, use timed commands around the tuning 


usrp->set_rx_freq(desired_freq1, 0)

usrp->set_rx_freq(desired_freq2, 1)


Also, see the Ettus knowledge-base:

On 2017-08-10 13:06, Snehasish Kar wrote:

Tried that and yeah the default code works, but can you help me in 
understanding how do I tune the two daughter boards separately to two different 
frequencies and receive data from them parallely. Also I need to time 
synchronise the two daughter boards, how to achieve that.


On 10-Aug-2017, at 10:27 PM, "<>" 
<<>> wrote:

This may be timing-out due to performance issues on your host, or it may be a 
bug in your code.

Have you tried using the the rx_multi_samples example at the same sample rates?

2 x 50Msps is a lot of data, and with the short "packets" on PCIe, your 
computer will be working fairly hard at servicing those samples.

Before we get in to debugging your code, could you:

   (A) Try lower sample rates

   (B) Try rx_multi_samples

On 2017-08-10 12:53, Snehasish Kar wrote:

It's connected via the pcie cable.


On 10-Aug-2017, at 9:04 PM, Marcus D. Leech 
<<>> wrote:

On 08/10/2017 05:26 AM, Snehasish Kar wrote:

Please find the log below:

linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.002.000-0-unknown

Creating the usrp device with: ...
-- X300 initialization sequence...
-- Connecting to niusrpriorpc at localhost:5444...
-- Using LVBITX bitfile /usr/local/share/uhd/images/usrp_x310_fpga_HG.lvbitx...
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Detecting internal GPSDO.... Found an internal GPSDO: LC_XO, Firmware Rev 
-- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1303.3MB/s)
-- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1303.8MB/s)
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
Using Device: Single USRP:
  Device: X-Series Device
  Mboard 0: X310
  RX Channel: 0
    RX DSP: 0
    RX Dboard: A
    RX Subdev: UBX RX
  RX Channel: 1
    RX DSP: 0
    RX Dboard: B
    RX Subdev: UBX RX
  TX Channel: 0
    TX DSP: 0
    TX Dboard: A
    TX Subdev: UBX TX
  TX Channel: 1
    TX DSP: 0
    TX Dboard: B
    TX Subdev: UBX TX

Setting RX Rate: 50.000000 Msps...
Actual RX Rate: 50.000000 Msps...

Setting device timestamp to 0...
Press Ctrl + C to stop streaming...
Waiting for "lo_locked": ++++++++++ locked.

Begin streaming 10000 samples, 1.500000 seconds in the future...


Receive timeout before all samples received...



How is your X310 connected to your computer?

USRP-users mailing list

Reply via email to