|Subject:||Re: [Discuss-gnuradio] Tunnel.py exception|
|Date:||Wed, 27 Apr 2011 14:39:26 +0200|
Hello William, Hello David,
i had this problem too.
After a short time period the exception was thrown.
I found out that the gnu which is the receiver cannot handle the speed of the sender – gnu so the exception was raised. I inserted some time.sleep()’s in the sender and the exception was gone.
Von: address@hidden [mailto:discuss-gnuradio-bounces+th=thomashauer.address@hidden Im Auftrag von William Cox
I've recently been using tunnel.py for 1/2 hr tests with no problems. I'm using the basic_tx/rx boards with a low frequency (5 MHz) and 1 Mbit datarate.
On Thu, Apr 21, 2011 at 10:31 AM, David Barton <address@hidden> wrote:
I am working with two USRPS wired connection with 25 dB attenuator between them so I didnt expect to much corruption of the packets.
The error seems to occur quicker at lower bit rates for some reason , like around after 10s of minutes for below 250 kbps and more like after an hour or more for 1 Mbps. Unfortunatly this makes it unusable for longer duration lower bandwidth tests until I find a way to fix the problem.
Has anyone else had this problem with tunnel.py?
On Wed, Apr 20, 2011 at 9:25 AM, David Barton <address@hidden> wrote:
I am running tunnel.py on gnuradio 3.3.0 . It run successfully for a while but after a period of time (around an hour) the following exception prints out:
I think that the problem is when the receiver thinks it has a zero-length packet (that is, something gets screwed up with the header and it sees 0's there). I'm not positive that this is the real problem, but I'd say it has something to do with a packet getting corrupted in a particular way that's causing this to happen.
We would need to put some protections into the unmake_packet to handle this as a dropped packet and then continue, once we find the exact problem.
|[Prev in Thread]||Current Thread||[Next in Thread]|