[USRP-users] Re: Error while using USRP Echotimer Block from gr-radar

2022-01-07 Thread mobizmn--- via USRP-users
I changed the wire and now it shows USB 3.0. ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Re: Error while using USRP Echotimer Block from gr-radar

2022-01-07 Thread mobizmn--- via USRP-users
I posted it there, but have not received an answer yet. ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com

[USRP-users] Re: Error while using USRP Echotimer Block from gr-radar

2022-01-05 Thread Marcus D. Leech
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

[USRP-users] Re: Error while using USRP Echotimer Block from gr-radar

2022-01-05 Thread Rob Kossler
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

[USRP-users] Re: Error while using USRP Echotimer Block from gr-radar

2022-01-05 Thread Marcus D. Leech
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