Hi, The problem was fixed by removing a periodic call to the reset() method of the streamers. The code<https://github.com/LorenzoMinutolo/GPU_SDR> and the documentation<http://www.its.caltech.edu/~minutolo/gpu_sdr_doc.html> is publicly available and the fix has been applied in one of the recent commits. The effect of not resetting the streamers was critical for our application in UHD 3.11 (we were observing a different line delay in each of out measurement) but with the latest UHD (3.15) Everything seems to work fine.
Best, Lorenzo ________________________________ From: USRP-users <usrp-users-boun...@lists.ettus.com> on behalf of Marcus D. Leech via USRP-users <usrp-users@lists.ettus.com> Sent: Monday, December 2, 2019 4:01 PM To: usrp-users@lists.ettus.com <usrp-users@lists.ettus.com> Subject: Re: [USRP-users] x300 systematic error On 12/02/2019 05:57 PM, Ettus Research Support via USRP-users wrote: Hi Lorenzo, What version of UHD are you using? Can you share your C++ app (either by emailing the mailing list or by emailing it to supp...@ettus.com<mailto:supp...@ettus.com>)? Regards, Nate Temple My guess is that *somebody* is running out of sockets -- either the host-side UHD library or the X3xx side. How rapidly do you reset/re-start the streams? For TCP sockets at least, there's a timer when the socket is closed that causes it to hang-around for a while in case more data arrives after the close handshake. While the socket is in this state, it cannot be reused, so if you're rapidly creating and destroying objects that ultimately create a socket, you can run out of sockets. Pure speculation on my part, and it may be something else entirely. On Wed, Nov 6, 2019 at 1:41 PM Minutolo, Lorenzo via USRP-users <usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>> wrote: Hi All, My C++ application has a loop which after creating the streamers, send and receive some samples -> reset the streamers -> wait some time -> repeat. after exactly 83 iterations I get the error in the attached screenshot. If I restart the application everything works normally again What is causing this? is there a workaround? I'm using the USRP x300, core i9-990k CPU, intel x710 chip, running ubuntu 18.04 LTS with boost 1.68 and the latest UHD library (just coned). The error is the same using all other UHD versions Thanks, Lorenzo _______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com _______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com<mailto:USRP-users@lists.ettus.com> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
