[USRP-users] getting parser error with uhd-usrp for rx-ofdm example

Hi, I am trying to use usrp N210 in a system running ubuntu16.04 for rx-ofdm in gnuradio while using TX/RX antenna but i get the following error below. linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.HEAD-0-g929e3b32 -- Opening a USRP2/N-Series device... -- Current recv frame

Re: [USRP-users] getting parser error with uhd-usrp for rx-ofdm example

Hi dapodun nudopad - Yes there are a variety of possible ways the Tx/Rx can result in the "Parser returned #f" issue. What it means is that the S&C detected a header, but the header CRCs (computed versus embedded) didn't match up. Since we can't see your whole flowgraph, its a little difficult to g

[USRP-users] Multiple B200, Python API.

Hi, Hope you're doing well. I am new here and new to the USRP API. Attached is a setup to record signals at 380MHz and 2.4Ghz on two B200's. The aim is to sync the devices using the 10Mhz and 1PPS provided from an external source to both devices. Using the python API to achieve this and here

Re: [USRP-users] Multiple B200, Python API.

On 10/17/2018 10:53 AM, J Subash via USRP-users wrote: Hi, Hope you're doing well. I am new here and new to the USRP API. Attached is a setup to record signals at 380MHz and 2.4Ghz on two B200's. The aim is to sync the devices using the 10Mhz and 1PPS provided from an external source to both

Re: [USRP-users] Synch'ing two USRP-X310

You can test the hypothesis using a heat gun. Sent from my iPhone > On Oct 17, 2018, at 1:13 AM, Francois Quitin wrote: > > We use 30cm high quality sma cables, so I'm a bit surprised that this would > be thermal noise... > > n 17.10.2018 05:23, Marcus D. Leech wrote: >>> On 10/16/2018 04:49

[USRP-users] n3xx master clock rate selection

Hi all, I'm working on an FPGA application on the n310/n300, and I'm bumping into a limitation of the master_clock_rate selection I'd like to be able to use sample rates in the FPGA of 2 MHz, 4 MHz, and 10 MHz, but none of these values are integer multiples of the supported rates (122.88e6, 12

[USRP-users] Test

Sorry about this. Testing. ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] n3xx master clock rate selection

Hi EJ, The fundamental limitation comes from the AD9371. Although the datasheet specifies a wide reference clock input range, there are only certain supported rates within the public side of their API (at least that I'm aware of). These include the rates you mentioned from the KB. Assuming the AD

[USRP-users] X310 synchronization over White Rabbit

[copy to the White Rabbit Developers mailing list] I am considering distributed radiofrequency signal acquisition and generation using two Ettus Research X310 SDR platforms, fed with the 1 PPS and 10 MHz outputs from our White Rabbit (WR) network. In addition to these signals, the control softwa

Re: [USRP-users] N310 SPF+ compatability

Never-mind. It was an issue unrelated to USRP. At least those searching the mailing list in the future know now that these parts are known good. On Tue, Oct 16, 2018 at 11:39 AM Ali Dormiani wrote: > Hello > > I am having a lot of problems getting 10 Gbe SFP+ working between an N310 > and a serv

Re: [USRP-users] X310 synchronization over White Rabbit

Hi Jean-Michel, As you hinted, it might be best to re-post this to the White Rabbit list: https://lists.ohwr.org/sympa/info/white-rabbit-dev >From my limited experience with White Rabbit and the N310 product, I don't see any obvious issues, other than possibly within the switch. -Daniel On Wed,

[USRP-users] Pybombs error for gnuradio

Hello all, I have used pybombs in the past and it worked just fine. But recently I get compatibility issues of uhd and fpga, as well as the following error while building gnuradio. Has anyone seen this before? I am following the getting started rfnoc guide. [ 87%] Building CXX object gr-uhd/swig/

[USRP-users] B210 EnvironmentError: IOError: usb rx6 transfer status: LIBUSB_TRANSFER_OVERFLOW

Hi, I'm having trouble receiving samples with my B210. I get the following error when I run either a GNU Radio Companion script or the benchmark utillity: EnvironmentError: IOError: usb rx6 transfer status: LIBUSB_TRANSFER_OVERFLOW Does anyone have a way to resolve this? Below is the benchmark

Re: [USRP-users] B210 EnvironmentError: IOError: usb rx6 transfer status: LIBUSB_TRANSFER_OVERFLOW

Hi Andrew. It looks like your USRP B210 is connected via USB2. Do you still see the same error when connected to a USB3 port? -Robin On Wed, Oct 17, 2018 at 1:00 PM Harper, Andrew via USRP-users < usrp-users@lists.ettus.com> wrote: > Hi, I'm having trouble receiving samples with my B210. I get

Re: [USRP-users] Saturation issue with low amplitude (USRP N310)

Attempt 2. Sorry for breaking mailing list rules with the attachments. Here is a google drive link to the screenshots, GRC file, and binary files. (3 MB zip) https://drive.google.com/a/eng.ucsd.edu/file/d/1TvmHuEMFb2QpkiMMdiUEW6aVoUfLYayi/view?usp=sharing We have three sliders in GNUradio. 1. T

Re: [USRP-users] n3xx master clock rate selection

Hi Daniel, Sad to hear that! By the way, I forgot to mention another important rate I need, 3 MHz, that also has an integer relationship to 120 MHz... Perhaps I'd like to make a formal feature request for 120 MHz master clock?? It strikes me as odd that so many of the "whole number" MHz sample rat

[USRP-users] Another test

test. ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] n3xx master clock rate selection

So, I'm trying to understand the fundamental clock rate selection limitations for the 9371... From what I understand, this is plausibly due to some limitations of the JESD interface (?). This wiki answer suggests possible rates of 122.88M, 153.6M, 184.32M, 245.76M, or 307.2M: https://ez.analog.com