Hi Miguel,
:)
Having had a night of sleep:
Normally in GNU Radio, you've got input- and output buffers, and if
there's no space in your output buffer, you can't process input, so you
stall until there's space in your output buffer.
That's how the throttle block works: by not taking samples from
Sadly, we all need some sleep...
Well, thanks, A LOT! I'll try that.
Have a good night, you deserve a statue or a Nobel or something like that!
Best regards,
Miguel
On 22-03-2016 22:41, Marcus Müller wrote:
Indeed, there seems to be a problem here; sadly, I'll really need some sleep
tonight ;)
Indeed, there seems to be a problem here; sadly, I'll really need some
sleep tonight ;)
To answer your question, yes, Packet Encoder is really old and IMHO
should be deprecated in favor of the architecture you'd find in the
ofdm_tx.grc example (should be installed somewhere like
As an attachment I send the .grc on which I'm doing tests.
So:
- with head and/or throttle between source and packet encoder -> fine
- bypassing Head and Throttle -> huge file
- bypassing Head, Throttle and Encoder -> fine
I answered your questions below.
Another question: I'm
Hi Miguel,
On 22.03.2016 21:54, Miguel Santos wrote:
>
> On 22-03-2016 20:32, Marcus Müller wrote:
>> Hi Miguel,
>>
>> On 22.03.2016 17:14, Miguel Santos wrote:
>>> Yes, it's set to repeat.
>> oh!
>>> My real flow graph ends with a file sink, but
>>> here, as an example to test which block was
On 22-03-2016 20:32, Marcus Müller wrote:
> Hi Miguel,
>
> On 22.03.2016 17:14, Miguel Santos wrote:
>> Yes, it's set to repeat.
> oh!
>> My real flow graph ends with a file sink, but
>> here, as an example to test which block was the problem, I used a number
>> sink just to be able to run it
Hi Miguel,
On 22.03.2016 17:14, Miguel Santos wrote:
> Yes, it's set to repeat.
oh!
> My real flow graph ends with a file sink, but
> here, as an example to test which block was the problem, I used a number
> sink just to be able to run it and test it.
But then, how does your flow graph decide
Hi Marcus, thanks for your answer.
Yes, it's set to repeat. My real flow graph ends with a file sink, but
here, as an example to test which block was the problem, I used a number
sink just to be able to run it and test it.
I've made more tests and if I switch Throttle with Packet Encoder, it's
Hi Miguel,
I assume your Vector Source is not set to "Repeat"? Or how does your
Flow graph Terminate?
Generally, no block can modify its input buffer; hence, what File Sink
"sees" as an input number sequence must be identical (unless we really
have a bad memory access bug at hand, which I don't
Hi all!
While I was using the block Packet Encoder I realized that my input file
(saved before that block) becomes a lot bigger.
So I made a simple example to show that problem.
Vector Source ---> Packet Encoder ---> Throttle ---> Number Sink
---> File Sink
Just to make it clear,
10 matches
Mail list logo
