Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-df02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 16B9238000088; Sat, 7 Apr 2012 06:26:21 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1SGSpZ-0000B2-O7 for rs_out_1@blacksheep.org; Sat, 07 Apr 2012 11:25:17 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1SGSpZ-0000As-1O for rsgb_lf_group@blacksheep.org; Sat, 07 Apr 2012 11:25:17 +0100 Received: from imr-db03.mx.aol.com ([205.188.91.97]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1SGSpX-00008C-B4 for rsgb_lf_group@blacksheep.org; Sat, 07 Apr 2012 11:25:17 +0100 Received: from mtaout-db01.r1000.mx.aol.com (mtaout-db01.r1000.mx.aol.com [172.29.51.193]) by imr-db03.mx.aol.com (8.14.1/8.14.1) with ESMTP id q37AP9vF018062 for ; Sat, 7 Apr 2012 06:25:09 -0400 Received: from White (nrbg-4d073cd9.pool.mediaWays.net [77.7.60.217]) by mtaout-db01.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id A8D28E0000A9 for ; Sat, 7 Apr 2012 06:25:08 -0400 (EDT) Message-ID: <07E161587DA646DCBC41A19A9D7EC3C2@White> From: "Markus Vester" To: References: <4F801932.4814.48CC805@mike.dennison.ntlworld.com> Date: Sat, 7 Apr 2012 12:25:06 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1333794309; bh=1K+66yD248i5HR/wBCoTRckoqOAbA0CXjDUFafmXDa8=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=R0A6f8bN9hg9V06TzZnTXE+ocDvQAEIrsPkQIlwaUHOuf/d7Frm90uyfR+lfmkAw2 Z3ir8KN4z25UuAzAb2LR4K5NOGXGzrpc6Isg9LddA2XvWlz2blIgDaaJMDtG3IGD/k Wrs1OMA6zGbvHv2L+ppLP1GMW6cVVLjKGuaHUTXc= X-AOL-SCOLL-SCORE: 0:2:435205792:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: Argo vs SpecLab - DCF39 bursts Content-Type: multipart/alternative; boundary="----=_NextPart_000_001A_01CD14B9.77039080" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:474579776:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m005.1 ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d40d64f80164d6d22 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_001A_01CD14B9.77039080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Mike, you have probably selected Argo's visual AGC button on the bottom left, = which is on by default. This does not really suppress interference, but = scales each display column to the same average brightness of the noise. = So during a strong noise burst, the brightness stays the same but the = signals disappear.=20 Speclab also has a similar visual AGC option. The advantage is that you = wouldn't have to adjust gain between day and night, but I rarely use it = because I like to see whether the signal went down or the noise went up. = As you can guess, DCF (and also HGA) sidebands are really big here. For = the LF grabber I am using neither analog or digital AGC nor clipper, = just the SpecLab noise blanker alone. It gets the full SSB bandwidth and = is set to fast rampdown / rampup times (2 ms), so that it can recover = between individual clicks within an FSK bursts, minimizing signal loss. = The NB threshold is normally set to 9 dB above average. Best wishes, Markus (DF6NM) From: Mike Dennison=20 Sent: Saturday, April 07, 2012 11:38 AM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: Argo vs SpecLab I have recently being playing with the settings in SpecLab, and have=20 managed to reduce the effect of some local QRM. However, I am still=20 plagued by DCF39 data bursts. When using Argo (1.3.7) these are=20 almost invisible, but SpecLab still displays them. I have the SpecLab Limiter set very hard, and the Noise Blanker on,=20 and this helps, but it is still nowhere near as good as Argo in=20 taking out the data bursts. Any ideas? Mike, G3XDV =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ------=_NextPart_000_001A_01CD14B9.77039080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Mike,
 
you have probably selected = Argo's visual=20 AGC button on the bottom left, which is on by default. This does not = really=20 suppress interference, but scales each display column to the same = average=20 brightness of the noise. So during a = strong noise=20 burst, the brightness stays the same but the signals disappear.=20
 
Speclab also has a similar visual AGC = option.=20 The advantage is that you = wouldn't have=20 to adjust gain between day and night, but I rarely use it because I like = to see whether the signal went down or the noise went=20 up. 
 
As you can guess, DCF (and also HGA) = sidebands are=20 really big here. For the LF grabber I am using neither analog or digital = AGC nor=20 clipper, just the SpecLab noise blanker alone. It gets the full SSB = bandwidth and is set to fast rampdown / rampup times (2 ms), so = that it can=20 recover between individual clicks within an FSK bursts, minimizing = signal=20 loss. The NB threshold is normally set to 9 dB above = average.
 
Best wishes,
Markus (DF6NM)
 
 
From: Mike Dennison
Sent: Saturday, April 07, 2012 11:38 AM
To: rsgb_lf_group@blacksheep.org= =20
Subject: LF: Argo vs SpecLab

I have recently being = playing with=20 the settings in SpecLab, and have
managed to reduce the effect of = some local=20 QRM. However, I am still
plagued by DCF39 data bursts. When using = Argo=20 (1.3.7) these are
almost invisible, but SpecLab still displays=20 them.

I have the SpecLab Limiter set very hard, and the Noise = Blanker on,=20
and this helps, but it is still nowhere near as good as Argo in =
taking=20 out the data bursts.

Any ideas?

Mike,=20 G3XDV
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


------=_NextPart_000_001A_01CD14B9.77039080--