Return-Path: Received: from rly-dc03.mx.aol.com (rly-dc03.mail.aol.com [172.19.136.32]) by air-dc08.mail.aol.com (v121_r4.4) with ESMTP id MAILINDC081-b12497247ed343; Sat, 17 Jan 2009 16:05:08 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dc03.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINDC036-b12497247ed343; Sat, 17 Jan 2009 16:04:47 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LOIL5-0002Fp-Mj for rs_out_1@blacksheep.org; Sat, 17 Jan 2009 21:04:19 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LOIL5-0002Fg-0Y for rsgb_lf_group@blacksheep.org; Sat, 17 Jan 2009 21:04:19 +0000 Received: from imo-d04.mx.aol.com ([205.188.157.36]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LOIL3-0006rp-PF for rsgb_lf_group@blacksheep.org; Sat, 17 Jan 2009 21:04:18 +0000 Received: from MarkusVester@aol.com by imo-d04.mx.aol.com (mail_out_v39.1.) id l.d13.2095fddf (37079) for ; Sat, 17 Jan 2009 16:04:07 -0500 (EST) Received: from Black (g229197169.adsl.alicedsl.de [92.229.197.169]) by cia-db06.mx.aol.com (v121_r5.5) with ESMTP id MAILCIADB061-90d7497247c5178; Sat, 17 Jan 2009 16:04:06 -0500 Message-ID: From: "Markus Vester" To: References: <496E6B45.5020100@usa.net> <0F3DBBAC61C545AE85525CD884B642EC@Black> <20090114231729.6b8aea4f@lurcher> <2AD1A31DF27448F495C0CE7FF33CE9DE@Black> <1E6D0A88C4DE49E5A2AF05911187E7A3@Black> <424931F60B3D4F41AB7DCB9E9FCAB3C5@big7368b9a7d3d> <000e01c97703$df2dfcb0$8d01a8c0@JAYDELL> <5E6F6CB3C59741678D3AE19CEA22B373@JimPC> <45AE4BD5B9164F9A929A6A98D89CF1E6@cahal.danet> <008901c9772e$3b16a2f0$8cd9160a@EFREMOV> <49708674.5080009@telia.com> <006701c97814$91b188a0$8cd9160a@EFREMOV> <1F4FBFE39AD245A3B4A2DDAA4361BA7C@Black> <003701c97897$39a3f110$8cd9160a@EFREMOV> <5A4D281B4A044457B3A14F908BAB31DD@JimPC> In-Reply-To: <5A4D281B4A044457B3A14F908BAB31DD@JimPC> Date: Sat, 17 Jan 2009 22:04:03 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6000.16480 X-MIMEOLE: Produced By Microsoft MimeOLE V6.0.6000.16669 X-Spam-Flag:NO X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: Re: WSPR does not work Content-Type: text/plain; charset="iso-8859-1" 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-IP: 193.82.116.20 Hello Jim, LF, this is interesting! Yesterday I did basically the same experiment using an audio filter, and saw no difference at all in decoding ability between full SSB bandwidth and a 250 Hz filter. I concluded (perhaps prematurely) that there is no blocking effect present. Today I did another test by injecting an audio carrier from the Speclab generator within the WSPR search bandwidth. The "wanted signal" was F5WK signal at 1577 Hz with -57 dB below ADC fullscale, displaying -15 dB SNR at the time. I found that at a 1450 Hz carrier at -20 dBFS completely blocked decoding, even though the spectrogram traces of the WSPR signal and the carrier both looked perfect. Reducing the blocking carrier to -30 dBFS seemed to reduce Michel's SNR to -20 dB. In hindsight, and with the information from Jim, I assume that the out-of-band interference levels in my first experiment simply have been too small to cause an effect. DCF39, the strongest daytime carrier, is attenuated by the SSB IF filter edge to about -34 dBFS at originally 3330 Hz, which is then downconverted to 2830 Hz for the WSPR computer. So I now also believe that decoding might possibly be prevented by a 25 dB larger signal anywhere in the audio band. I guess I will need to play more with this tomorrow. Kind regards, Markus, DF6NM ----- Original Message ----- From: "James Moritz" To: Sent: Saturday, January 17, 2009 8:57 PM Subject: LF: Re: WSPR does not work Dear Andrey, LF Group, Here is an observation that might be relevant, (or perhaps not!) to the problem of WSPR displaying a clear spectrogram trace of a signal, but failing to decode it. I noticed it while looking for OH1LSQ's QRSS earlier, and have now checked a bit more carefully. First, I changed the BW from 250Hz to 2.4kHz so that I would be able to see OH1SQ at 800Hz audio frequency (carrier frequency set to 136.000k) using Spectrum Lab, and at the same time decode F5WK at around 1500Hz audio. This required reducing RF/IF gain to prevent overloading by the DCF39 carrier at 2.83kHz audio. I could then see OH1LSQ OK, but although there was a good trace from F5WK in WSPR, no decoding occured. (Changing the gain does not alter the spectrogram appearance much, so presumably it is displaying SNR rather than absolute signal level. ). Reducing the bandwidth to 250Hz, with the gain still reduced, restored normal decoding. Increasing the bandwidth to 2.4kHz again, adjusting the passband shift control, and changing the loop orientation to reduce DCF39 and Lakihegy to a minimum while maintaining F5WK's signal, with the gain still reduced, also gave normal decoding, although there was now assorted additional noise in the passband. It seems to me most likely that the failure to decode was due to the presence of the strong tone at high audio frequency from DCF39, although this tone was outside the WSPR frequency range, and not saturating the sound card A/D converter or overloading the analogue RX channel. So if there are other tones in your RX passband while receiving WSPR, it appears they may prevent decoding occuring, even though a good signal is displayed on the WSPR spectrogram. This seems to be a reproducible case where a strong WSPR signal does not decode on a receiving system that is known to work well. If others can reproduce this, it may be worth contacting K1JT to see if he is aware of this or can shed light on the matter. Cheers, Jim Moritz 73 de M0BMU