[USRP-users] E310 Rx Timeout with higher sampling rates
jason.j.hein at gmail.com
Thu Apr 30 15:40:43 EDT 2015
It sounds like you're running in network mode (pulling streaming data off
the gigabit network interface) and the usrp_e3x0_network_mode process on
the E310 can't keep up with those sample rates. Try logging into the E310
and running 'top' when you're doing the usrp->recv(). Start scaling back
the data rate until the CPUs aren't pegged. I was getting about 1 MSps
On Thu, Apr 30, 2015 at 2:45 PM, Voss, Nathan J via USRP-users <
usrp-users at lists.ettus.com> wrote:
> I am in the process of porting code that was built and tested successfully
> on a USRP N200 to a USRP E310. The sampling rate is user-configurable, and
> we really need to support as large a bandwidth as possible. On the N200, my
> code worked fine for sampling rates up to ~15Msps, but on the E310 the same
> code is struggling to run over about 500Ksps.
> When I set the sampling rate on the E310 above about 500Ksps, I initially
> get one or two 'O' overflow notifications, and then start to get timeout
> errors very frequently. My code is fairly simple, in that I'm calling
> 'usrp->recv()' in a pretty tight loop, very similar to the
> 'rx_samples_to_file' example. The timeout value I'm passing into the recv()
> call is currently 3.0 seconds, and my 'nsampls_per_buf' is typically 512.
> Thanks for your help.
> USRP-users mailing list
> USRP-users at lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the USRP-users