Josh Blum schrieb:
Markus,
I really believe that the gui is not freezing. What you see is a result
of the fact the the peak detect outputs a binary 1 or 0 signal.
Connect the peak detect to a char_to_float block, and then to a
numbersink. Setup the numbersink for a min of 0 and a max of 1.
Josh Blum josh at joshknows.com writes:
Also, add a few printfs to the work method,...
Do you mean it is better to make my own signal processing block to print ?
As i understand in,
http://www.gnu.org/software/gnuradio/doc/howto-write-a-block.html
the only way to make a signal processing
Josh Blum josh at joshknows.com writes:
Do you think that it might be possible for peak detector to output
always the same number at some frequencies?
I think not. The Peakdetector(with TH factor Rise and Fall) works and the
Peakdetector2 works not. Maybe there are some bugs in the
Markus,
I really believe that the gui is not freezing. What you see is a result
of the fact the the peak detect outputs a binary 1 or 0 signal.
Connect the peak detect to a char_to_float block, and then to a
numbersink. Setup the numbersink for a min of 0 and a max of 1. The
numbersink will
peak detector can output 1 or 0. What is it outputting?
feldmaus wrote:
Josh Blum josh at joshknows.com writes:
That says that throttling is not your issue. You are probably correct to
think that the peak detect block stopped outputting samples. -Josh
Is this because i did not configure
Josh Blum josh at joshknows.com writes:
peak detector can output 1 or 0. What is it outputting?
I get 1 and 0 when it is not freezed.
I uploaded a screenshot, but i am not sure whether this works,
http://img228.imageshack.us/my.php?image=peakdetected.jpg
There you can see that i get 1 at a
feldmaus wrote:
Josh Blum josh at joshknows.com writes:
peak detector can output 1 or 0. What is it outputting?
I get 1 and 0 when it is not freezed.
I uploaded a screenshot, but i am not sure whether this works,
http://img228.imageshack.us/my.php?image=peakdetected.jpg
There you can see
Josh Blum josh at joshknows.com writes:
That says that throttling is not your issue. You are probably correct to
think that the peak detect block stopped outputting samples. -Josh
Is this because i did not configure the Peak-Detector correctly,
or because it is a bug ?
Regards Markus
feldmaus feldmann_markus at gmx.de writes:
Hi All,
i still read in the gnuradio documentation, that we can prevent
freezing graphical elements by inserting the throttle element before,
but how can i locate which element is freezed ?
Is there any hlp in grc or python modules which can be
feldmaus wrote:
feldmaus feldmann_markus at gmx.de writes:
Hi All,
i still read in the gnuradio documentation, that we can prevent
freezing graphical elements by inserting the throttle element before,
but how can i locate which element is freezed ?
Is there any hlp in grc or python modules
Josh Blum schrieb:
feldmaus wrote:
feldmaus feldmann_markus at gmx.de writes:
Hi All,
i still read in the gnuradio documentation, that we can prevent
freezing graphical elements by inserting the throttle element before,
but how can i locate which element is freezed ?
Is there any hlp in
-Josh
Hi and thanks for your response,
i am using a usrp-source and a fft-sink and peakdetect+scope-sink.
only the screen with the wave form freezes, the buttons of the scope
and the fft sink are not freezing. This seems to appear mostly when
there are many peaks i think, but i can not
Josh Blum schrieb:
-Josh
Hi and thanks for your response,
i am using a usrp-source and a fft-sink and peakdetect+scope-sink.
only the screen with the wave form freezes, the buttons of the scope
and the fft sink are not freezing. This seems to appear mostly when
there are many peaks i think,
Have you removed ALL gr.throttle blocks from your flowgraph?
Dimitris Symeonidis
If you think you're too small to make a difference, try sleeping with a
mosquito! - Amnesty International
On Tue, Apr 14, 2009 at 21:13, Markus Feldmann feldmann_mar...@gmx.dewrote:
Josh Blum schrieb:
-Josh
14 matches
Mail list logo