Forum: GNU Radio Re: a running problem with the USRP, i am confused!

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
80e825d1e631c4d6681b39c0176c2f85?d=identicon&s=25 Bill Stevenson (Guest)
on 2009-05-09 02:32
(Received via mailing list)
Hi, Jason

Thank you for your help! Good man! Actually, after running lots of
experiments, I found the reason for my problem. One of my USRP is broken
and it can only serve as a TX, when playing as RX, that weird thing
would happen.

Actually, I am not transmitting one large batch file continuously. I was
transmitting 1000 packets 8 times, which means I started the
benchmark_rx.py 8 times. E.g., the PDR was 90% 1st time, 80% 2nd time,
60% 3rd time....

Anyway, thank you! I have fixed it now!

Bill

--- On Fri, 5/8/09, Jason Uher <jasonuher@gmail.com> wrote:

From: Jason Uher <jasonuher@gmail.com>
Subject: Re: [Discuss-gnuradio] a running problem with the USRP, i am
confused!
To: "Bill Stevenson" <bill.stevenson07@yahoo.com>,
discuss-gnuradio@gnu.org
Date: Friday, May 8, 2009, 4:35 PM

> Does it mean USRP could not keep on running for
> a long time or the USRP boards we are using have been broken? I do not know
> the reason for this problem. Please let me know what's wrong with the USRP.
> Thanks a lot!

I believe there is an issue with the costas loop implementation in one
of the older mpsk_receiver implementations where the phase offset
correction gets clipped rather than rolled over (ie, -2pi->2pi).  If
the offset is small it may take awhile for this error to show up.  If
you use the verbose costas loop and see the phase correction going up
to 2pi or down to -2pi and not rolling over you may have this issue.

Jason
This topic is locked and can not be replied to.