: [Discuss-gnuradio] Trouble posting messages to block's message port
I had this issue once and if I remember correctly, connecting the block
to the flowgraph (i.e. connect any block to your message port, even if
that port will never send messages) will make your message handler react
to messages
I had this issue once and if I remember correctly, connecting the block
to the flowgraph (i.e. connect any block to your message port, even if
that port will never send messages) will make your message handler react
to messages from your python code.
Hope this helps
Martin
Am 03.05.2013 19:4
On 05/03/2013 01:41 PM, Sean Nowlan wrote:
On 05/03/2013 01:26 PM, Marcus Müller wrote:
Hi Sean,
have you tried using tb.msg_connect(src, "out_port_id", dst,
"in_port_id") instead of tb.connect?
Cheers
Marcus
I'm trying to post a message to a port from top_block as opposed to
connecting th
On 05/03/2013 01:26 PM, Marcus Müller wrote:
Hi Sean,
have you tried using tb.msg_connect(src, "out_port_id", dst,
"in_port_id") instead of tb.connect?
Cheers
Marcus
I'm trying to post a message to a port from top_block as opposed to
connecting the output port of one block to the input of "
Hi Sean,
have you tried using tb.msg_connect(src, "out_port_id", dst,
"in_port_id") instead of tb.connect?
Cheers
Marcus
Am 03.05.2013 00:35, schrieb Sean Nowlan:
I'm trying to create a block that accepts messages and prints them out.
I created a block that extends gr_block and it has no strea
I'm trying to create a block that accepts messages and prints them out.
I created a block that extends gr_block and it has no stream ports: I'm
using gr_io_signature(0,0,0) for input and output. I am following the
guidance of this page:
http://gnuradio.org/doc/doxygen/page_msg_passing.html
Fr
