X-GM-THRID: 1241131072477485154 X-Gmail-Labels: rsgb lf Delivered-To: daveyxm@gmail.com Received: by 10.78.172.10 with SMTP id u10cs485295hue; Thu, 5 Jul 2007 04:27:07 -0700 (PDT) Received: by 10.82.108.9 with SMTP id g9mr19956907buc.1183634827479; Thu, 05 Jul 2007 04:27:07 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mx.google.com with ESMTP id k10si13322007nfh.2007.07.05.04.27.03; Thu, 05 Jul 2007 04:27:07 -0700 (PDT) Received-SPF: neutral (google.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) DomainKey-Status: bad (test mode) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1I6PQ6-0002G9-1z for rs_out_1@blacksheep.org; Thu, 05 Jul 2007 12:22:46 +0100 Received: from [193.82.59.130] (helo=relay2.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1I6PQ5-0002G0-Fw for rsgb_lf_group@blacksheep.org; Thu, 05 Jul 2007 12:22:45 +0100 Received: from smtp805.mail.ird.yahoo.com ([217.146.188.65]) by relay2.thorcom.net with smtp (Exim 4.63) (envelope-from ) id 1I6PQ1-0001uH-1q for rsgb_lf_group@blacksheep.org; Thu, 05 Jul 2007 12:22:44 +0100 Received: (qmail 29718 invoked from network); 5 Jul 2007 11:22:34 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=F6qtZoy4oZZ1qVtrClbRbExYzAOPCO6aby4zp+iciMvTTKzrytRCHxgWq55QmOaM/8S7YuS18VMHCwwPZT4kNtKTr6ylXIuGuLFERwmJJzeaaSCoN1lq9AAqioCfk6a1iYRV22gAT0fplSHky5VDZ6+a5mZpYUE80XaKfb5rZXY= ; Received: from unknown (HELO lark) (alan.melia@btinternet.com@213.122.49.51 with login) by smtp805.mail.ird.yahoo.com with SMTP; 5 Jul 2007 11:22:33 -0000 X-YMail-OSG: 51BdlBMVM1mPQhDVo2XfAIF3Vs3Nc5bdFcArWqcb4eEIgSBwpH7Ss1ZcwALgsP6y9TILOfEHOg-- Message-ID: <001701c7bef6$c8bcd800$0300a8c0@lark> From: "Alan Melia" To: Date: Thu, 5 Jul 2007 12:22:28 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 DomainKey-Status: good (testing) X-Spam-Score: -0.4 (/) X-Spam-Report: autolearn=disabled,AWL=-0.383 Subject: LF: QRSS Content-Type: text/plain; charset="iso-8859-1" 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: 1531 Whilst I apprciate that the "constant" nature of QRSS can be a problem, I am afraid there are some misconceptions about its use. It should NOT be NECESSARY to send a morse call at "normal" speeds. This may be advisable in some cases, in the way of making normal qsos, but it is no more "necessary" than a 30wpm operator needing to send his ID at 5wpm. The mode is actually morse and 3sec dot can be read audibly with a little practice. It became unnecessary for RTTY operators to send a morse ID many years ago (this was anyway for the benefit of the RIS officers, not other amateurs), and this archaic regulation is even less necessary now we have fairly common usage of these modes and common PC usage within many stations. If you dont want to use a PC in your station that is fair but it is sufficient surely to know that the mode exists, it has been around a long time at LF. There is another reason for not sending "normal" speed morse ids. It precludes the efficient stacking of QRSS stations which can exist within a very narrow bandwidth. On 136 I have seen as many as 6 stations in a bandwidth of less than 1Hz. The morse id also sometimes causes confusion with the identification of the weak QRSS information at extreme range. This is a narrow band and we are hardly in the QRM situation. Only on a few occasions have I seen more than three stations active at the same time. At the same time, one must not expect to be able to operate with a barn-door wide receiver and blame its failings on everyone else. QRSS has other uses. We tend in the UK to be very parochial, and on several occasions on 136kHz operators tried to impose our idea of a "band plan" on operators in other countires, where conditions were different. At present there is 500khz interest in many European counties but they are not in the fortunate position of being able to transmit. (The exception being several special "commercial" permits). Our use of QRSS gives then something to listen (look ?) for and keeps the flag flying for a world wide band in this area. It is also giving useful information about the potential range covered by transmissions and aiding our case for an eventual sensible operating power level. Interest soon flags if you cant hear any signals, and international support will be necessary if we are to achieve a band here. It is unfortunate that the ARRL sponsored FCC Part 5 permits in this area have concentrated on using 500k as an interstate chat band. This is understandable when considering the nature of the application with reference the emergency comms, but it adds little to our case for an international allocation. Alan G3NYK