Hi David,
For these cases, I typically recommend building an adjustable block that has a
message port input, and one or multiple blocks that have message port outputs.
You can, for example, write a multiply block that has one stream in-and one
steam output, and does register_message_port_in, and has a message handler that
updates the factor used internally for multiplication in a thread-safe manner.
Then, you'd write something that is a stream sink, I.e. only has an input for
samples, but based on some condition, sporadically sends a message to the
aforementioned block. That way, you get asynchronous cooperation in GNU radio.
I'm on my phone, currently, but if you look for the "GNU radio guided
tutorials", you'll find a section on message passing. In the GNU radio doxygen,
you'll find a reference for the typical command syntax that GNU radio devs
usually agree on using.
Best regards,
Marcus
Am 23. September 2015 13:12:20 MESZ, schrieb David Halls
<david.ha...@toshiba-trel.com>:
>?Hi guys,
>
>
>I am familiar with using function probes to update values to blocks.
>This is straightforward with built in blocks like Multiply Const, where
>the input is underline in the GRC dialogue box.
>
>
>How do I create a block, specifically a Python block, that allows me to
>update parameters in this fashion so that they are not fixed at
>runtime?
>
>
>Regards,
>
>
>David
>
>________________________________
>
>NOTE: The information in this email and any attachments may be
>confidential and/or legally privileged. This message may be read,
>copied and used only by the intended recipient. If you are not the
>intended recipient, please destroy this message, delete any copies held
>on your system and notify the sender immediately.
>
>Toshiba Research Europe Limited, registered in England and Wales
>(2519556). Registered Office 208 Cambridge Science Park, Milton Road,
>Cambridge CB4 0GZ, England. Web: www.toshiba.eu/research/trl
>---------------------------------------------------------------------------------------
>This email has been scanned for email related threats and delivered
>safely by Mimecast.
> For more information please visit http://www.mimecast.com
>---------------------------------------------------------------------------------------
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Discuss-gnuradio mailing list
>Discuss-gnuradio@gnu.org
>https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
