[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: |
Thu, 21 Apr 2016 11:02:48 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
On 04/20/2016 04:48 PM, Jingyi Sun wrote:
> tagged_stream_mux works when substituted for my block, so I think all of
> my inputs are tagged streams. Also, my inputs are coming from the
> outputs of OFDM_frame_equalizer, which I think propagates tagged streams?
Yes.
M
> I think it's an error somewhere in the code, but the changes I mentioned
> are the only changes I made between the block working and the block not
> working.
>
> My code is based on OFDM_frame_equalizer, but without the actual signal
> processing part. I will fill in my own signal processing after I know I
> can at least pass one out of three inputs along so that the outputs are
> the same as if this new block were bypassed.
>
>
>
>
> On Wed, Apr 20, 2016 at 6:24 PM, Martin Braun <address@hidden
> <mailto:address@hidden>> wrote:
>
> 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 <mailto:address@hidden>
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden <mailto:address@hidden>
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
- [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Jingyi Sun, 2016/04/20
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Jingyi Sun, 2016/04/20
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Andrej Rode, 2016/04/20
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Martin Braun, 2016/04/20
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Jingyi Sun, 2016/04/20
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block,
Martin Braun <=
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Jingyi Sun, 2016/04/21
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Jingyi Sun, 2016/04/22
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Jingyi Sun, 2016/04/23
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Martin Braun, 2016/04/24
- Message not available
- Re: [Discuss-gnuradio] Multiple Inputs in Tagged Stream Block, Martin Braun, 2016/04/24