Return-Path: Received: from mtain-dg03.r1000.mx.aol.com (mtain-dg03.r1000.mx.aol.com [172.29.65.11]) by air-de05.mail.aol.com (v126.13) with ESMTP id MAILINDE053-5eb44b5a1db9289; Fri, 22 Jan 2010 16:50:49 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-dg03.r1000.mx.aol.com (Internet Inbound) with ESMTP id 7A89538000062; Fri, 22 Jan 2010 16:50:47 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NYROB-0003pw-BT for rs_out_1@blacksheep.org; Fri, 22 Jan 2010 21:49:59 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NYROA-0003pl-Sz for rsgb_lf_group@blacksheep.org; Fri, 22 Jan 2010 21:49:58 +0000 Received: from fg-out-1718.google.com ([72.14.220.156]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NYRO7-0007tH-PC for rsgb_lf_group@blacksheep.org; Fri, 22 Jan 2010 21:49:58 +0000 Received: by fg-out-1718.google.com with SMTP id 22so634579fge.10 for ; Fri, 22 Jan 2010 13:49:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=75t5cHAmrgjZ5A8r8ZTcBQkbk71KV/G2+KDgjLwQcng=; b=KJHMJ3DIcss2GUkGw9GDyia7c85eZH71GXMjuMFzG7zjlhYPS/Tvo/RMtuLgS1BNzG +htzCl9ED1+ON5a3fEnUHjr0Qbd/43hK4rnlRbJmMnBzequzdqmrFxVBMypZxtpdirCF 1L2mjKZQhRuN5WnVhG84dCGnluUtxCfdMWhcw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ROHOLJz/6urNiv3+C2K9pYeF9MChwm3UQumz+QHjQ9B08eBiDGd28XOttYNLKN+M60 DQwRcnSEQRDkwEToPg/0bI2XXtS3SN2s3RjcEPxWkQixA1OAPZC4m25eyS0gXwjpx3tL fBxXNIw5mYCgc1vDIqEjTO7NNew7zJWW4ooeM= MIME-Version: 1.0 Received: by 10.239.188.146 with SMTP id p18mr381967hbh.208.1264196994602; Fri, 22 Jan 2010 13:49:54 -0800 (PST) In-Reply-To: <20100122224217.gm8o4dichs0o4wcs@webmail6.kuleuven.be> References: <1f0624b91001221140ib63e25fqf514c9fc604be78c@mail.gmail.com> <20100122220657.0kvbv3do0s48kwo4@webmail6.kuleuven.be> <20100122221736.upoqvds57owwk48s@webmail6.kuleuven.be> <20100122224217.gm8o4dichs0o4wcs@webmail6.kuleuven.be> Date: Fri, 22 Jan 2010 21:49:54 +0000 Message-ID: From: Andy Talbot To: rsgb_lf_group@blacksheep.org X-Karma: unknown: DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: 500 kHz JT4A Content-Type: multipart/alternative; boundary=001485f795f4ca1a6a047dc7cc9f X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE 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-sid: 3039ac1d410b4b5a1db70546 X-AOL-IP: 193.82.116.20 X-Mailer: Unknown (No Version) --001485f795f4ca1a6a047dc7cc9f Content-Type: text/plain; charset=ISO-8859-1 That sync figure not 'poor'. The mode will decode with values as low as 3 or 4. Just not as good as it could be in pure noise at that S/N. Pulse type QRM interferes with the decoding process more than poor S/N does. Andy www.g4jnt.com 2010/1/22 Rik Strobbe > Andy, > > thanks. > I just decoded Gary : "CQ G4WGT IO83", sync = 11 , dB = -2. > Not sure wether QRM is an issue, I see 2 bright traces against a black > background. > What else could cause the poor sync ? > > 73, Rik ON7YD - OR7T > > > Quoting Andy Talbot : > > See annotations below >> >> Andy >> www.g4jnt.com >> >> >> 2010/1/22 Rik Strobbe > Rik.Strobbe@fys.kuleuven.be>> >> >> As said I haven't read any instructions / manual but maybe the figures >> WSJT7 spits out on the readable copies of Jim may give a clue: >> Sync = 9 Not brilliant for -2dB S/N but blame the bad QRM >> dB = -2 Very good signal (This is the S/N normalised to >> 2.5kHz) >> DT = 0.0 Timing spot-on, no error between clocks at both ends >> DF = -107 -107Hz tuning error >> W = 33 Not sure - >> >> 73, Rik ON7YD - OR7T >> > --001485f795f4ca1a6a047dc7cc9f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
That sync figure =A0not 'poor'.=A0 The mode will decode with= values as low as 3 or 4.
=A0Just not as good as it could be in pure noise at that S/N.
=A0
Pulse type QRM interferes with the decoding process more than poor S/= N does.
2010/1/22 Rik Strobbe <Rik.Strobbe@fys.kuleuven.be>
Andy,

thanks.
I just= decoded Gary : "CQ G4WGT IO83", sync =3D 11 , dB =3D -2.
Not= sure wether QRM is an issue, I see 2 bright traces against a black backgr= ound.
What else could cause the poor sync ?

73, Rik =A0ON7YD - OR7T=20


Quoting Andy Talbot <andy.g4jnt@googlemail.com>:<= br>
See annotations below

A= ndy
www.g4jnt.com<http://www.g4jnt= .com>


2010/1/22 Rik Strobbe =A0<Rik.Strobbe@fys.kuleuven.be<mailto:Rik.Strobbe= @fys.kuleuven.be>>=20

As said I haven't read any instructions / manual= but maybe the =A0figures WSJT7 spits out on the readable copies of Jim ma= y give a clue:
Sync =3D 9 =A0 =A0 =A0 =A0 =A0 =A0Not brilliant for -2dB= S/N =A0 but blame the bad QRM
dB =3D -2 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Very good signal (This is the S/N no= rmalised to 2.5kHz)
DT =3D 0.0 =A0 =A0 =A0 =A0 =A0 =A0 Timing spot-on,= no error between clocks at both ends
DF =3D -107 =A0 =A0 =A0 =A0 =A0= -107Hz tuning error
W =3D 33 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Not sure= -

73, Rik =A0ON7YD - OR7T
--001485f795f4ca1a6a047dc7cc9f--