Florian - Please don't e-mail the same question to the list in multiple threads - it actually makes it more difficult for people to help you in a coherent manner.
Switching between RX and TX on the XCVR daughterboard should have very minimal overhead - certainly not 6 ms. As soon as it sees the first TX packet, it should automatically switch. It is possible that tunnel.py is not properly closing the TX stream, and thus confusing the USRP. Your colleague might be on to something - have you looked through the tunnel.py source to see how it is handling the TX packets? Cheers, Ben On Fri, Feb 3, 2012 at 4:28 AM, Florian Schlembach < florian.schlemb...@tu-ilmenau.de> wrote: > Trying out the tunnel.py example, we are transmitting a ping request > between two USRP2s. The receiving USRP should respond immediately with a > ping reply what the outpout is also saying. > At all, this ping reply is not send. We can bypass this by deploying a > time.sleep(0.05) at the RX-USRP before sending the ping reply > (txpath.send_pkt(payload)). Thus, the transmission is left behind for 50ms > which is not very convenient. > > Is it because the hardware components have to settle and the tx/rx > switching takes some time? Or might there be some configuration settings? A > colleague of mine is supposing something about different transmitting mode > like streaming and sending just bursts? > > Thanks a lot in advance, I really appreciate your help! > > > ______________________________**_________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/**listinfo/discuss-gnuradio<https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
