Re: [Discuss-gnuradio] Message Passing

[Martin Braun]

On 14.05.2014 11:14, Activecat wrote:
> Both blocks (message sender block, message receiver block) are source
> blocks, both are directly connected to the inputs of a divider blocks,
> i.e. the message receiver block is not at the downstream of the message
> sender block.  I guess this is ok because Message Passing is for
> downstream blocks to communicate to upstream blocks. Is this correct?

The message passing API doesn't really care about who's upstream for the 
streaming API.

> This is part of the top_block.py generated by GRC, to illustrate the
> flowgraph.
>
>          ##################################################
>          # Blocks
>          ##################################################
>          self.blocks_head_0 = blocks.head(gr.sizeof_int*1, 10)
>          self.blocks_divide_xx_0 = blocks.divide_ii(1)
>          self.activecat_message_source1_0 = activecat.message_source1()
>          self.activecat_message_sink1_0 = activecat.message_sink1()
>          self.activecat_integer_sink3_0 = activecat.integer_sink3(False,
> True, "Integer1")
>
>          ##################################################
>          # Connections
>          ##################################################
>          self.connect((self.blocks_divide_xx_0, 0), (self.blocks_head_0, 0))
>          self.connect((self.blocks_head_0, 0),
> (self.activecat_integer_sink3_0, 0))
>          self.connect((self.activecat_message_source1_0, 0),
> (self.blocks_divide_xx_0, 0))
>          self.connect((self.activecat_message_sink1_0, 0),
> (self.blocks_divide_xx_0, 1))

There's no msg_connect() call here -- that would be your problem.

M