Rob, Thanks for the patch! I was looking into that flushing in the example and it does not seem to occur on X310 but I was able to see a delay on N310. It's not immediately clear to me why there would be a difference between products, but I will investigate. 10 seconds seems like more samples than should be queued up. I assume you're testing on N310?
Thanks, Wade On Wed, Oct 31, 2018 at 2:35 PM Rob Kossler via USRP-users < usrp-users@lists.ettus.com> wrote: > There are a couple of issues with the replay block example: > - It doesn't work correctly for ports other than the default port because > some function calls have missing "port" args or they are set to zero rather > than using the specified port (see attached patch file with changes). > - It can take a very long time to flush the samples. Is there any way > around this? Note that I am using a sample rate of 12.5 MS/s and it takes > several seconds (perhaps up to 10) to flush. I am not certain how > consistent the time is. > > Rob > > > > > _______________________________________________ > 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
