On 2022-01-05 16:16, Rob Kossler wrote:
I noticed in the log that the device was B210 operating over "USB 2".
This is generally not a good thing. It should be operating over USB 3.
Rob
It depends. It's perfectly willing to operate over USB2, albeit at
lower sample rates.
Whether that's adequ
I noticed in the log that the device was B210 operating over "USB 2". This
is generally not a good thing. It should be operating over USB 3.
Rob
On Wed, Jan 5, 2022 at 12:20 PM Marcus D. Leech
wrote:
> You may be better served by cross-posting this to the discuss-gnuradio
> mailing list, where
> I don’t think that recv_async_msg() blocks. So an infinite loop will chews up
> CPU.
I had a separate thread that only called recv_async_msg(). I have unused cores
on my machine, my reasoning was that I’d rather have a CPU busy looping than
risk Ls on my transmit because the hot loop Tx threa
You may be better served by cross-posting this to the discuss-gnuradio
mailing list, where there may be more users of gr-radar than here.
Generally, a "late command" isn't a fatal error. What it basically
means is that the *application* (gr-radar) asked for a "timed" command,
but was unable t
I am trying to use the USRP echotimer block from gr-radar module. But when I
run the flowgraph containing this block, I get the following error:
`[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501;
UHD_3.15.0.0-70-g42b6fcf6`
`[INFO] [B200] Detected Device: B210`
`[INFO] [B200] Operating o
On 1/4/22 5:12 PM, constantineta...@gmail.com wrote:
Hello Community
Is there a way to apply CFR for B210 by using configurations in srslte?
sorry, just out of curiosity, what is CFR?
What parameters do we need to tweak to be able to do so? Specifically,
what are the values do we need to se
