Hello Rich, although Ed commented on the latency issue, regarding your performance issue my 2 pence: From my experience, using a time domain equalizer with 100 taps is a huge computational burden. Imagine: You are expecting significant echos (to be equalized) of 100*4/250kHz=1,6 ms. I do not know your application, but for wireless this is a whole lot.
BTW: I am about to use exactly your computer USRP setup. Best regards Stephan Ludwig Robert Bosch GmbH Corporate Sector Research & Advance Engineering, Communication Technology (CR/AEH4) Renningen 70465 Stuttgart GERMANY www.bosch.com<http://www.bosch.com> Tel. +49(711)811-8809 Fax +49(711)811-1052 Mobile +49(172)5630639 stephan.ludw...@de.bosch.com<mailto:stephan.ludw...@de.bosch.com> Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB 14000; Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr. Volkmar Denner, Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, Dr. Dirk Hoheisel, Christoph Kübel, Uwe Raschke, Wolf-Henning Scheider, Dr. Werner Struth, Peter Tyroller Von: discuss-gnuradio-bounces+stephan.ludwig2=de.bosch....@gnu.org [mailto:discuss-gnuradio-bounces+stephan.ludwig2=de.bosch....@gnu.org] Im Auftrag von Richard Bell Gesendet: Donnerstag, 19. Februar 2015 00:45 An: discuss-gnuradio@gnu.org Betreff: [Discuss-gnuradio] QPSK Receiver and Processing Power Hello all, My question is, looking at my receiver flowgraph, would you think this design should push the limits of a good laptop? Would you believe I could be constrained to near the lowest sample rate limit with this design? Laptop Specs: HP Elitebook 8570w, Core i7, 16 GB RAM, Ubuntu 14.04 I would be interested in hearing what sample rates other peoples QPSK radios run at with a USRP N210 and similar computer. Thanks, Rich
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio