On 3 May 2010 11:28, Umair Naeem wrote:
> Sometimes When I run my GRC flow graph it gives following error and the
> program runs very slowly and sometimes GRC also crashes...
>
> (python: (no.) ): Gtk:CRITICAL **:gtk_progress_set_percentage: assertion
> 'percentage >= 0 && percentage <= 1.0' fai
Sometimes When I run my GRC flow graph it gives following error and the program
runs very slowly and sometimes GRC also crashes...
(python: (no.) ): Gtk:CRITICAL **:gtk_progress_set_percentage: assertion
'percentage >= 0 && percentage <= 1.0' failed
the no. contains value like 3031, 2986 etc...
Matt Ettus wrote:
aU == audio underrun (not enough samples ready to send to sound card sink)
uU == USRP underrun (not enough sample ready to send to USRP sink)
uO == USRP overrun (USRP samples dropped because they weren't read in time.
How big are the USRP buffers?
On Mon, Feb 21, 2005 at 05:26:01PM -0600, Meenal wrote:
> Hi all,
> I am writing FM TX and RX scripts similar to the FSK TX and RX scripts
> found in gnuradio-examples/python/usrp1
>
> I have noticed that when running these scripts, they seem to work
> correctly, but strange characters like "aU
aU == audio underrun (not enough samples ready to send to sound card sink)
uU == USRP underrun (not enough sample ready to send to USRP sink)
uO == USRP overrun (USRP samples dropped because they weren't read in time.
___
Discuss-gnuradio mailing
Replying to my own query :) but I noticed that on reducing the FFT window
from 512 to 256 points, I got stable FFT outputs. A few
"aUaU.."characters do appear still , but its much better than
before.
Still I do not understand why this happens , so will be glad if anyone
wants to shed some light
Hi all,
I am writing FM TX and RX scripts similar to the FSK TX and RX
scripts found in gnuradio-examples/python/usrp1
I have noticed that when running these scripts, they seem to work
correctly, but strange characters like "aUaU..." appear
on my session window and continue appearing till I te
