> > You can try using the "num_recv_frames" option in the device argument--I'd > suggest trying 128 and 256. >
I get tons of errors right after seeing [INFO] [B200] Operating over USB 3. Would this explain why I can't seem to stream fast? Here's what I get for 128 Creating the usrp device with: num_recv_frames=128... [INFO] [UHD] Win32; Microsoft Visual C++ version 14.0; Boost_105900; UHD_3.12.0.0-release [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_session_impl::libusb_event_handler_task: LIBUSB_ERROR_CODE -1 [INFO] [B200] Initialize CODEC control... [...] With 256 the program crashes and I only see Creating the usrp device with: num_recv_frames=256... [INFO] [UHD] Win32; Microsoft Visual C++ version 14.0; Boost_105900; UHD_3.12.0.0-release [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_sessi Can this be a USB driver problem? I'm using the one from http://files.ettus.com/binaries/misc/ dated 29-Mar-2016 19:52. Can I run any test to make sure everything is fine (B210, drivers, software)? I'll also note that, near as I can tell, LimeSDR drivers dont' reliably > report overruns, so you may be getting them without knowing about it. > I always check the timestamps returned, so I'm pretty sure I only get very few overruns with the Lime.
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
