On 10/11/2019 04:28 PM, Sam Reiter via USRP-users wrote:
Ivan,

Thanks for sending that along. From a software perspective, what parameters do you input to your attached code to run it? I'm trying to understand the data rates you're trying to sustain over the NIC you have. I've been combing through this past USRP-users thread for some additional insight:

http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2014-May/037495.html

Based on some of those suggestions, it might be wise to try finding another NIC to bring into the equation.

Sam
Indeed, I just noticed the 82574L/LM referenced in the original complaint.

Those types of NICs have issues that cause packet loss--there have been a few "workarounds" over the years in various kernels, but none of them actually 100% fix the underlying issue with those chips--they're basically broken. You don't notice this with web-browsing and
  other TCP-based protocols, because those protocols do error recovery.





On Wed, Oct 9, 2019 at 2:14 PM Ivan Zahartchuk via USRP-users <usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> wrote:



    ---------- Forwarded message ---------
    От: *Ivan Zahartchuk* <adray0...@gmail.com
    <mailto:adray0...@gmail.com>>
    Date: ср, 9 окт. 2019 г. в 06:05
    Subject: Re: [USRP-users] Error handling D when reading data USRP
    N 210
    To: Sam Reiter <sam.rei...@ettus.com <mailto:sam.rei...@ettus.com>>


    CPU intel core i7 -3610QE 2.3 GGz
    RAM 16 Gb
     2 NIC intel 82574L gigabit ethernet and intel 82574LM gigabit
    ethernet


    вт, 8 окт. 2019 г. в 16:59, Sam Reiter <sam.rei...@ettus.com
    <mailto:sam.rei...@ettus.com>>:

        What hardware are you using on the host side? Specifically,
        I'm interested in CPU, RAM, and NIC.

        Sam Reiter

        On Tue, Oct 8, 2019 at 6:22 AM Ivan Zahartchuk via USRP-users
        <usrp-users@lists.ettus.com
        <mailto:usrp-users@lists.ettus.com>> wrote:

            Hello. When I read data from the board, error D
            periodically passes. It leads to bursts in the spectrum
            that fits in the figure. Please tell me how you can remove
            this error or how it can be handled? I also attach the
            code file.
            errorD.png
            _______________________________________________
            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

_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to