[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss-gnuradio] Python message ports
From: |
Johannes Demel |
Subject: |
[Discuss-gnuradio] Python message ports |
Date: |
Tue, 14 May 2013 15:10:21 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5 |
Hi list,
I tried to use message ports with python blocks but I can't find
something like "register_msg_port_in" or similar. And asking google
didn't give me any results as well. So I can't register a message port.
This rises the question if it is possible to use message ports with
python blocks.
In my case it would be very useful as I want to create a block which is
only called a few times.
Also, I wanted to create QA code for my block and tried to use a
"message_sink" block. This block does not use the msg_connect method to
connect to a message queue. It demands a msg_queue object. Is there a
reason for this block not to use the msg_connect method?
GRC uses
self.blocks_message_sink_0=blocks.message_sink(gr.sizeof_gr_complex*1,
blocks_message_sink_0_msgq_out, False)
but this raises another error
NameError: global name 'blocks_message_sink_0_msgq_out' is not defined
That's not surprising as the variable is never declared.
I hope someone can clear things up.
- Johannes
- [Discuss-gnuradio] Python message ports,
Johannes Demel <=