X-GM-THRID: 1212236803977233326 X-Gmail-Labels: rsgb lf X-Gmail-Received: 768d17c574f5c4235a3daa9103ce1f62b960aa32 Delivered-To: daveyxm@gmail.com Received: by 10.64.249.16 with SMTP id w16cs120423qbh; Sun, 20 Aug 2006 07:44:28 -0700 (PDT) Received: by 10.49.29.3 with SMTP id g3mr6537503nfj; Sun, 20 Aug 2006 07:44:27 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mx.gmail.com with ESMTP id k24si1161623nfc.2006.08.20.07.44.27; Sun, 20 Aug 2006 07:44:27 -0700 (PDT) Received-SPF: neutral (gmail.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1GEoTT-0005rj-5a for rs_out_1@blacksheep.org; Sun, 20 Aug 2006 15:40:27 +0100 Received: from [193.82.59.130] (helo=relay2.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1GEoTS-0005ra-L5 for rsgb_lf_group@blacksheep.org; Sun, 20 Aug 2006 15:40:26 +0100 Received: from mtaout03-winn.ispmail.ntl.com ([81.103.221.49]) by relay2.thorcom.net with esmtp (Exim 4.51) id 1GEoTO-0006Z5-0A for rsgb_lf_group@blacksheep.org; Sun, 20 Aug 2006 15:40:26 +0100 Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20060820144015.VWVT1865.mtaout03-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com> for ; Sun, 20 Aug 2006 15:40:15 +0100 Received: from mikedennison ([82.10.67.170]) by aamtaout02-winn.ispmail.ntl.com with ESMTP id <20060820144015.FWIW23938.aamtaout02-winn.ispmail.ntl.com@mikedennison> for ; Sun, 20 Aug 2006 15:40:15 +0100 From: "Mike Dennison" To: rsgb_lf_group@blacksheep.org Date: Sun, 20 Aug 2006 15:40:08 +0100 MIME-Version: 1.0 Message-ID: <44E88258.14756.598E2B@localhost> In-reply-to: <001c01c6c455$110d8200$45be3b3e@fujitsu> X-mailer: Pegasus Mail for Windows (4.21c) Content-description: Mail message body X-Spam-Score: -0.1 (/) X-Spam-Report: autolearn=disabled,AWL=-0.110,FORGED_RCVD_HELO=0.05 Subject: Re: LF: QRSS/DFCW timing Content-type: text/plain; charset=US-ASCII 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 Status: O X-Status: X-Keywords: X-UID: 4968 On 20 Aug 2006 at 14:31, Dick wrote: > I wonder if there is anything about fixed TX/RX periods when using > QRSS/DFCW. I mean like it is used to be on moonbounce and > meteorscatter for instance. > > Like transmit 5 minutes, RX 5 minutes, all synchronized of course by > starting at exact the whole hour or so. > > Transmitting QRSS is no longer a question for me, but I do not have > any experience in the 'real' QSO's. There is a need to find a way to > make QSO's as efficient as possible, and also as quick as possible > during the upcoming DX-pedition, because I will be limited in > operation time, and want to work as many as possible, hi. DFCW could > be a nice solution to save time. > > 73 > > Dick