discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] UHD Sink Error


From: Marcus D. Leech
Subject: Re: [Discuss-gnuradio] UHD Sink Error
Date: Wed, 15 Mar 2017 19:03:11 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

On 03/15/2017 06:43 PM, Nigel Steed (XENINT) wrote:

Hi Marcus,

 

UHD Version is 3.10.1.1

 

And target is X310 with UBX-40 installed.

 

If I only use Rx it works fine when changing the sample rate dynamically in a flowgraph. I probably need to test just using Tx. Using both Tx and Rx (sink and source) gives the error.

 

Note, if I use the same flowgraph with a USB radio (B205mini) all comms works fine.

 

Any help much appreciated,

 

Thanks,

 

NIgel

 

From: Discuss-gnuradio [mailto:address@hidden] On Behalf Of Marcus D. Leech
Sent: Wednesday, March 15, 2017 1:29 PM
To: address@hidden
Subject: Re: [Discuss-gnuradio] UHD Sink Error

 

On 03/15/2017 05:02 AM, Nigel Steed (XENINT) wrote:

Hi All,

 

I have a flowgraph which has both a uhd_sink and uhd_source. I also have the samp_rate for both of these linked to a QT Chooser to enable me to select valid sample rates dynamically at runtime.

 

If I change the sample rate from 500kHz to 12.5MHz I can repeatedly generate the following error and the transmitter stops:

 

read[thread-per-block[9]: <block gr uhd usrp sink (8)>]: RuntimeError: On node 0/DmaFIFO_0, input port 0 is already connected.

 

If I change between sample rates closer together (12.5MHz and 3.125MHz) this problem does not appear.

 

Has anyone else experienced this, and/or know of a solution ?

 

Thanks,

 

Nigel

 

 

What version of UHD?   What USRP device type?

Thanks, Nigel.

I'm continuing this conversation on usrp-users, where it properly belongs, and where there are other Ettus support and engineering
  folk paying attention.

This looks like a bug.  You might try pulling from most recent UHD master, building it, and see if that fixes this issue.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]