Return-Path: <owner-rsgb_lf_group@blacksheep.org>
Received: from rly-da08.mx.aol.com (rly-da08.mail.aol.com [172.19.129.82]) by air-da10.mail.aol.com (v121_r4.4) with ESMTP id MAILINDA103-a8749708095ff; Fri, 16 Jan 2009 07:42:21 -0500
Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-da08.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINDA087-a8749708095ff; Fri, 16 Jan 2009 07:42:01 -0500
Received: from majordom by post.thorcom.com with local (Exim 4.14)
	id 1LNo18-0005zr-Md
	for rs_out_1@blacksheep.org; Fri, 16 Jan 2009 12:41:42 +0000
Received: from [193.82.116.32] (helo=relay1.thorcom.net)
	by post.thorcom.com with esmtp (Exim 4.14)
	id 1LNnes-0005Jw-TF
	for rsgb_lf_group@blacksheep.org; Fri, 16 Jan 2009 12:18:42 +0000
Received: from qmta10.westchester.pa.mail.comcast.net ([76.96.62.17])
	by relay1.thorcom.net with esmtp (Exim 4.63)
	(envelope-from <jrusgrove@comcast.net>)
	id 1LNZzW-0002vE-CR
	for rsgb_lf_group@blacksheep.org; Thu, 15 Jan 2009 21:43:08 +0000
Received: from OMTA11.westchester.pa.mail.comcast.net ([76.96.62.36])
	by QMTA10.westchester.pa.mail.comcast.net with comcast
	id 3s6A1b00J0mv7h05AxizmK; Thu, 15 Jan 2009 21:42:59 +0000
Received: from DELL4 ([65.96.107.144])
	by OMTA11.westchester.pa.mail.comcast.net with comcast
	id 3xiy1b00e36xPMd3XxizH9; Thu, 15 Jan 2009 21:42:59 +0000
Message-ID: <001501c9775a$3b925ea0$6c01a8c0@DELL4>
From: <jrusgrove@comcast.net>
To: <rsgb_lf_group@blacksheep.org>
References: <F4E8A04C3CBA4C67AE9C3318F2F40C4F@JimPC> <496E6B45.5020100@usa.net> <0F3DBBAC61C545AE85525CD884B642EC@Black> <20090114231729.6b8aea4f@lurcher> <2AD1A31DF27448F495C0CE7FF33CE9DE@Black> <C4F6E432D5814955A1FDD42B0279F472@AGB> <1E6D0A88C4DE49E5A2AF05911187E7A3@Black> <424931F60B3D4F41AB7DCB9E9FCAB3C5@big7368b9a7d3d> <E68E6C5A539A4838ADAC20BE903CBC68@JimPC> <000e01c97703$df2dfcb0$8d01a8c0@JAYDELL> <5E6F6CB3C59741678D3AE19CEA22B373@JimPC>
Date: Thu, 15 Jan 2009 16:42:57 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Karma: unknown: 
X-Spam-Score: 0.6 (/)
X-Spam-Report: autolearn=disabled,NO_REAL_NAME=0.55
Subject: LF: Re: Re: 136khz WSPR
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com
X-Spam-Level: 
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_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-IP: 193.82.116.20


Jim

Had a look at noon using an Argo QRSS10 screen and could not find a single
open area wider than 5.02 Hz anywhere in the band. All 5.02 Hz spaced lines
are plenty bright so they're likely a problem for WSPR. Guess the program
wasn't designed to co-exist with loran...

Jay

----- Original Message ----- 
From: "James Moritz" <james.moritz@btopenworld.com>
To: <rsgb_lf_group@blacksheep.org>
Sent: Thursday, January 15, 2009 9:39 AM
Subject: LF: Re: 136khz WSPR


> Dear Jay, Vernon, LF Group,
>
> Jay - Thanks for looking -  I can see that could be the problem!
>
> The WSPR signal has a bandwidth of around 6Hz, so the problem is finding 
> that much of a gap between lines. E.g. with the Northeastern USA chain 
> with 9960 GRI, lines should appear every 5.02Hz roughly, although I expect 
> some will probably be stronger than others. Can you look with Argo on a 
> wider setting to see if there are any 6Hz wide spaces, or at least areas 
> where the lines are weaker?
>
> Vernon - I'm afraid "SCP/LN8PHG" probably isn't a genuine signal, but WSPR 
> producing a false decode - this is fairly common when narrow-band QRM is 
> present, although only occurs rarely when just the band noise is present. 
> Because of the way WSPR encodes/decodes, it will usually try to format any 
> "gobbledygook" as a legitimate message with callsigns, reports, etc. You 
> can usually tell by the outlandish callsigns and locators. A pity really, 
> otherwise they would be pretty impressive DX!
>
> Cheers, Jim Moritz
> 73 de M0BMU
>