|Subject:||Re: [Discuss-gnuradio] Message API questions|
|Date:||Wed, 26 Feb 2014 08:53:29 -0500|
I have a few questions regarding messages in GR.
1) Is it possible to mix-and-match the old style message sink/source blocks with the new style message passing API? Any guidance on how to make the connections? I didn’t have much luck with msg_connect. I don’t think the message sink/source blocks have an associated port name to make this possible. Perhaps that’s something worth adding internally?
2) I see 2 implementations of msg_queue, one in gr namespace and one in gr::messages namespace. What are the differences between these?
3) How does one achieve flow control with the new style message passing API? I have a use case in which I’m generating packets in one flowgraph and pushing them through a pdu_to_tagged_stream (P2TS) block to be modulated in another flowgraph. I believe I’m overwhelming the P2TS block’s queue because I get warnings about dropped messages. One hack I made was to insert a throttle block into the packet generating flowgraph. This helped a bit, but I have to guess the magic throttle rate at which I don’t fill up the queue. Is there a way to have P2TS block when its queue is full and therefore generate backpressure on the upstream flowgraph?
Discuss-gnuradio mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|