Hello Cedric, This information is listed in the manual for error/problem troubleshooting) [1]
The "D" is a dropped packet on reception, and shows up as an indication of a sequence error caused by an overflow on networked devices. [2] The "S" is a sequence error on transmission. The possible causes of such problems are also listed in [1]. Cheers, - Nicolas [1] https://files.ettus.com/manual/page_usrp_x3x0_config.html#x3x0cfg_hosthw_troubleshooting [2] https://files.ettus.com/manual/page_general.html#general_ounotes_overflow On Tue, Apr 3, 2018 at 9:47 AM, Cedric Roux via USRP-users < usrp-users@lists.ettus.com> wrote: > On 04/03/18 00:45, Martin Braun via USRP-users wrote: > >> If you're on 3.11.* or later, then you can use >> -DUHD_LOG_FASTPATH_DISABLE to disable the printing of UOSDL. If you want >> to know about U, S and L events, then use recv_async_msg() as you're >> already doing. If you want to know about O and D events, then check the >> rx_metadata from recv(). >> >> Cheers, >> Martin >> > > Thanks Martin. > > Just to recap (the documentation is vague, or I did not find the > correct URL): > - L: late packet on TX, I send a packet to the device with a timestamp > in the past > - U: underflow: there is a TX stream running but the application > did not send data for time T=now > - S: what is it? > - O: overflow: there is too much data in RX buffers, the device > cannot put new samples because the application did not > get the data in the buffers yet > - D: what is it? > > I don't understand S and D. I hope I'm correct for the others. > > Thanks. > > _______________________________________________ > USRP-users mailing list > 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
