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 adequate depends entirely on the application...
On Wed, Jan 5, 2022 at 12:20 PM Marcus D. Leech
<patchvonbr...@gmail.com> wrote:
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 to deliver that command before the
time requested.
On 2022-01-05 04:29, mobizmn--- via USRP-users wrote:
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 over USB 2.|
|[INFO] [B200] Initialize CODEC control...|
|[INFO] [B200] Initialize Radio control...|
|[INFO] [B200] Performing register loopback test... |
|[INFO] [B200] Register loopback test passed|
|[INFO] [B200] Performing register loopback test... |
|[INFO] [B200] Register loopback test passed|
|[INFO] [B200] Setting master clock rate selection to 'automatic'.|
|[INFO] [B200] Asking for clock rate 16.000000 MHz... |
|[INFO] [B200] Actually got clock rate 16.000000 MHz.|
|Using USRP Device (TX): |
|Single USRP:|
|Device: B-Series Device|
|Mboard 0: B210|
|RX Channel: 0|
|RX DSP: 0|
|RX Dboard: A|
|RX Subdev: FE-RX2|
|RX Channel: 1|
|RX DSP: 1|
|RX Dboard: A|
|RX Subdev: FE-RX1|
|TX Channel: 0|
|TX DSP: 0|
|TX Dboard: A|
|TX Subdev: FE-TX2|
|TX Channel: 1|
|TX DSP: 1|
|TX Dboard: A|
|TX Subdev: FE-TX1|
|Setting TX Rate: 2000000|
|[INFO] [B200] Asking for clock rate 32.000000 MHz... |
|[INFO] [B200] Actually got clock rate 32.000000 MHz.|
|Actual TX Rate: 2e+06|
|[INFO] [USRP2] Opening a USRP2/N-Series device...|
|[INFO] [USRP2] Current recv frame size: 1472 bytes|
|[INFO] [USRP2] Current send frame size: 1472 bytes|
|[WARNING] [UHD] Unable to set the thread priority. Performance
may be negatively affected.|
|Please see the general application notes in the manual for
instructions.|
|EnvironmentError: OSError: error in pthread_setschedparam|
|Using USRP Device (RX): |
|Single USRP:|
|Device: USRP2 / N-Series Device|
|Mboard 0: N210r4|
|RX Channel: 0|
|RX DSP: 0|
|RX Dboard: A|
|RX Subdev: WBXv3 RX+GDB|
|TX Channel: 0|
|TX DSP: 0|
|TX Dboard: A|
|TX Subdev: WBXv3 TX+GDB|
|Setting RX Rate: 2000000|
|Actual RX Rate: 2e+06|
|set_min_output_buffer on block 1 to 2400|
|set_min_output_buffer on block 2 to 2400|
|terminate called after throwing an instance of 'std::runtime_error'|
|what(): Receiver error ERROR_CODE_LATE_COMMAND|
My transmit device is USRP B210 and the receiver is USRP N210.
The settings of the USRP Echotimer block are attached. What could
be causing this error?
_______________________________________________
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-le...@lists.ettus.com
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
