On Wed, May 14, 2014 at 4:26 PM, Martin Braun <martin.br...@ettus.com>wrote:
> On 14.05.2014 08:11, Activecat wrote: > >> Dear gurus, >> >> I am learning gnuradio Message Passing feature, but couldn't get >> desirable result. >> The Message seems published successfully, but not subscribed by the >> Message receiver. >> How to correct the error ..? >> > > Just to make sure: You did connect the ports in your flow graph? > That said, I've seen something like this recently. Maybe there's a bug... > needs investigating. > M > 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? 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)) System info: Gnuradio version = 3.7.3 OS = Debian jessie/sid, SMP Debian 3.13.10-1 x86_64 GNU/Linux
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio