Return-Path: Received: from rly-da10.mx.aol.com (rly-da10.mail.aol.com [172.19.129.84]) by air-da04.mail.aol.com (v125.7) with ESMTP id MAILINDA044-a984ab7dffbc7; Mon, 21 Sep 2009 16:20:32 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-da10.mx.aol.com (v125.7) with ESMTP id MAILRELAYINDA108-a984ab7dffbc7; Mon, 21 Sep 2009 16:20:13 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1MppM3-0008Ok-ND for rs_out_1@blacksheep.org; Mon, 21 Sep 2009 21:19:23 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1MppM3-0008Ob-6K for rsgb_lf_group@blacksheep.org; Mon, 21 Sep 2009 21:19:23 +0100 Received: from n6a.bullet.mail.ac4.yahoo.com ([76.13.13.69]) by relay1.thorcom.net with smtp (Exim 4.63) (envelope-from ) id 1MppKs-0003Zs-0S for rsgb_lf_group@blacksheep.org; Mon, 21 Sep 2009 21:18:10 +0100 Received: from [76.13.13.25] by n6.bullet.mail.ac4.yahoo.com with NNFMP; 21 Sep 2009 20:19:07 -0000 Received: from [76.13.10.184] by t4.bullet.mail.ac4.yahoo.com with NNFMP; 21 Sep 2009 20:19:07 -0000 Received: from [127.0.0.1] by omp125.mail.ac4.yahoo.com with NNFMP; 21 Sep 2009 20:19:04 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 472689.60688.bm@omp125.mail.ac4.yahoo.com Received: (qmail 60972 invoked by uid 60001); 21 Sep 2009 20:03:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1253563413; bh=baUw/8BsvFsSvqd0QlUMprqe9YctPFT6DiFvizRUtak=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=HjhHilWhcTZgfRdDHSz1cg0rAVZoOalIaS8uENV3sj9TXUzYwpf1Z/qSwKOPHMOx3Z0FiU31fxjbwvtiqGY5OfXtnmKNh6r4fcG6q1B1Frg2DfiH2OlZYPldE1TFmvjczQOeroA6Hr043xiuMEKMmw42SUEajkAPwIqZue4eEIY= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=t/YmZDR7X1E7jADOdtG7Rh1yh40SaOEdM1CedCzgCwY6Qvb7iadLQ5kzCgXKKZ2xeg2Vs/7gKwPiinKaHRsdlmt8yYL3vS1VZc/hWZDPSrAkeIXb4nmfaEsLiKOcyeZffb14zEnfEfiPSEqfcfBrxvL7gi/Qv40s8Rkmnc8GJSg=; Message-ID: <772404.60948.qm@web63603.mail.re1.yahoo.com> X-YMail-OSG: Ua2xmF4VM1lyGGuvdVmdDEwxGxFZVLB0kE.yO9gPaN0Nb33_SAf8r2xgWq1eYpb8312r2zHw83E2dXbTzvAhvSPyN335sVWO8cEqOkVwEZY9JtSIk682lPnW_b.OfnwgrwVhqeooKhVqZ3bOVMjCs8AcfjstnmgQKNiL1zClo9EVqXUIoQTYDN8D9zEo7r979C4t8l0Gj4XVVb4Hg8FRQMaVpq7Ek4bP4vvrgOo8ECMdm.Op8dLVO1vnvFY4XrWGtNBvzY445CiyqaZvq.4jMKZGm6KydUElprVnhxxRdpRILOtf Received: from [98.70.127.22] by web63603.mail.re1.yahoo.com via HTTP; Mon, 21 Sep 2009 13:03:33 PDT X-Mailer: YahooMailClassic/7.0.14 YahooMailWebService/0.7.347.2 Date: Mon, 21 Sep 2009 13:03:33 -0700 (PDT) From: Andy - KU4XR To: 600 meter group , EU - LF group , lowfer@mailman.qth.net MIME-Version: 1.0 X-Karma: unknown: DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: My recent observations with WSPR Content-Type: text/plain; charset=us-ascii X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=FORGED_YAHOO_RCVD 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 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-d287.1 ; domain : yahoo.com DKIM : fail Hello all: I monitored the transmission of John, WD2XES in WSPR mode on 9/20 to 9/21 -2009 ending at 05:00 UTC. I copied him for about 2-1/2 hours during which time I experimented with different settings on my receiver, as well as my DSP audio filters to see what interaction it would have on WSPR decodes. John was transmitting on 137.577 KHz, and this was my first attempt using WSPR on 2200 meters. Receive conditions were deplorable. The lightening crashes with a 500 cycle filter were peaking at 40dB over S-9. I didn't have enough time to make many observations; however here are some things that I did find out about WSPR. WSPR references its decodes against the noise level in a given audio passband. The more noise, lower S/N ratios of course. On my setup; WSPR could not decode when static crashes were above peaks of 10dB over S-9. I found this out by using my noise blanker. Without the NB on, static peaks were 40 over, and WSPR would not decode. My NB reduced the peaks to S-9 to 10 over, and WSPR would then decode. It made no difference what audio BW I was using, without the NB, the Static simply masked the signal. The noise level using the 2.4 KHz SSB filter was out of the question. So, the narrower you can get your IF - BW,the better WSPR will do at decoding. My comment about the dB reading. With no audio filtering, the XES signal decoded around -26 to -29 dB. With audio BW as low as 20 Hz; it would show +8 to +10 dB. This is not an exaggerated reading. When you narrow your audio BW, you lower the passband noise level. And the DSP filter also " Boosts " the desired signal level in amplitude. So, lower passband noise, coupled together with a higher signal level amplitude will naturally increase WSPR's dB reading. And just to make this remark, adjustment of the volume control does not have any effect on WSPR at all. That is unless you turn it all the way down. About narrow audio filtering and WSPR, I'll say this; try it and see what happens. I did find this out; audio filtering less than 20 Hz produced too much " filter ringing " and WSPR hears this as an un-intelligible signal, and the ringing will mask out the desired signal, and No Decode. My little one night, 2-1/2 hour experiment showed this: In the extreme receive conditions on 2200 meters, WSPR decoded OK at an IF - BW of 500 Hz. Decodes were better, and easier for WSPR when I used an audio BW of 220 Hz. And decodes came thru fine with the 20 Hz audio BW, centered on the desired signal. IF filtering, and IF shift will provide the best results from interfering signals within the passband. Notch filter would be beneficial if the interfering signal is far enough away that the notch dosen't affect the signal you are trying to receive. The audio filtering is most effective at reducing the noise that WSPR has to deal with, and WSPR dosen't like extreme static. I am fairly new to WSPR, and this is probably some elementary information, But I do hope that to any newcomers to WSPR, it might be of some value. Thanks for your time in reading this, and ; 73 to all ::: Andy - KU4XR - EM75xr - Friendsville, TN. LOWfer Beacon " XR " @ 184.322 KHz ( QRSS-60 ) Coordinates: N: 35* 43' 54" - W: 84* 3' 16" http://www.myspace.com/beaconxr