[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnuradio-discuss
Subject:    Re: [Discuss-gnuradio] tb.start(), tb.wait() or tb.stop() dows not work ... help
From:       Tom Rondeau <tom () trondeau ! com>
Date:       2013-09-25 16:57:07
Message-ID: CA+SzT6gcMPws+uvEFGd-iL7nFrTXpeUvBsrivaM1FmDUHwZcmA () mail ! gmail ! com
[Download RAW message or body]

On Mon, Sep 23, 2013 at 8:07 PM, shakib034 <shakib034@live.com> wrote:
> I am new to GNURADIO environment.
>
> I want the flow graph that i am working with to turn ON and OFF with 5 sec
> of interval.
>
> I tried  tb.start(), tb.wait(), tb.stop() and sleep(5).
>
> But that is not working.
>
> whenever I try to replace "tb.Run(True)" with any thing the program does not
> work.
>
> Any suggestion will be greatly appreciated.
>
> Thanks.

You probably don't want to be toggling the flowgraph on and off
constantly like this, anyways. That's a very inexact way of handling
it. You'll want some kind of gating block that handles this more
appropriately.

But regardless, you're method for doing this wouldn't work, anyways,
since you have the order wrong. The start function is a non-blocking
call that starts the flowgraph working. The wait is a blocking call
that sits there and waits for the flowgraph to finish. In your code,
you're never getting past the wait stage. You'd want this instead:

tb.start()
sleep(5)   # Let the flowgraph run for some amount of time.
tb.stop()
tb.wait()   # not really necessary, but makes sure the stop() call
propagates to all blocks before moving on.
sleep(5)   # wait 5 seconds before doing anything (like in a while loop)

Like I said, this isn't the best way to be accurate about how long
things run and stop for, but it'll get you in the right direction.

-- 
Tom
GRCon13 Oct. 1 - 4
http://www.trondeau.com/grcon13


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic