Return-Path: Received: from rly-me06.mx.aol.com (rly-me06.mail.aol.com [172.20.83.40]) by air-me06.mail.aol.com (v121_r4.4) with ESMTP id MAILINME064-9c249706efd1ed; Fri, 16 Jan 2009 06:26:59 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-me06.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINME066-9c249706efd1ed; Fri, 16 Jan 2009 06:26:56 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LNmpZ-0003U2-3A for rs_out_1@blacksheep.org; Fri, 16 Jan 2009 11:25:41 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LNmby-0003NT-Iv for rsgb_lf_group@blacksheep.org; Fri, 16 Jan 2009 11:11:38 +0000 Received: from qmta04.westchester.pa.mail.comcast.net ([76.96.62.40]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LNYm1-0007OT-RU for rsgb_lf_group@blacksheep.org; Thu, 15 Jan 2009 20:25:13 +0000 Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA04.westchester.pa.mail.comcast.net with comcast id 3siu1b00G0EZKEL54wQqqZ; Thu, 15 Jan 2009 20:24:50 +0000 Received: from DELL4 ([65.96.107.144]) by OMTA01.westchester.pa.mail.comcast.net with comcast id 3wQp1b00A36xPMd3MwQpLn; Thu, 15 Jan 2009 20:24:50 +0000 Message-ID: <001b01c9774f$5047bc10$6c01a8c0@DELL4> From: To: References: <496E6B45.5020100@usa.net> <0F3DBBAC61C545AE85525CD884B642EC@Black> <20090114231729.6b8aea4f@lurcher> <2AD1A31DF27448F495C0CE7FF33CE9DE@Black> <1E6D0A88C4DE49E5A2AF05911187E7A3@Black> <424931F60B3D4F41AB7DCB9E9FCAB3C5@big7368b9a7d3d> <000e01c97703$df2dfcb0$8d01a8c0@JAYDELL> <5E6F6CB3C59741678D3AE19CEA22B373@JimPC> Date: Thu, 15 Jan 2009 15:24:48 -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-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" To: 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 >