Return-Path: Received: (qmail 15241 invoked from network); 12 Jan 2004 15:33:52 -0000 Received: from unknown (HELO ptb-mxscan03.plus.net) (212.159.14.237) by ptb-mailstore01.plus.net with SMTP; 12 Jan 2004 15:33:52 -0000 Received: (qmail 8477 invoked from network); 12 Jan 2004 15:33:52 -0000 Content-Transfer-Encoding: 8bit X-Filtered-by: Plusnet (hmail v1.01) X-Spam-detection-level: 11 X-Priority: 3 X-MSMail-Priority: Normal Received: from ptb-mxcore03.plus.net (212.159.14.217) by ptb-mxscan03.plus.net with SMTP; 12 Jan 2004 15:33:51 -0000 Received: from post.thorcom.com ([193.82.116.20]) by ptb-mxcore03.plus.net with esmtp (Exim) id 1Ag44d-00025b-1t for dave@picks.force9.co.uk; Mon, 12 Jan 2004 15:33:51 +0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Fake-Domain: majordom Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Ag449-00025b-6y for rs_out@blacksheep.org; Mon, 12 Jan 2004 15:33:21 +0000 Received: from [134.58.240.41] (helo=nibbel.kulnet.kuleuven.ac.be) by post.thorcom.com with esmtp (Exim 4.14) id 1Ag448-00024C-IO for rsgb_lf_group@blacksheep.org; Mon, 12 Jan 2004 15:33:20 +0000 Received: from localhost (localhost [127.0.0.1]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 5CC354B4EA for ; Mon, 12 Jan 2004 16:32:50 +0100 (CET) Received: from lepidus.kulnet.kuleuven.ac.be (lepidus.kulnet.kuleuven.ac.be [134.58.240.72]) by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP id BC9894B617 for ; Mon, 12 Jan 2004 16:32:49 +0100 (CET) X-Fake-Domain: dell-rik.fys.kuleuven.ac.be Received: from dell-rik.fys.kuleuven.ac.be (pc-10-33-165-177.fys.kuleuven.ac.be [10.33.165.177]) by lepidus.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 80E57380151 for ; Mon, 12 Jan 2004 16:32:49 +0100 (CET) Message-ID: <5.1.0.14.0.20040112162906.037a6718@u0019445.kuleuven.be> X-Sender: u0019445@u0019445.kuleuven.be X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 12 Jan 2004 16:35:29 +0100 To: rsgb_lf_group@blacksheep.org From: "Rik Strobbe" In-reply-to: <001301c3d91c$76072fc0$09dc9384@jka> References: <007a01c3d870$20dd0bc0$0500a8c0@charter.net> <304614133.20040112111754@dx.ru> <002801c3d90b$b41134c0$0500a8c0@charter.net> <004401c3d914$cdb10690$1f00a8c0@dellboy> MIME-Version: 1.0 X-Virus-Scanned: by KULeuven Antivirus Cluster Subject: Re: LF: Re: Re: Re: Re: First WOLF QSO! Content-Type: text/plain; charset=us-ascii; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on post.thorcom.com X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-SA-Exim-Scanned: Yes Sender: Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-PN-SPAMFiltered: yes X-Spam-Rating: 1 Hello John, Dave, I believe that it might be difficult to compare QRSS and WOLF as their effectivity also depends on propagation conditions. As WOLF is repeating the message over and over at a rather high speed it can take advantage of short propagation peaks, this is not the case with QRSS where the message is sent a single time at a very slow speed. At the other hand QRSS might be better when propagation is rather stable but very weak (or for surface wave propagation). 73, Rik ON7YD At 09:57 12/01/2004 -0500, you wrote: >Dave, > >We did some tests a couple of years ago involving two similar stations near >each other that were about 1800 km from me. One ran QRSS60, the other WOLF. >I think we did the tests for about a week, and found similar results. >Neither had a clear advantage over that period. The conclusion was that the >effectiveness of WOLF was about the same as QRSS60. > >While our QSO of yesterday did not fully exercise WOLF's capability, do >realize that we were receiving 15 characters in a 20 minute period. QRSS60 >can't do that! > >As originally conceived by Stewart Nelson, the "reference channel" could be >used to exchange signal report information. Neither that nor real-time >decoding has been realized, however. It does remain an interesting mode, >with a number of limitations as listed in Alan Melia's message of this >morning. For U.S. Lowfers, bandwidth is not an issue, and the potential for >anything but very local interference is limited. > >I do believe that gps-locked slower BPSK has more potential at LF, and am >slowly working on getting set up for that. Underline the word "slowly," >though! > >John Andrews, W1TAG