Re: [USRP-users] rfnoc build standard image x310 failing

2020-06-02 Thread Mitch Grabner via USRP-users
Jeff, I'm having the same error as you while trying to build an OOT block using 3.15 LTS. I've tried modifying the uhd_image_builder.py script to point to the root directory of the OOT but I get a different error saying there is no rule to make target. I'll update if I find a fix. -mitch On Mon,

Re: [USRP-users] Timed commands (still) not executed properly: command time is in the past

2020-03-12 Thread Mitch Grabner via USRP-users
Hi Lukas, I've had success doing a TX tune at some exec_time_tx (where exec_time_tx is time_now() + some_delay) and then tuning RX at some exec_time_rx which is exec_time_tx + trx_offset. As long as the trx_offset is the same between runs, you should see phase coherence. I also like to use get_tim

[USRP-users] Phase coherent UBX160s on multiple X310s

2019-07-31 Thread Mitch Grabner via USRP-users
Hello, I'm trying to achieve a constant phase offset with multiple X310s each using a UBX160 daughter card. My procedure is as follows: 1) All X310s have a 10MHz reference and PPS fed via an octoclock 2) each device FPGA time is aligned on the PPS edge 3) each device sets their LO to the same freq

Re: [USRP-users] starting and stopping continuous sample streaming B200

2018-10-19 Thread Mitch Grabner via USRP-users
I think I figured it out. Since the receive streamer is expecting recv() to be called continuously until the stop command is sent there will be some left over samples between sending the command and the device recognizing the command. I simply use while(!rx_metadata.end_of_burst) loop to clear thos

[USRP-users] starting and stopping continuous sample streaming B200

2018-10-19 Thread Mitch Grabner via USRP-users
Hi again, I'm having trouble receiving a continuous stream of samples, sending a stop command to the rx_streamer, and then a little while later re-initiating continuous streaming. I either get a timeout error the second time I start streaming or the recv() function will send me back an incomplete p

Re: [USRP-users] weird sample values when receiving on b200

2018-10-15 Thread Mitch Grabner via USRP-users
, 2018 at 1:35 PM Marcus Müller wrote: > Hi Mitch, > > where/how do you create the rx_streamer, and which otw / cpu format > does that use? > > Best regards, > > Marcus > On Thu, 2018-10-11 at 11:53 -0400, Mitch Grabner via USRP-users wrote: > > I'm doi

Re: [USRP-users] weird sample values when receiving on b200

2018-10-11 Thread Mitch Grabner via USRP-users
us to review, to get an idea of > what you're doing that's causing this issue for you? Without specific > code, debugging is a little difficult ... And, no, I haven't seen this > issue to the best of my knowledge / understanding of what it might be. > Cheers! - MLD

[USRP-users] weird sample values when receiving on b200

2018-10-10 Thread Mitch Grabner via USRP-users
Hello, I find that sometimes when I initialize a b200 and start streaming in samples I will get buffers with values of infinity (especially at the last sample in the buffer). Is this caused by a bad packet or overflow condition? It also seems to happen randomly. Thanks for your help, - mitch

Re: [USRP-users] timed burst problem on B200

2018-10-01 Thread Mitch Grabner via USRP-users
md.end_of_burst = false; > >>>>>> md.has_time_spec = true; > >>>>>> md.time_spec = uhd::time_spec_t(time_to_transmit); > >>>>>> > >>>>>> //then while loop through samples > >>>>>> > >>&

Re: [USRP-users] timed burst problem on B200

2018-10-01 Thread Mitch Grabner via USRP-users
; double time_to_transmit = 2.0; > >>>>>> > >>>>>> uhd::tx_metadata_t md; > >>>>>> md.start_of_burst = false; > >>>>>> md.end_of_burst = false; > >>>>>> md.has_time_spec = true; &g

[USRP-users] timed burst problem on B200

2018-09-27 Thread Mitch Grabner via USRP-users
Hello, I'm trying to get a timed burst working on a B200 and it looks like the device is transmitting the samples the instant they reach the device (tested by listening on a second device) instead of holding them until the time specified in md.time_spec. I set up the first packet's metadata with s