Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.138 with SMTP id ds10csp45655igb; Sat, 14 Dec 2013 12:18:39 -0800 (PST) X-Received: by 10.194.21.225 with SMTP id y1mr975179wje.60.1387052318586; Sat, 14 Dec 2013 12:18:38 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id t9si1385037wif.6.2013.12.14.12.18.37 for ; Sat, 14 Dec 2013 12:18:38 -0800 (PST) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1VrvAW-00055Q-Hn for rs_out_1@blacksheep.org; Sat, 14 Dec 2013 19:46:32 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VrvAV-00055E-Ci for rsgb_lf_group@blacksheep.org; Sat, 14 Dec 2013 19:46:31 +0000 Received: from smtp21.cix.co.uk ([77.92.64.201] helo=smtp1.cix.co.uk) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1VrvAS-00023o-UW for rsgb_lf_group@blacksheep.org; Sat, 14 Dec 2013 19:46:30 +0000 Received: (qmail 7144 invoked from network); 14 Dec 2013 19:46:28 -0000 Received: from unknown (HELO cix.co.uk) (79.71.126.74) by smtp1.cix.co.uk with SMTP; 14 Dec 2013 19:46:28 -0000 Mime-Version: 1.0 Date: Sat, 14 Dec 2013 19:46 +0000 (GMT Standard Time) From: tsmithers@cix.co.uk (Trevor Smithers) To: markusvester@aol.com, rsgb_lf_group@blacksheep.org CC: tsmithers@cix.co.uk In-Reply-To: Message-Id: X-Ameol-Version: 2.53.2014, Windows 2000 build 2600 (Service Pack 3) X-HELO-Warning: Remote host 77.92.64.201 (smtp21.cix.co.uk) used invalid HELO/EHLO smtp1.cix.co.uk - verification failed X-Spam-Score: -0.4 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi Marcus, Hartmut, Victor It doesn't have to be from last night - I'm sure Joe would be happy to see any recordings that you think would benefit from further analysis. With not many stations using wspr-15 on a regular basis any feedback he gets is going to be limited, so anything that demonstrates the qrm conditions in EU is going to be useful. [...] Content analysis details: (-0.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: f1498eebf16822c5ea85527a90413169 Content-Type: text/plain; charset="us-ascii" Subject: Re: LF: All 73 Banders... wspr-x recordings X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none 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 Status: O X-Status: X-Keywords: X-UID: 2169 Hi Marcus, Hartmut, Victor It doesn't have to be from last night - I'm sure Joe would be happy to see any recordings that you think would benefit from further analysis. With not many stations using wspr-15 on a regular basis any feedback he gets is going to be limited, so anything that demonstrates the qrm conditions in EU is going to be useful. 73 Trevor G0KTN -------- Original Message -------- Trevor, thanks for this comment! It would be interesting to know how much = spacing is needed between a weak WSPR signal and a relatively strong = neighbouring carrier, located within the WSPR analysis range but outside = the four-tone spectrum of the desired signal. Unfortunately I can't contribute as I hadn't run recordings, and also = both the desired WSPR signal and the Loran carrier were anyway too weak = here for a meaningful result. Perhaps Hartmut or Victor happened to have = .c2 or .wav saving enabled last night?=20 Best 73, Markus From: Trevor Smithers=20 Sent: Saturday, December 14, 2013 6:43 PM To: markusvester@aol.com ; rsgb_lf_group@blacksheep.org ; = lowfer@mailman.qth.net=20 Cc: tsmithers@cix.co.uk=20 Subject: Re: LF: All 73 Banders... As you know WSPR-X is regarded as experimental software and as such Joe = Taylor K1JT has=20 often asked for users to contact him with any difficulties they = encounter. So how about Marcus, Hartmut, Victor and anyone else, producing a .wav = file of successful and=20 non successful wspr-15 decodes including all the DCF77 and other qrm. = The files could be sent=20 to Joe direct or made available for him to download and he can analyse = them to see if any=20 improvements can be made. K1JT email address can be found at the bottom of this page http://physics.princeton.edu/pulsar/K1JT/wspr.html Trevor G0KTN From: Markus Vester=20 Sent: Saturday, December 14, 2013 4:03 PM To: rsgb_lf_group@blacksheep.org ; Bob Raide=20 Subject: Re: LF: All 73 Banders... ... It's however strange that Hartmut and Victor didn't get any decodes, = even though the signal seemed to be well visible for both. What looks = like noise on Victor's capture must really be the WSPR-15 spectrum:=20 = http://dl.dropboxusercontent.com/u/26404526/pa3fny_74603_131214_0700_arro= wheads.jpg But both statiopns have a relatively strong Loran line, and Hartmut's = directional antenna is pointing towards Sylt. However the nearby line = frequency 74603.280 Hz should have been well outside the occupied = spectrum of Bob's WSPR signal (74603.51 to 604.24), so it's not ovbvious = why it should have prevented decodes. I'm speculating that the WSPR = software finds the strong line, tries to sync to it, and then somehow = excludes nearby real signals from further decode attempts. To prove the = point and see how much spacing is needed, we could experiment with = letting WSPR decode local audio signals in the presence of injected = carriers. But systematic trials with WSPR tend to be time-consuming, = even if such tests were accelerated by scaling to WSPR-2. ...