Hi all, any idea what the problem might be?
I'm on Windows 10 64 bit. I see the B210 in "Device Manager" under USRPs > Ettus Research LLC B200/B210. The drivers are by "Ettus Research", on 29 March 2016, version 0.0.0.0, signed by National Instruments Corporation. Thanks. Le jeu. 28 juin 2018 à 16:22, RizThon <rizt...@gmail.com> a écrit : > Here's what I see > > *Creating the usrp device with: num_recv_frames=256...* > *[INFO] [UHD] Win32; Microsoft Visual C++ version 14.0; Boost_106300; > UHD_3.11.0.1-37-g2c9087d1* > *[INFO] [B200] Detected Device: B210* > *[INFO] [B200] Operating over USB 3.* > *[ERROR] [USB] libusb_session_impl::libusb_event_handler_task: > LIBUSB_ERROR_CODE -1* > *[ERROR] [USB] libusb_ses* > > I guess the program crashes as I don't see anything else. If I try with a > lower value like 128 or 64, I get tons of erros like that, until I see > *DONE!* towards the end. > > I've seen https://github.com/EttusResearch/uhd/issues/68 but it's on Mac > OS. > > I've tried switching the Lime and B210, changing USB cable, but I'm still > seeing the same issues with overruns. > > > Le jeu. 28 juin 2018 à 09:43, Marcus D. Leech <mle...@ripnet.com> a > écrit : > >> On 06/27/2018 09:25 PM, RizThon wrote: >> > >> > I would have expected to have no problem in mono channel at 56MS/s, as >> > I have no problem on the Lime (with int12 instead of int16, but with 2 >> > channels instead of 1). >> > >> > Is it possible to stream at 56MS/s on a single channel on the B210 >> > (same question for the others B2xx) without overflows? >> Yes, if your machine is up to the task, and you've tweaked the buffering. >> >> Try "num_recv_frames=256" in your device arguments. >> >> >> > >> > Thanks. >> >>
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
