# Problem with benchmark\_tx.py with "--discontinuous"

**URL:** <https://www.ruby-forum.com/t/problem-with-benchmark-tx-py-with-discontinuous/227628>\
**Category:** GNU Radio\
**Created:** [March 21, 2013, 9:56pm UTC](https://www.ruby-forum.com/t/problem-with-benchmark-tx-py-with-discontinuous/227628 "2013-03-21T21:56:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![SahooS\_Anirudha](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/a87d85/32.png) [@SahooS\_Anirudha](https://www.ruby-forum.com/u/SahooS_Anirudha)\
**Post date:** [March 21, 2013, 9:56pm UTC](https://www.ruby-forum.com/t/problem-with-benchmark-tx-py-with-discontinuous/227628/1 "2013-03-21T21:56:04Z")

</div>

Hi,  
When I run benchmark\_tx.py with “-discontinuous” flag ON, I notice  
the following problem:

When the transmitter goes to sleep (for 1 sec), the receiver TIMEOUT  
(which is fine).  
But then when the txmitter wakes up and sends the next 5 packets, the  
receiver consistently does not  
receive the first packet (of this set of 5 packets). Occasionally, I see  
the rcvr does not  
get the first two packets.  
So, I think there is some problem when packets are sent after a  
period of “lull”  
which leads to very first packet (after a TIMEOUT) being lost.

Can anyone think of what could be wrong with the ofdm implementation  
which may  
lead to this problem?

I am running gnuradio 3.6.2 on USRP N210.

thanks and regards

–Anirudh Sahoo  
Advanced Network Technology Div.  
National Institute of Standards and Technology (NIST)  
100 Bureau Drive,  
Gaithersburg, MD - 20878  
Room - B230, bldg.- 222  
Phone- 301-975-4439
