Re: [Discuss-gnuradio] Message passing: boost::bind() not executing

Thank you very much Marcus. I was using the the scheduler ( *sudo GR_SCHEDULER=STS nice -n -10 python ./test.py* ) to start my flow graph, I did'nt realize before that the message passing needs more than one thread. Best On Tue, Aug 20, 2019 at 4:53 AM Müller, Marcus (CEL) wrote: > Hi! > > So

Re: [Discuss-gnuradio] Message passing: boost::bind() not executing

Hi! So, Occam's Razor first: Is it certain that gate_impl's general_work is really called regularly? Because: the message passing code here looks really good, and thus my first guess is that of the code which you sensibly omitted here, the rest of the general_work() somehow leads to the thing not

Re: [Discuss-gnuradio] Message passing to UHD: USRP source/sink

In the above-explained case scenario, I'm thinking of appending the csv to a dictionary and based on a loop, can I code (IN PYTHON) the work function of the block according to when there is 1, the corresponding channel frequency is sent as a message when it reads a change: So, firstly, Is it possib

Re: [Discuss-gnuradio] Message Passing Not Working

Hi, AFAIS, you call the output message port "gain", but try to publish to the message port "gain_port". When I changed it to use "gain", it seems to work. Best, Bastian On 07/22/2017 12:49 AM, Tellrell White wrote: In the attached flow graph, I've created a block, "gain setter" that takes

Re: [Discuss-gnuradio] Message passing from external program

Check out the ControlPort interface - https://gnuradio.org/redmine/projects/gnuradio/wiki/ControlPort On Sun, Feb 7, 2016 at 11:01 AM, Daniel Brogren wrote: > Hi all > > Im trying to change the freq, both the source but also in a filter, from an > external program. My first guess is that this can

Re: [Discuss-gnuradio] Message passing.

On Wed, Nov 4, 2015 at 3:06 PM, M. Ranganathan wrote: > Hello! > > I am building a monitor where capture of I/Q samples to a file is > triggered on an pluggable detection scheme. For example, I want to capture > say 10 seconds of I/Q samples when LTE is detected. > > Is this an appropriate place

Re: [Discuss-gnuradio] Message passing(connect) in C++

Marcus, thank you very much for your deep answer. Your proposal about the usage of your_block::detail()->input(0)->buffer()->link seem very interesting, so I shoulld evaluate if use this mechanism or only some memory allocation created with malloc. I'd prefer to simplify the life of user as much a

Re: [Discuss-gnuradio] Message passing(connect) in C++

Hi Marco, ok, I think it's best if I describe a bit of what happens behind the curtains: GRC is really just a graphical generator for python code. As soon as you hit the "generate" button (or the run button, where generating is done inherently), python code is written that has no connection, knowl

Re: [Discuss-gnuradio] Message passing(connect) in C++

I want to exchange data between adjacent blocks which are already connected through the GUI, without ask to the user to write additional code. So my approach would be: the upper block send down its name(through tags) and the lower block configure the communication, so I thought to take advantage f

Re: [Discuss-gnuradio] Message passing(connect) in C++

excuse me, I'm seeing the new API 3.7.7 of GNURadio which is changed. The "connect" is a member of gr::flowgraph which connects both blocks' ports and message ports: http://gnuradio.org/doc/doxygen/classgr_1_1flowgraph.html#af8678658129a819673a59555d030aaac Best, On Thu, Apr 30, 2015 at 4:15 PM

Re: [Discuss-gnuradio] Message passing(connect) in C++

Hi Marco, The top_block class has a member named: connect. You can use it in the main() to connect different blocks. However, if you want to dis/connect blocks within C++ blocks, you must pass top_block pointer to the class in some fashion. Once I did and I got errors because I didn't have accesse

Re: [Discuss-gnuradio] Message passing - issue with messages left in queues after running top block

