discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block


From: Martin Braun
Subject: Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block
Date: Wed, 20 Apr 2016 15:24:21 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

The tagged_stream_mux is an example of this kind of block. As Andrej
points out, you need to make sure every input signal is actually a
tagged stream.

Cheers,
M

On 04/20/2016 03:12 PM, Andrej Rode wrote:
> Hello Jenny, 
> 
> I can try to help you, but I'm not quite sure if I am right. If I am wrong I 
> will be corrected soon. 
> 
>>>> Generating: "/home/jenny/Tutorials/rx_ofdm.py"
>>>> Executing: "/home/jenny/Tutorials/rx_ofdm.py"
>>>> Using Volk machine: sse4_2_64_orc
>>>> gr::log :FATAL: geese_vcvc0 - Missing a required length tag on port 1 at
>>>> item #0
>>>> thread[thread-per-block[46]: <block geese_vcvc (1)>]: Missing length tag.
> 
> This error tells you that your block is missing a length tag in one of his 
> inputs. A Stream Tag on the first sample is a requirement for a tagged stream 
> block. This Stream Tag has to provide information about how much input data 
> your block has to process.
> I assume you don't have an tagged stream on each of your inputs and this 
> causes a problem for your tagged stream block. 
> 
> Best you provide a screenshot of your example flowgraph (the relevant parts). 
> Based on the error it is nothing inside of your block but the way you are 
> trying to feed it with samples. 
> 
> Best Regards, 
> Andrej
> 
> 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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