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.

Hello,
I tried the DBPSK and DQPSK scheme with benchmark_tx.py and
benchmark_rx.py. I
found there is a problem with USRP. After having TX and RX rest for
20 mins, the communication between them are so good that the PDR
detected at the RX is almost 99%, but after those two USRPs run for a
while, say 10 mins, the communication quality deteriorates rapidly,
which means the synchronization was worsen. 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!
Bill

> 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