On Wed, Feb 06, 2008 at 01:58:16PM -0500, Steven Clark wrote:
> > Your msg_source, which is a gr.message_source, is blocked, waiting for
> > new messages to arrive. In order to allow the second block chain to
> > exit, you need to send it a message that causes it to unblock. The
> > flowgraph sche
> Your msg_source, which is a gr.message_source, is blocked, waiting for
> new messages to arrive. In order to allow the second block chain to
> exit, you need to send it a message that causes it to unblock. The
> flowgraph scheduler thread that is running this chain will then see
> the indication
On 2/5/08, Steven Clark <[EMAIL PROTECTED]> wrote:
> 1) With this second block chain inside the top block, tb.wait() never
> returns. I can't even ctrl-c out of python, it's just stuck.
Your msg_source, which is a gr.message_source, is blocked, waiting for
new messages to arrive. In order to allo
On Jan 31, 2008 1:13 PM, Eric Blossom <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 31, 2008 at 10:49:50AM -0500, Steven Clark wrote:
> > Pardon the bump. Maybe I should simplify the question:
> >
> > With the packet modulator, is it possible to run the packet payload
> > bits through any kind of flow-g
On Thu, Jan 31, 2008 at 10:49:50AM -0500, Steven Clark wrote:
> Pardon the bump. Maybe I should simplify the question:
>
> With the packet modulator, is it possible to run the packet payload
> bits through any kind of flow-graph/block during the rx_callback?
Yes. You could push the bits back int
Pardon the bump. Maybe I should simplify the question:
With the packet modulator, is it possible to run the packet payload
bits through any kind of flow-graph/block during the rx_callback?
On Jan 27, 2008 6:39 PM, Steven Clark <[EMAIL PROTECTED]> wrote:
> 'lo all.
>
> I would like to place code i
