Return-Path: Received: from rly-de06.mx.aol.com (rly-de06.mail.aol.com [172.19.170.142]) by air-de06.mail.aol.com (v125.7) with ESMTP id MAILINDE064-4df4af74ccc38e; Sun, 08 Nov 2009 17:57:24 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-de06.mx.aol.com (v125.7) with ESMTP id MAILRELAYINDE062-4df4af74ccc38e; Sun, 08 Nov 2009 17:57:18 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1N7GgG-0001We-Bn for rs_out_1@blacksheep.org; Sun, 08 Nov 2009 22:56:20 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1N7GgF-0001WV-M5 for rsgb_lf_group@blacksheep.org; Sun, 08 Nov 2009 22:56:19 +0000 Received: from out1.ip08ir2.opaltelecom.net ([62.24.128.244]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1N7GgD-00072c-2Q for rsgb_lf_group@blacksheep.org; Sun, 08 Nov 2009 22:56:19 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqkEABPb9kpcHccI/2dsb2JhbACEOtUZhD4EgWg X-IronPort-AV: E=Sophos;i="4.44,704,1249254000"; d="scan'208";a="212607643" Received: from unknown (HELO mal769a60aa920) ([92.29.199.8]) by out1.ip08ir2.opaltelecom.net with SMTP; 08 Nov 2009 22:56:07 +0000 Message-ID: <02c801ca60c6$aa5e0540$0301a8c0@mal769a60aa920> From: "mal hamilton" To: References: <027601ca60a2$841cd150$0301a8c0@mal769a60aa920> <020b01ca60a9$4495adc0$0201a8c0@Clemens04> <029701ca60af$4f444d20$0301a8c0@mal769a60aa920> <4AF73120.6070007@telus.net> Date: Sun, 8 Nov 2009 22:56:10 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.3 (/) X-Spam-Report: autolearn=disabled,MAILTO_TO_SPAM_ADDR=0.276 Subject: Re: LF: Re: Re: WSPR 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=1.1 required=5.0 tests=MAILTO_TO_SPAM_ADDR 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 Sri Scott I do not use beacon mode only QSO mode. If you want to try xband let me know your QRG on HF. I have worked VE7 on every band from 1.8 - 28 Mcs. Only CW or QRS3 tx this end. 73 de mal/g3kev ----- Original Message ----- From: "Scott Tilley" To: Sent: Sunday, November 08, 2009 8:59 PM Subject: Re: LF: Re: Re: WSPR > Hey Mal > > Would you consider firing up a QRSS beacon for a couple of hours before > and during your sunrise in the NA waterhole 137778.0Hz +/- 3Hz? > > DCF39 has been audible for the last couple of nights and it may be our > time to get a signal from EU into the west coast of NA. I'd like to see > how the path works while open and see whether there is a possibility of > QSO in the future. > > Here's your chance at another first... > > TU es 73 > Scott > > > mal hamilton wrote: >> Two points >> >> Why waste 2.4 kHz when QRS only needs a few Hz with a better S/N ratio. >> >> You agree that a faint trace is visible. If this faint trace was QRS >> mode only a few Hz bandwidth would be necessary to read the >> intellegence and the signal/noise would be superior. >> G3KEV >> >> ----- Original Message ----- From: "Clemens Paul" >> To: >> Sent: Sunday, November 08, 2009 7:23 PM >> Subject: LF: Re: WSPR >> >> >>> Mal, >>> >>>> WSPR reports amongst stns indicate reception reports usually minus >>>> dB. Most of these >>>> stations are usually PLUS >>>> dB with me or very close to that figure. >>> >>> WSPR refers the indicated SNR to a BW of 2,4kHz. >>> So if your receiving BW is say 100Hz your actual SNR is better by >>> ~14dB than WSPR >>> reports. >>> >>>> A trace of the signal is visible long before a decode takes place, >>>> therefore why >>>> not use QRS in >>> >the first place. >>> >>> This may be an issue of your RX/soundcard setup. >>> I can assure you that with my Perseus SDR RX,set to a RBW of less >>> than one Hertz >>> for the display,I can decode every WSPR signal which shows even only >>> a faint trace on >>> the waterfall diagram. >>> At least this is my experience so far. >>> >>> 73 >>> Clemens >>> DL4RAJ >>> >>> ----- Original Message ----- From: mal hamilton >>> To: rsgb >>> Sent: Sunday, November 08, 2009 7:37 PM >>> Subject: LF: WSPR >>> >>> >>> WSPR reports amongst stns indicate reception reports usually minus >>> dB. Most of these stations >>> are usually PLUS dB with me or very close to that figure. >>> So what does that prove. I would say it depends on the RX antenna and >>> not necessarily >>> propagation. A large antenna yields better results than a small loop >>> or active whip. >>> When I switch from my 1/4 wave inv L for 500 khz to a smaller 40 m >>> resonated loop for 500 the >>> signals then do go down to a minus db figure. >>> So what is all this all ABOUT ? >>> There is also the TX pwr to consider. Two transmitters from the same >>> location one using QRO >>> and the other QRP will be received at different levels at a specified >>> RX location. There is a >>> lot of misrepresentation and misleading information by WSPR operator >>> A trace of the signal is visible long before a decode takes place, >>> therefore why not use QRS >>> in the first place. >>> >>> G3KEV >>> >>> >>> >>> >>> >>> >>> No virus found in this incoming message. >>> Checked by AVG - www.avg.com >>> Version: 8.5.425 / Virus Database: 270.14.55/2489 - Release Date: >>> 11/08/09 07:37:00 >>> >>> >> >> >> -------------------------------------------------------------------------------- >> >> >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.425 / Virus Database: 270.14.55/2489 - Release Date: >> 11/08/09 07:37:00 >> >> >> > -------------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.425 / Virus Database: 270.14.55/2489 - Release Date: 11/08/09 07:37:00