[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Other block as parameter in GRC

From: Sebastian Koslowski
Subject: Re: [Discuss-gnuradio] Other block as parameter in GRC
Date: Tue, 19 Aug 2014 14:25:10 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0

On 08/19/2014 01:07 PM, Julius Durst wrote:
> Hi,
> how can I pass an other block from my flowgraph to a self written block 
> in the gnuradio-companion? What I want to do is invoking a method of 
> that passed block in my own one (or maybe there's an other way to do that?).
> I have tried passing the ID of the block to a parameter of type "raw", 
> but it says
> Param - <param_name>(param_key):
>       Value "<ID_of_ohter_block>" cannot be evaluated:
>       name '<ID_of_ohter_block>' is not defined in the block properties in 
> the GRC.
> I thought that is what raw was for?
> What I exactly want to do is switching filters or, what I am trying with 
> the above, change the taps of one filter, at runtime. So if you have any 
> suggestions for that, please also tell me.
raw is for python code. Blocks are not instantiated at design time so
they are not in the namespace when GRC does the FG validation. Consider
putting those taps in variable and use a callback. Or, if your tap
update is triggered from within the flowgraph, use message passing.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]