Return-Path: Received: from mtain-di02.r1000.mx.aol.com (mtain-di02.r1000.mx.aol.com [172.29.64.6]) by air-dd08.mail.aol.com (v127_r1.1) with ESMTP id MAILINDD084-86b04babcde4217; Thu, 25 Mar 2010 16:56:04 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-di02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 94EBB380000ED; Thu, 25 Mar 2010 16:56:01 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Nuu4T-0002ir-Cw for rs_out_1@blacksheep.org; Thu, 25 Mar 2010 20:54:29 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Nuu4S-0002ii-Qy for rsgb_lf_group@blacksheep.org; Thu, 25 Mar 2010 20:54:28 +0000 Received: from smtp815.mail.ukl.yahoo.com ([217.12.12.244]) by relay1.thorcom.net with smtp (Exim 4.63) (envelope-from ) id 1Nuu4Q-0001Ii-2B for rsgb_lf_group@blacksheep.org; Thu, 25 Mar 2010 20:54:28 +0000 Received: (qmail 69099 invoked from network); 25 Mar 2010 20:54:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btopenworld.com; h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:In-Reply-To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE; b=ZCd4EF5BOagxi0Dsk2kLRkVGxquIkfdqcsC9NKAIMufEZfzZifZvGj94JceeJ/L+PMikdfp9aF25WyMtvmYjmdRW0daGp9/7w6u6QzHAuCD+UdI3/y3gOJXpGV85rgqBImSGukZbIlPpyf1Yimswy79l9HyjYNdVX/ft1NPIYvE= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btopenworld.com; s=s1024; t=1269550459; bh=TX17ZtB/pDsmTZaIW7hXRTp/Fu3Kx7nOj3tmrXDzTHc=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:In-Reply-To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE; b=tHC26rP8VP14RK+3ySqOjGc9Kfme5m/mPaZgIQLi+q1/r1w9M0byP8vCQXBXNvMdq+ILqHfDC5bOcX9X2ePf/pclaFv1AcxPMTCz3gkhT5ckqY8l+NEsqXAD7QTuzn/tV/PF3ncCezQbbF5hzzP+CNj1lgc0SAgvzX2ed9I59kc= Received: from JimPC (james.moritz@86.180.204.156 with login) by smtp815.mail.ukl.yahoo.com with SMTP; 25 Mar 2010 20:54:19 +0000 GMT X-Yahoo-SMTP: Cxhli3eswBD1ozmtAojhjrja86kWx0Qm9tycD5QR1DKWrOLgjJcXkw-- X-YMail-OSG: 07ohUwoVM1kTQTak.5L12mJzimWs7ngLJklRT4AqbPtMgocFm7wWcZEpNAQJ8OmJcbKwYfvuffyWnAfTxkAGO1_R4aMHsK..FaMuQ8VH1S5aqNWTtyxsoDz0vWbTj5izv2.4fijEhDgMulatwORin_bRWlM0otrzdqUqOt26hEstjRFL0fGZ8KcsHS4SQ2ZKlV9xxBf0.b4j0Cszsg1.SOTVSFD1Mqschb4A4dC4TpuAEsNNw7_IYPjGbniIISn7 X-Yahoo-Newman-Property: ymail-3 Message-ID: From: "James Moritz" To: References: In-Reply-To: Date: Thu, 25 Mar 2010 20:54:19 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18005 X-MIMEOLE: Produced By Microsoft MimeOLE V6.0.6002.18005 DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,UNPARSEABLE_RELAY=0.001 Subject: LF: Re: Interesting False WSPR Decode Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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.1 required=5.0 tests=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-AUTHENTICATION: mail_rly_antispam_dkim-m214.2 ; domain : btopenworld.com DKIM : fail x-aol-sid: 3039ac1d40064babcde17bb4 X-AOL-IP: 193.82.116.20 Dear Andy, Eddie, LF Group, Actually these "double false decodes" are not particularly rare, although not usually correctly formatted as a beacon signal, so they don't make it into the database. For instance, O4V1FS appeared twice at 1640utc. I think they must be an artefact of the demodulation/decoding algorithms used by WSPR - don't ask me how! There have actually been some fairly impressive bursts of noise this evening. I have a feeling that this kind of behaviour is linked to times when WSPR takes a very long time to complete decoding. In fact, sometimes the blue "decoding" button in the WSPR window remains active for a whole 2 minute TX period, and overruns into the next period - this may be when these decodes appear. This behaviour seems to be associated with bursts of noise. Or at least, so it seems, but it happens quite rarely, and so life is probably too short for me to check! So it might be some sort of bug. The false decode of an "extra" G3ZJO on 503.989kHz is curious too, presumably it must be related. The DT time offset figure in the WSPR readout is -1.4s for the real signal, and +2.9s for the imposter - the two "7D0LX"s were also offset in time with DT of +5.7 and +6.4 seconds. A long delay echo seems to be stretching credibility a bit! Of course, there also have been genuine double decodes, where a station has had hum sidebands and so on. Cheers, Jim Moritz 73 de M0BMU > Jim - > How did you manage this? Never seen one like it before. > > A false WSPR decode, but the identical message appearing twice, 124 Hz > apart. > Must have been an interesting burst of pulsed WB interference to generate > in. >