---
>> From: Matt Ettus
>> Date:2014/10/16 22:42 (GMT+00:00)
>> To: John Malsbury
>> Cc: David Halls ,GNURadio
>> Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
>>
>>
>>
>> On Thu, Oct 16, 2014 at 8:40 AM, John Malsbury <
>>
From: Matt Ettus
Date:2014/10/16 22:54 (GMT+00:00)
To: David Halls
Cc: John Malsbury ,GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
On TX, if you need your first sample to be valid and everything settled in the
radio, you should zero pad ahead of it. If you need your
t: Re: [Discuss-gnuradio] Source Block - Flow Control
>
>
>
> On Thu, Oct 16, 2014 at 8:40 AM, John Malsbury <
> jmalsbury.perso...@gmail.com> wrote:
>
>> I'm happy this is working for you, David. So do I understand
>> correctly, that the adding tx_time finally
Original message
From: Matt Ettus
Date:2014/10/16 22:42 (GMT+00:00)
To: John Malsbury
Cc: David Halls ,GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
On Thu, Oct 16, 2014 at 8:40 AM, John Malsbury
mailto:jmalsbury.perso...@gmail.com>> wrote:
I&#
On Thu, Oct 16, 2014 at 8:40 AM, John Malsbury wrote:
> I'm happy this is working for you, David. So do I understand correctly,
> that the adding tx_time finally made the MIMO case work?
>
> I'd never done burst transmission with multiple USRP outputs. I'm not
> totally surprised but I wasn't s
014/10/16 16:40 (GMT+00:00)
To: David Halls
Cc: Matt Ettus ,GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
I'm happy this is working for you, David. So do I understand correctly, that
the adding tx_time finally made the MIMO case work?
I'd never done burst t
;
>
>
>
>
> *From:* John Malsbury [mailto:jmalsbury.perso...@gmail.com]
> *Sent:* 15 October 2014 20:03
>
> *To:* David Halls
> *Cc:* Matt Ettus; GNURadio
> *Subject:* Re: [Discuss-gnuradio] Source Block - Flow Control
>
>
>
> H.. I've never done b
2014 20:03
To: David Halls
Cc: Matt Ettus; GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
H.. I've never done burst transmissions with a 2x MIMO case. That may or
may not put a minor wrinkle in things. Let's go for the gusto and try this
anyway...
(or we
dea of how to even do the simpler
>> idea, that I had thought of… I need to basically trigger the source at
>> certain intervals. How does the message queue interact with the block, does
>> the program flow jump to ‘parse_header_data_msg()’ automatically when a
>> message arrives?
>>
>
message arrives?
>
>
>
> DH
>
>
>
> *From:* John Malsbury [mailto:jmalsbury.perso...@gmail.com]
> *Sent:* 14 October 2014 23:42
> *To:* David Halls
> *Cc:* Matt Ettus; GNURadio
>
> *Subject:* Re: [Discuss-gnuradio] Source Block - Flow Control
>
>
>
&g
2014 23:42
To: David Halls
Cc: Matt Ettus; GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
In the implementation I have in mind, the upstream logic didn't make decisions
on when the data generating block should generate data per se... Instead, the
upstream block pro
umber of calls? and is there anyway to know when I can
> stop blocking? What will fill the buffers further down the chain?
>
> thanks,
>
> David
>
>
> Original message
> From: Matt Ettus
> Date:2014/10/14 22:56 (GMT+00:00)
> To: David Halls
>
elease a packet from
> the source?
>
> David
>
>
> Original message
> From: John Malsbury
> Date:2014/10/14 23:08 (GMT+00:00)
> To: David Halls
> Cc: Matt Ettus ,GNURadio
> Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
>
> Davi
0)
To: David Halls
Cc: Matt Ettus ,GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
David,
Perhaps you can use an async message to trigger the blocks output?
In some applications that require filler between valid data frames, I've seen
people throttle based off of the
t; need to output something from the block, won't I? This will then propagate
>> and fill the buffers?
>>
>> Thanks,
>>
>> David
>>
>>
>> Original message
>> From: Matt Ettus
>> Date:2014/10/14 19:09 (GMT+00:00)
>> To: Jeff Long
know when I can stop
blocking? What will fill the buffers further down the chain?
thanks,
David
Original message
From: Matt Ettus
Date:2014/10/14 22:56 (GMT+00:00)
To: David Halls
Cc: Jeff Long ,GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
No, if you
nal message
> From: Matt Ettus
> Date:2014/10/14 19:09 (GMT+00:00)
> To: Jeff Long
> Cc: GNURadio
> Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
>
>
> Jeff,
>
> If there is a hardware device like a USRP in the chain, then you should
> not u
ng
Cc: GNURadio
Subject: Re: [Discuss-gnuradio] Source Block - Flow Control
Jeff,
If there is a hardware device like a USRP in the chain, then you should not use
a throttle block. What you are seeing is the initial startup burst. When
everything starts up, all the buffers are empty, and GNU
scuss-gnuradio] Source Block - Flow Control
Agree the throttle it not the best solution. David - what is your
source, and what problem are those 1000's of vectors causing at startup?
- Jeff
On 10/14/2014 06:08 PM, Matt Ettus wrote:
>
> Jeff,
>
> If there is a hardware device li
Agree the throttle it not the best solution. David - what is your
source, and what problem are those 1000's of vectors causing at startup?
- Jeff
On 10/14/2014 06:08 PM, Matt Ettus wrote:
Jeff,
If there is a hardware device like a USRP in the chain, then you should
not use a throttle block.
Jeff,
If there is a hardware device like a USRP in the chain, then you should not
use a throttle block. What you are seeing is the initial startup burst.
When everything starts up, all the buffers are empty, and GNU Radio will
generate data until something backs up. Once they fill up, you are se
Should have mentioned ... set the throttle rate just slightly higher
than what the chain would consume at steady state when all the buffers
are filled and the USRP is transmitting. How well this works depends on
what the rest of the chain looks like.
- Jeff
On 10/14/2014 05:52 PM, Jeff Long w
Use a throttle block immediately after your source block, setting the
vector size to match your source.
- Jeff
On 10/14/2014 04:34 PM, David Halls wrote:
Dear All,
I am wondering how to add some flow control to a source block, so that
it doesn’t fire out items so quickly.
Later stages of my
23 matches
Mail list logo
