Re: Passing Tags or Additional Port Data to Change Parameters of Downstream Blocks

2024-04-20 Thread walter
Hi Matt, ++props for Ron's example of PMT tagging in C++ :-) Quick tip: as a person with strong/current Python skills and C++ expertise that's 20 years out-of-date, I've found that I can get "best results per unit time" by reading the C++ code/docs but coding my blocks and snippets in

Re: Passing Tags or Additional Port Data to Change Parameters of Downstream Blocks

2024-04-19 Thread Matt Clemons
Thank you Ron! This does look like exactly what I need. I almost reached out to you directly, seeing all the DrMpeg commits related to gnuradio DTV blocks. Thanks for your help and all the contributions you've made to the community. Matt On Thu, Apr 18, 2024 at 6:33 PM Ron Economos wrote: >

Re: Passing Tags or Additional Port Data to Change Parameters of Downstream Blocks

2024-04-18 Thread Ron Economos
Matt, Take a look at my DVB-S2 OOT. This is a different version of the DVB-S2 transmitter that implements VCM (as opposed to the regular CCM version included in GNU Radio). https://github.com/drmpeg/gr-dvbs2 It implements exactly what you're talking about to achieve VCM (Variable Coding

Re: Passing Tags or Additional Port Data to Change Parameters of Downstream Blocks

2024-04-18 Thread Federico 'Larroca' La Rocca
Hi, That's a great idea! You may take a look at several blocks that are already in GNU Radio and are configurable through messages. Signal Source comes to my mind. More "sophisticated" blocks also use messages for configuration. For instance, UHD USRP Source, or some blocks of our OOT module