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 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. On Mon, Feb 19, 2018 at 8:05 AM, <address@hidden> wrote: I had the same problem. Even when I built the flowgraph the problem remained. I think it’s coming from the stages related to signal clock/phase/frequency recovery. Most of these blocks are working as a state machine. For any reason, when the received signal power drops, they probably go to an unknown state. Unfortunately these blocks have no reset input to initialise them so what you have to do is to re-run the program. There might be a solution if you use code. But I haven’t used coding. Hi All, I am using USRP E312. I used the available examples by Gnuradio, benchmark_{rx,tx}.py to have a simple communication between transmitter and receiver. I noticed that when the transmitter pauses sending, the receiver freezes somehow and when the transmitter resumes packet transmission, the receiver cannot receive anymore. Has any one experienced the same problem? Do you think building flowgarph can solve this issue?
_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
|