On Tue, Jul 22, 2014 at 8:44 AM, Perper wrote: > Hi all, > > I've noticed that "Run to completion" works now in situation when > message passing is used, which is great! > I have a related question. I'm creating a block which uses message > passing, and run it once: > > tb = some_block(fn

Re: [Discuss-gnuradio] Message Passing

On Wed, May 14, 2014 at 10:25 PM, Tom Rondeau wrote: > On Wed, May 14, 2014 at 7:06 AM, Activecat wrote: > >> On Wed, May 14, 2014 at 6:49 PM, Koslowski, Sebastian (CEL) < >> sebastian.koslow...@kit.edu> wrote: >>> >>> I retried by putting the definition of on top of >> in the xml file, it wor

Re: [Discuss-gnuradio] Message Passing

On Wed, May 14, 2014 at 7:06 AM, Activecat wrote: > > On Wed, May 14, 2014 at 6:49 PM, Koslowski, Sebastian (CEL) < > sebastian.koslow...@kit.edu> wrote: > >> On 05/14/2014 12:29 PM, Activecat wrote: >> > I have then tested few combinations, it seems that a source block cannot >> > have a message

Re: [Discuss-gnuradio] Message Passing

On Wed, May 14, 2014 at 6:49 PM, Koslowski, Sebastian (CEL) < sebastian.koslow...@kit.edu> wrote: > On 05/14/2014 12:29 PM, Activecat wrote: > > I have then tested few combinations, it seems that a source block cannot > > have a message sink port. > > Is there such a restriction ..? > > Not that I

Re: [Discuss-gnuradio] Message Passing

On 05/14/2014 12:29 PM, Activecat wrote: > I have then tested few combinations, it seems that a source block cannot > have a message sink port. > Is there such a restriction ..? Not that I know of... Test message_sink_complex_source_test Custom None in message True

Re: [Discuss-gnuradio] Message Passing

On Wed, May 14, 2014 at 6:18 PM, Activecat wrote: > > On Wed, May 14, 2014 at 5:50 PM, Sylvain Munaut <246...@gmail.com> wrote: > >> Did you define the message port in the .grc XML file for your blocks ? >> Something like : >> >> >> portname >> message >> 1 >> >> >> Then they sh

Re: [Discuss-gnuradio] Message Passing

On Wed, May 14, 2014 at 5:50 PM, Sylvain Munaut <246...@gmail.com> wrote: > Did you define the message port in the .grc XML file for your blocks ? > > Something like : > > > portname > message > 1 > > > Then they should show as message port in the GRC UI and you need to > connect

Re: [Discuss-gnuradio] Message Passing

On 14.05.2014 11:35, Activecat wrote: On Wed, May 14, 2014 at 5:26 PM, Martin Braun mailto:martin.br...@ettus.com>> wrote: There's no msg_connect() call here -- that would be your problem. M I build the flowgraph using GRC. How to make correction? To correct this, connect the messag

Re: [Discuss-gnuradio] Message Passing

Hi, >> There's no msg_connect() call here -- that would be your problem. >> M > > > I build the flowgraph using GRC. How to make correction? > The complete top_block.py is as follows. Did you define the message port in the .grc XML file for your blocks ? Something like : portname mes

Re: [Discuss-gnuradio] Message Passing

On Wed, May 14, 2014 at 5:26 PM, Martin Braun wrote: > There's no msg_connect() call here -- that would be your problem. > M > I build the flowgraph using GRC. How to make correction? The complete top_block.py is as follows. #!/usr/bin/env python #

Re: [Discuss-gnuradio] Message Passing

On 14.05.2014 11:14, Activecat wrote: 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 Mess

Re: [Discuss-gnuradio] Message Passing

On Wed, May 14, 2014 at 4:26 PM, Martin Braun 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. >> H

Re: [Discuss-gnuradio] Message Passing

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 i

Re: [Discuss-gnuradio] message passing test

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Neil, yes, this can't work; you can only multiply two numbers if there are two numbers (factors). Which will never be the case, since there has not been a multiplication before the first factor. Message passing can't make an flowgraph that has a s

Re: [Discuss-gnuradio] message passing error

ssage --- From: Johan Carlsson To: MHMND Herath Cc: discuss-gnuradio@gnu.org Sent: Sat, 25 Jan 2014 09:41:07 -0500 (EST) Subject: Re: [Discuss-gnuradio] message passing error Looks like a a C++ or boost question? Are you experienced in using C++ templates? Regards, Johan On Sat, 25 Jan 2014

Re: [Discuss-gnuradio] message passing error

Looks like a a C++ or boost question? Are you experienced in using C++ templates? Regards, Johan On Sat, 25 Jan 2014, MHMND Herath wrote: Dear Sir When I trying to implement message passing between 2 blocks called a1_ff and a2_ff following error comes when comiling. I cannot trace it. Thanks

Re: [Discuss-gnuradio] Message passing as input and output in block (C++ coding)

Hi Josh, I've check the documentation and also my variables. I've found that my list is a PMT pair or PMT dict: std::cout << std::endl << "checking if pair:"

Re: [Discuss-gnuradio] Message passing as input and output in block (C++ coding)

Hi Josh, I've checked this information and it is very useful. I've solved several issues that I had before. However, it is still complaining when I post a BLOB_METADATA (which is a pmt_list) downstream. What I have is the following: BLOCK 1 --- > BLOCK 2 (both blocks use message passing as blobs

Re: [Discuss-gnuradio] Message passing as input and output in block (C++ coding)

> I generated the BLOB_METADATA as pmt::pmt_t type. However, I cannot post > blob_data because is related to _msg (in the previous example), which is a > gr_tag_t type. > There are two post_msg methods. The key/value version of the method is a convenience method that makes a gr_tag_t and sets ke

Re: [Discuss-gnuradio] Message passing as input and output in block (C++ coding)

Hi Josh, I've figured out this question. I just need to post this->post_msg(0,_msg); Since, _msg is a gr_tag_t. But, still is not clear for me how can I post a message as follows: this->post_msg(0, BLOB_METADATA,blob_data, _id); ? I generated the BLOB_METADATA as pmt::pmt_t type. However,

Re: [Discuss-gnuradio] Message passing as input and output in block (C++ coding)

Hi Josh, Thanks for the info. So, for example if I want to modify the blob_to_stream example as blob_to_blob (ie. input a message and then output a message). The .cc files is as shown below, but I got errors when I compile because of the type of variables: In member function ‘virtual int blob_to

Re: [Discuss-gnuradio] Message passing as input and output in block (C++ coding)

On 10/07/2012 09:56 PM, Jose Torres Diaz wrote: > Hi All, > > I have another question about the message passing technique. In this > opportunity, I would like to create a block that takes message as input, > but also that post message downstream as output. In my initial attempt, I'm > using the

Re: [Discuss-gnuradio] Message passing - PSDU block and sink connection

On 09/26/2012 12:47 AM, Jose Torres Diaz wrote: > Hi, > > I've just finished my block that generates PSDUs and then, it transmits > downstream subscribers using message passing mechanism. I am using as a > sink "Extras: Blob to Socket", but when I run my flowgraph in GNU Radio > Companion (after

Re: [Discuss-gnuradio] Message passing - PSDU block and sink connection

Hi Josh, I've attached the xml file for "my_block.xml". I don't have a .i file (like "my_block.i"), because it is using the "extras_blobs.i" file. I've attached for you extras_blob.i and I added some lines to that .i file in order to include "my_block". All the example is based on blob to stream

Re: [Discuss-gnuradio] Message passing - PSDU block and sink connection

On 09/26/2012 12:47 AM, Jose Torres Diaz wrote: > Hi, > > I've just finished my block that generates PSDUs and then, it transmits > downstream subscribers using message passing mechanism. I am using as a > sink "Extras: Blob to Socket", but when I run my flowgraph in GNU Radio > Companion (after