svn co svn://206.216.146.154/svn/repos_sdr_dttsp/trunk dttsp
'Eric Blossom' wrote:
On Wed, Sep 27, 2006 at 01:44:34PM -0400, Robert W McGwier wrote:
The feedforward AGC system in DttSP is more complex in that it is two
track (fast and "user set"). I believe I already mentioned this so I
On Wed, Sep 27, 2006 at 01:44:34PM -0400, Robert W McGwier wrote:
> The feedforward AGC system in DttSP is more complex in that it is two
> track (fast and "user set"). I believe I already mentioned this so I
> won't go over it again. But let me reiterate one important feature of
> our work.
The feedforward AGC system in DttSP is more complex in that it is two
track (fast and "user set"). I believe I already mentioned this so I
won't go over it again. But let me reiterate one important feature of
our work. One of the things that was important to its success as a
feedforward ag
On Mon, Sep 25, 2006 at 11:35:33PM -0400, Tom Rondeau wrote:
> Eric,
>
> Here's a brief write-up on the tests I ran for the AGC loops. It looks like
> the feedforward has a slight advantage over most of the test cases.
>
> I thought I'd email this to the listserv in case anyone is interested in
Eric,
Here's a brief write-up on the tests I ran for the AGC loops. It looks like
the feedforward has a slight advantage over most of the test cases.
I thought I'd email this to the listserv in case anyone is interested in the
digital modulations. Basically, we're working on getting stable DBPSK
On Thu, Sep 21, 2006 at 12:20:50PM -0400, Robert W McGwier wrote:
> Eric Blossom wrote:
>
> >On Tue, Sep 19, 2006 at 01:36:55PM -0400, Robert W McGwier wrote:
> >
> >>Tom:
> >>
> >>A good agc has at least two time constants. One for attack and one for
> >>decay. Your attack is much too slow.
>
Bob McGwier wrote:
Eric Blossom wrote:
On Tue, Sep 19, 2006 at 01:36:55PM -0400, Robert W McGwier wrote:
Tom:
A good agc has at least two time constants. One for attack and one
for decay. Your attack is much too slow.
tmp = (reference - sqrt(real(y)^2 + imag(y)^2));
rate = rate1;
if
Eric Blossom wrote:
On Tue, Sep 19, 2006 at 01:36:55PM -0400, Robert W McGwier wrote:
Tom:
A good agc has at least two time constants. One for attack and one for
decay. Your attack is much too slow.
tmp = (reference - sqrt(real(y)^2 + imag(y)^2));
rate = rate1;
if tmp > gainrate
On Tue, Sep 19, 2006 at 01:36:55PM -0400, Robert W McGwier wrote:
> Tom:
>
> A good agc has at least two time constants. One for attack and one for
> decay. Your attack is much too slow.
>
> tmp = (reference - sqrt(real(y)^2 + imag(y)^2));
> rate = rate1;
> if tmp > gainrate = rate2;
>
uradio mailing list'
> Subject: Re: [Discuss-gnuradio] AGC loop
>
> Tom:
>
> A good agc has at least two time constants. One for attack and one for
> decay. Your attack is much too slow.
>
> tmp = (reference - sqrt(real(y)^2 + imag(y)^2));
> rate = rate1;
> i
Tom:
A good agc has at least two time constants. One for attack and one for
decay. Your attack is much too slow.
tmp = (reference - sqrt(real(y)^2 + imag(y)^2));
rate = rate1;
if tmp > gainrate = rate2;
gain += tmp*rate;
rate2 is decay (where gain needs to be increased) and rate1 is
Do you already have some extra "sacrificial bits" that you send out to
allow for the AGC to settle? How long is it taking for the AGC to
settle?
You could try adding some extra sacrificial bits that you ramp up when
you transmit to try to allow for steady tracking in the AGC loop
instead of havi
Ok, so I've been working on the digital modulations, and everything works
great except when I put in the AGC loop. It jumps up in gain when there is
no signal applied and then takes too long to converge when the signal comes
in. The result is that it almost always misses the first packet before
con
13 matches
Mail list logo
