|
From: | Kyeong Su Shin |
Subject: | Re: [Discuss-gnuradio] E312 receiver gets stuck |
Date: | Tue, 20 Feb 2018 00:50:38 +0000 |
To whom it may concern:
I do not remember the structure of 'benchmark_rx.py', but the PSK/QAM demod blocks of GNU Radio do often fail if you feed in noise for a while. As
Mansour suspected, that is mainly due to the synchronization issues. The flowgraph does not stop, but loses synchronizations to the incoming signal and does not recover.
A few things that can be tried (assuming that the problem of 'benchmark_rx.py' is indeed the same blind synch issue):
1. Writing your own synchronization / demod blocks, instead of relying on the blind synchronization of the PSK/QAM demod blocks. (time-consuming, but often worth it). 2. Feed in data to the demod block when and only when the transmitter is actually transmitting. (maybe 'power sqeulch'?) 3. Try fixing the synchronization routine of the demod block. See: http://lists.gnu.org/archive/html/discuss-gnuradio/2017-10/msg00124.html (I am not sure what is the best way to correct the problem, or if anyone submitted a patch for this.) Regards, Kyeong Su Shin
보낸 사람: Mojtaba Mansour Abadi <address@hidden> 대신 Discuss-gnuradio <discuss-gnuradio-bounces+address@hidden>
보낸 날짜: 2018년 2월 20일 화요일 오전 4:12:19 받는 사람: address@hidden <address@hidden> 제목: Re: [Discuss-gnuradio] E312 receiver gets stuck I used Ettus USRP B210. I had this issue, no matter what modulation schemes I was implementing. What I noticed was the fact that if the signal power drops below a value, the whole receiver stopped and even the constellation was not updating. I think the receiver block diagrams couldn’t recover after a signal drop.
Sent from Mail for Windows 10
From: Niloofar Toorchi
Thank you Mansour, Which USRP did you use? E312? I know some one who used flowgraph in E310 but did not face any problem. I do not know whether this is related to USRP version or is a software issue.
Best, Niloofar
On Mon, Feb 19, 2018 at 8:05 AM, <address@hidden> wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |