Message-Id: <7.0.1.0.1.20090910194758.018681e8@magma.ca>
Date: Thu, 10 Sep 2009 19:58:34 -0400
To: rsgb_lf_group@blacksheep.org
From: Bill de Carle <ve2iq@magma.ca>
In-Reply-To: <000001ca326f$b6ce1c00$0b01a8c0@weazle>
References: <211F6B38DA2544AD84B814000D47EDF6@AGB>
 <0F69884C983F4F198A9B4B4F276326AD@radiorummet>
 <171181B694684DD8A9131D31D307EB5B@JimPC>
 <000001ca326f$b6ce1c00$0b01a8c0@weazle>
Mime-Version: 1.0
Subject: Re: LF: Wolf Config Settings
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


At 07:37 PM 9/10/2009, J.B. wrote:
>Hello LFers,
>
>What are most of you fellows setting your Nr of frames value at
>in the Wolf Config screen?  How important is this setting as to
>its effect on decodes?  Thanks in advance for any/all replies.

Mine is set to 32 - but Rx is locked to GPS for good long term
stability and I let the sound card warm up a long time then key in
the exact sampling rate.  If the overall drift is substantial
it doesn't pay to use a long integration time because it reduces
the probability of seeing a sudden (but of short duration) upswing
in the signal quality because the averaging process will treat
all received frames equally, which implies any one frame with good
SNR won't count very much when competing with lots of others with
poor SNR.  I suppose one could come up with a formula based on
expected stabilities at Tx, Rx, QSB periods, etc.

Bill