On Wed, Feb 26, 2014 at 9:26 AM, Nowlan, Sean <sean.now...@gtri.gatech.edu> wrote: > > > From: Aditya Dhananjay [mailto:adi...@cs.nyu.edu] > Sent: Wednesday, February 26, 2014 8:53 AM > To: Nowlan, Sean > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] Message API questions > > > On Wed, Feb 26, 2014 at 8:45 AM, Nowlan, Sean <sean.now...@gtri.gatech.edu> > wrote: > > 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? > > > > I'm not sure I completely understand your question. > > > > Have you looked at the OFDM Tx/Rx examples in PATH/gr-digital/examples/ofdm? > The flowgraph is a combination of standard connections within blocks, along > with a message passing connection (look at the header/payload demux block). > > > > Thanks! What I was referring to are the gr::blocks::message_source and > gr::blocks::message_sink blocks. They don't use the new style message > passing API in which you register ports and message handlers. Instead, > gr::blocks::message_source has an internal message queue. It blocks in > within its work function waiting for a message to enter the queue. What I'm > wondering is how to connect a new style block's message output with the > input to this block, and the inverse case for connecting a > gr::blocks::message_sink to a new style block's message input.
The message queues (old) and async messages (new) won't really work well together. You'd have to have some translation between them. Tom > > Sean _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
