X-GM-THRID: 1212236803977233326 X-Gmail-Labels: rsgb lf X-Gmail-Received: c0f7df1b2361e42ef32bc1ead58b79ca637577e4 Delivered-To: daveyxm@gmail.com Received: by 10.64.249.16 with SMTP id w16cs121383qbh; Sun, 20 Aug 2006 08:10:50 -0700 (PDT) Received: by 10.49.29.3 with SMTP id g3mr6568841nfj; Sun, 20 Aug 2006 08:10:49 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mx.gmail.com with ESMTP id h1si19492nfe.2006.08.20.08.10.48; Sun, 20 Aug 2006 08:10:49 -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 1GEot7-00069j-1a for rs_out_1@blacksheep.org; Sun, 20 Aug 2006 16:06:57 +0100 Received: from [193.82.59.130] (helo=relay2.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1GEot6-00069a-Hn for rsgb_lf_group@blacksheep.org; Sun, 20 Aug 2006 16:06:56 +0100 Received: from mtaout03-winn.ispmail.ntl.com ([81.103.221.49]) by relay2.thorcom.net with esmtp (Exim 4.51) id 1GEot2-0006m2-Cs for rsgb_lf_group@blacksheep.org; Sun, 20 Aug 2006 16:06:56 +0100 Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20060820150646.WNLX1865.mtaout03-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com> for ; Sun, 20 Aug 2006 16:06:46 +0100 Received: from mikedennison ([82.10.67.170]) by aamtaout02-winn.ispmail.ntl.com with ESMTP id <20060820150646.GDNR23938.aamtaout02-winn.ispmail.ntl.com@mikedennison> for ; Sun, 20 Aug 2006 16:06:46 +0100 From: "Mike Dennison" To: rsgb_lf_group@blacksheep.org Date: Sun, 20 Aug 2006 16:06:40 +0100 MIME-Version: 1.0 Message-ID: <44E88890.25087.71D9F8@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.102,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.1 required=5.0 tests=LINES_OF_YELLING, LINES_OF_YELLING_2 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: 4967 Dick, There are no fixed periods. The essential thing is to keep QSOs as short as possible. A typical minimum QSO might be: CQ G3XDV K (note that 'de' is never used and only one callsign is sent) G3XDV PA4VHF K PA4VHF XDV O O K (just the sufffix is used after full callsigns have been exhanged. Reports are O for 100% readable, M for readable with difficulty, and T for unreadable) XDV VHF R O O TU SK (use TU for "thank you") VHF XDV R TU SK (and that is the end) When there is more time, you might give a locator. Some stations send "73", but this is very time-consuming. A question mark is used as a short form of "QRZ?" For an expedition things might be even more brief as they are on HF (but some people argue that full calls must be exchanged to make a valid QSO). Perhaps an expedition with callsign LX1XX might have QSOs like this: CQ LX1XX XX G3XDV K G3XDV O K R O SK R SK XX G3YXM K G3YXM O K R O SK R SK and so on ..... There have been QSOs where the DX station works two people at once since two QRSS stations can often be copied at once, but I would not recommend this. I do suggest that before you leave home you notify this group of your transmit frequency (say 137.730kHz) and a receive range (say 137.680- 137.690kHz) and try to operate split to avoid long delays when unsuccessful callers are still on your frequency. Hope this helps. Mike, G3XDV ========== > 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