Return-Path: Received: from rly-mf10.mx.aol.com (rly-mf10.mail.aol.com [172.20.29.180]) by air-mf09.mail.aol.com (v121_r4.4) with ESMTP id MAILINMF094-988497f53cc38; Tue, 27 Jan 2009 13:36:39 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mf10.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINMF106-988497f53cc38; Tue, 27 Jan 2009 13:36:27 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LRslb-0002GP-Uj for rs_out_1@blacksheep.org; Tue, 27 Jan 2009 18:34:31 +0000 Received: from [193.82.59.130] (helo=relay2.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LRslb-0002GG-9Y for rsgb_lf_group@blacksheep.org; Tue, 27 Jan 2009 18:34:31 +0000 Received: from smtp-out-3.talktalk.net ([62.24.128.233] helo=smtp.talktalk.net) by relay2.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LRslZ-00017M-Jx for rsgb_lf_group@blacksheep.org; Tue, 27 Jan 2009 18:34:30 +0000 X-Path: TTSMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ar8EAKTifklZ8+WJ/2dsb2JhbACEXMcHhUw Received: from unknown (HELO mal769a60aa920) ([89.243.229.137]) by smtp.talktalk.net with SMTP; 27 Jan 2009 18:34:23 +0000 Message-ID: <00ef01c980ad$e06b5d80$0301a8c0@mal769a60aa920> From: "mal hamilton" To: References: <004f01c9809a$708b5c30$0301a8c0@mal769a60aa920>, <497F3902.1070604@sighthound.demon.co.uk> <497F5976.5945.1B872C2@v.d.heide.on-line.de> Date: Tue, 27 Jan 2009 18:34:23 -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.0 (/) X-Spam-Report: autolearn=disabled,none Subject: !QRe: LF: PROPAGATION 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=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 Klaus They are flogging a dead horse but cannot see it mal/g3kev ----- Original Message ----- From: "Klaus von der Heide" To: Sent: Tuesday, January 27, 2009 5:59 PM Subject: Re: LF: PROPAGATION WSPR > > Dear LF Group, > > we should clearly differenciate between all aspects. > > A propagation study does not need any information transfer > via the radio path other than confidence on the identity of > the station in focus. In that case, observing the carrier > is best. So WSPR has no advantage over QRSS. > > On the other hand, WSPR has the advantage of automatic > recording. But that is not an advantage of the mode, it > simply is the lack of a corresponding simple program that > does the same with a QRSS signal. > > If the propagation is monitored with the final goal to > make a QSO at appropriate conditions, then the information > transfer gets important. In that case, WSPR may outperform > QRSS by a few dBs (at the same error rate). > > Nevertheless, WSPR is not very near to the Shannon limit. > I spent nearly all my leisure time of the last year with > the design of a new digital ham radio QSO-mode HD43 that > comes as close as possible to the theoretical limit. > I will send a preprint on request. > > 73 de Klaus, DJ5HG > > > >> mal hamilton wrote: >> > On LF I do not think wspr is the correct mode to study propagation >> >> Good points Mal. However CW for manual reception and QRSS, to be viewed >> on a waterfall display, are fine for all manner of uses and in extremis >> QRSS is probably more sensitive than WSPR. However QRSS requires the >> receiving station to be actively watching the screen all the time, or to >> save traces automatically and then manually review them, by eye, later. >> >> This is rather time consuming and laborious. >> >> WSPR may have it's downsides, and the problems last night with G0NBD >> aside, I've never had any problems decoding anything I can visually see, >> and also much that I could not hear and would be at the threshold of >> QRSS useabilty. >> >> I have confidence that what I see reported by the software is a >> reasonable representation of what was transmitted, and it's much easier >> to quantify changes in signal strength vs time with the WSPR data than >> estimating by eye the quality of a QRSS transmission. >> >> It may not be accurate in terms of actual reported S/N ratio, but it's >> consistent from session to session, and gives numbers to work with, if >> that's your interest. >> >> Not everyone can sit waiting for the brief propagation opening, so >> automating the process at least adds another facet this interesting >> hobby. >> >> If it hurts no-one then what's the harm? >> >> Regards, >> >> John >> GM4SLV >> >> >> > > > -------------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.14/1917 - Release Date: 1/26/2009 6:37 PM