Return-Path: Received: from rly-mg07.mx.aol.com (rly-mg07.mail.aol.com [172.20.83.113]) by air-mg09.mail.aol.com (v125.7) with ESMTP id MAILINMG091-a264abcc073250; Fri, 25 Sep 2009 09:07:17 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mg07.mx.aol.com (v125.7) with ESMTP id MAILRELAYINMG078-a264abcc073250; Fri, 25 Sep 2009 09:07:01 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1MrAUo-0001xr-3C for rs_out_1@blacksheep.org; Fri, 25 Sep 2009 14:05:58 +0100 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1MrAUn-0001xi-IL for rsgb_lf_group@blacksheep.org; Fri, 25 Sep 2009 14:05:57 +0100 Received: from smtprelay0177.hostedemail.com ([216.40.44.177] helo=smtprelay.hostedemail.com) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1MrAUc-00068E-R2 for rsgb_lf_group@blacksheep.org; Fri, 25 Sep 2009 14:05:49 +0100 Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay03.hostedemail.com (Postfix) with SMTP id E793315ADED4; Fri, 25 Sep 2009 13:05:40 +0000 (UTC) X-Session-Marker: 70657465722E636C65616C6C4076697267696E2E6E6574 X-Filterd-Recvd-Size: 3647 Received: from webmail10 (imap-ext [216.40.42.5]) (Authenticated sender: peter.cleall@virgin.net) by omf07.hostedemail.com (Postfix) with ESMTP; Fri, 25 Sep 2009 13:05:40 +0000 (UTC) Received: from 86.177.204.162 ([86.177.204.162]) by webmail10 (Tucows Webmail) with HTTP; Fri, 25 Sep 2009 13:05:40 +0000 (GMT) Date: Fri, 25 Sep 2009 13:05:40 +0000 (GMT) From: Peter Cleall To: rsgb_lf_group@blacksheep.org Cc: rsgb_lf_group@blacksheep.org Message-ID: <1491341984.116537.1253883940734.JavaMail.mail@webmail10> MIME-Version: 1.0 X-Originating-IP: [86.177.204.162] X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: Re: Re: s/n shown by wspr .... what is it actually showing ? Content-Type: text/plain; charset=UTF-8 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.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 X-AOL-IP: 193.82.116.20 X-Mailer: Unknown (No Version) Thanks Jim for this observation and others for their feedback. When I first set up WSPR, in the days when the s/n button did not exist I ran a series of tests where I changed the level into the sound card and looked at the S/n of a single station as reported by WSPR. I found some non linearity and settled for an area on the linear part of the curve. When the s/n button appeared. I found it was red and reading -27dB. I have been running it at this level for several months. I have been getting decoded reports of s/n between -27 and -9 but usually about 6 -9dB worse than others were reporting. Last week as you know I tried your sigs on 137kHz and picked up 3 signals each time. slot After the dialogue of the last few days I have turned my audio down and am setting to 0 dB on the button. Plenty of decodes last night. Now I need to find time to redo my linearity measurements and also compare my results with others reports on the database. regards peter G8AFN Dear Dave, LF Group, There seem to be some misunderstandings here... The little box with the receiver noise level is there so you can set the gain controls to a reasonable level where the incoming audio is well above the noise level of the sound card, but well below overload level. 0dB is what K1JT has settled on as an optimum level, but quite wide deviations from that (say +/- 10dB or more) will not have much effect on the decoding process, or the reported SNR of the signal. In fact, even if the overload level is reached on noise peaks, it still makes little difference provided it only occurs a reasonably small proportion of the time. The reported SNR is obtained by measuring the level of each WSPR signal during the 2 minute period, measuring the associated noise level during the same period, and calculating the dB ratio. Thus it is largely independent of the actual receiver or sound card gain settings, and gain can be varied through many dB (see above) without significantly changing the SNR reports. So there is no direct connection between the receiver output level and the SNR figures. Cheers, Jim Moritz 73 de M0BMU ----- Original Message ----- From: "Dave Sergeant" To: Sent: Thursday, September 24, 2009 9:39 AM Subject: LF: Re: s/n shown by wspr .... what is it actually showing ? > In the ideal case of course you have just receiver noise as your > background noise level. So you adjust your sound card input to give you > the magic 0dB on that. During the night the static crash level will > rise and push the S-meter to s9 at times. Every 15 minutes G4JNT will > do its one minute of transmission on 503.7 at various power levels and > push the little thing in the box well into the red. So one has to ask > oneself what exactly the dB figures in reports really mean....