Re: [Discuss-gnuradio] flow graph reconfiguration when using tagged streams

2017-02-13 Thread Damindra Bandara
Dear Tim, Thank you for your response. Is there any example that you could point me to understand async blocks? Thanks, Damindra Message: 3 Date: Sun, 12 Feb 2017 16:33:37 -0500 From: Tim To: GNURadio Subject: Re: [Discuss-gnuradio] flow graph reconfiguration when using tagged streams

Re: [Discuss-gnuradio] flow graph reconfiguration when using tagged streams

2017-02-12 Thread Tim
Use async message blocks, whatever you are doing is probably a bad idea On 02/12/2017 04:29 PM, Damindra Bandara wrote: > Hi, > > I am trying to reconfigure a flow graph that uses tagged streams. When > I lock() and unlock() the flow graph(or stop()--> wait() and start()) > the blocks that uses ta

Re: [Discuss-gnuradio] Flow Graph Reconfiguration

2014-09-05 Thread Gould, Daniel N.
-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Flow Graph Reconfiguration On Sep 4, 2014, at 13:27, Gould, Daniel N. wrote: > FlowGraph 1: > [src] -> [filt] -> [modem-1] > > FlowGraph 2: > [src] -> [filt] -> [modem-2] > > FG-1 runs to completion, is then dis

Re: [Discuss-gnuradio] Flow Graph Reconfiguration

2014-09-04 Thread Kevin Reid
On Sep 4, 2014, at 13:27, Gould, Daniel N. wrote: > FlowGraph 1: > [src] -> [filt] -> [modem-1] > > FlowGraph 2: > [src] -> [filt] -> [modem-2] > > FG-1 runs to completion, is then disconnected. Then FG-2 is connected and > executed. For both flowgraphs the src and filt are the same. The mod