Yes, B210 here.
Ron
On 7/19/21 2:19 PM, Marcus D Leech wrote:
Ron is that on a B2xx or something else?
Sent from my iPhone
On Jul 19, 2021, at 4:27 PM, Ron Economos <[email protected]> wrote:
I haven't tried the latest UHD version. However, I do have UHD
4.0.0.0 running without stopping with just the patch from
https://github.com/EttusResearch/uhd/commit/70e1f0f0c697d6522e3a87e2de93e34e375decb4
Ron
On 7/19/21 8:58 AM, wan wrote:
Ron,
I didnt find an open issue related to this at first, but after your
response I found it in the closed issues
(https://github.com/EttusResearch/uhd/issues/380
<https://github.com/EttusResearch/uhd/issues/380>). The fix was
committed in Oct 2020. However, I tried master
(UHD_4.1.0.0-13-g240c7fd), v4.1.0.0 and v4.1.0.1, and I have the
problem in all three versions. Is it working for you in any of these
versions?
Mike,
Thanks for joining the discussion. I'm also seeing the
ERROR_CODE_TIMEOUT problem with benchmark_rate. However, it usually
happens when I set the sample rate to 50 Msps or higher, and run for
more than 30 seconds. At 2 to 5 MSps, I dont have any errors or
overruns. I didn't mention it before because I figured it's normal
since I'm running at a high sample rate. However, on v3.15.0.0, I
can consistently stream at 50 Msps without getting any timeouts or
overruns.
On Mon, 19 Jul 2021 at 11:34, McNulty, Mike (Assoc) via USRP-users
<[email protected] <mailto:[email protected]>> wrote:
Hello,
I don’t want to interrupt the thread but I actually joined the
mailing list for this issue. I just upgraded to UHD 4.1.0.1 and
I’m experiencing the same timeout issue.
<image004.png>
This is a snip from a ./lib/uhd/examples/benchmark run at 5 Msps.
<image005.png>
It looks to me as soon as it receives the first overflow the
execution terminates. Somewhere between 2.0 and 5.0 Msps my
system drops samples
<image006.png>
Thanks for everything everyone does! I wanted to just add my
experience to help with development.
Mike
*From:* Ron Economos <[email protected] <mailto:[email protected]>>
*Sent:* Monday, July 19, 2021 1:45 AM
*To:* [email protected] <mailto:[email protected]>
*Subject:* [USRP-users] Re: Is UHD supposed to keep running
after detecting overrun?
It is a bug in UHD v4.0.0.0, but it should be fixed in UHD
v4.1.0.1 (and UHD v4.1.0.0).
Ron
On 7/18/21 9:37 PM, wan wrote:
Hello,
When UHD detects an overrun, is it supposed to keep going or
freeze? I'm using an USRP B200mini. I tested it with the
rx_ascii_dft and the uhd_fft GRC example using different
versions of UHD on Ubuntu 20.04. When using UHD 3.15.0, an
overrun is detected, the application keeps running and
prints a sequence of "O" to the terminal. However, when I
use UHD 4.0.0.0 and 4.1.0.1, as soon as an overrun is
detected, the ascii or gnuradio QT displays stop updating.
Regards,
Wan
_______________________________________________
USRP-users mailing list [email protected]
<mailto:[email protected]>
To unsubscribe send an email [email protected]
<mailto:[email protected]>
_______________________________________________
USRP-users mailing list -- [email protected]
<mailto:[email protected]>
To unsubscribe send an email to [email protected]
<mailto:[email protected]>
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
