Return-Path: Received: (qmail 4950 invoked from network); 11 Mar 1999 18:50:13 -0000 Received: from magnet.plus.net.uk (HELO magnet.force9.net) (195.166.128.26) by medusa.plus.net.uk with SMTP; 11 Mar 1999 18:50:13 -0000 Received: (qmail 17121 invoked from network); 11 Mar 1999 18:52:47 -0000 Received: from post.thorcom.com (194.75.130.70) by magnet.plus.net.uk with SMTP; 11 Mar 1999 18:52:47 -0000 Received: from troy.blacksheep.org ([194.75.183.50] ident=root) by post.thorcom.com with esmtp (Exim 2.04 #3) id 10LAXs-0000Dp-00; Thu, 11 Mar 1999 18:51:00 +0000 Received: (from root@localhost) by troy.blacksheep.org (8.6.12/8.6.12) id SAA04954 for rsgb_lf_group-outgoing; Thu, 11 Mar 1999 18:47:18 GMT X-Priority: 3 X-MSMail-Priority: Normal Received: from post.thorcom.com (root@post.unica.co.uk [194.75.183.70]) by troy.blacksheep.org (8.6.12/8.6.12) with ESMTP id SAA04699 for ; Thu, 11 Mar 1999 18:27:24 GMT Received: from nms.rz.uni-kiel.de ([134.245.1.2]) by post.thorcom.com with smtp (Exim 2.04 #3) id 10LAE5-0007d0-00 for rsgb_lf_group@blacksheep.org; Thu, 11 Mar 1999 18:30:34 +0000 Received: from mail.uni-kiel.d400.de (actually srv1.mail.uni-kiel.de) by nms.rz.uni-kiel.de with Local-SMTP (PP); Thu, 11 Mar 1999 19:26:15 +0100 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Received: from nephro.uni-kiel.de by mail.uni-kiel.d400.de (SMI-8.6/SMI-SVR4) id TAA01096; Thu, 11 Mar 1999 19:26:13 +0100 Message-ID: <36E80AD5.D800041A@nephro.uni-kiel.de> Date: Thu, 11 Mar 1999 19:26:29 +0100 From: "Peter W. Schnoor" Organization: University of Kiel, Clinic of Nephrology X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.33 i586) To: rsgb_lf_group@blacksheep.org Subject: Re: LF: QRSs References: <1999031115053268199@zetnet.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org Hello Group, Hello Peter, Peter Dodd wrote: > What tends to happen in practice is that if the signal is audible > then a RST report is sent. > If it is sent in the form, say '42N' (the N being a delimiter rather > than a tone) I cannot see anything wrong with that. > It has been suggested that to use four dashes _ _ _ _. This could be > used to say 'the signal is audible and reduce the dot size if you > want to get the QSO over a bit quicker'. I vote for the four dashes in *this* meaning for three reasons: 1. Dashes are much more detectable as dots especially in cases of pulsatile and/or Lux-Effect noise circumstances. If A could hear B very well, B could detect A very bad due to local conditions. 2. It stands for nothing I guess (apart from the old fashioned german "ch"). 3. It would be a good match to the dashed style of TMO. > The main problem is that on being told that the signal is audible > there is a temptation to go for fast CW. It happened to me (twice) > but I wont go for fast CW again in the middle of a SCW QSO. A signal could be audible but nearly unreadable in "fast" Morse. Detecting a carrier is much easier than to understand a "normal speed" code (not only for neurophysiologic reasons...). "Reducing dot length" could mean in steps of 500ms. > There are two reasons: > The bandwidth settings and often the receiver tuning have to be > re-adjusted. During this performance the signal can get lost. > The present unofficial bandplan, with all SCW above 137.65 seems to > be working quite well. To use fast CW in that part of the band (when > the band is busy) is a bit unsociable. Agreed! > The simplest solutions are nearly always the best. Fully agreed! Adding four dashes to our source codes should be very easy. (I'm using the "!" for encoding it...) 54°16'N / 10°04'E, JO54ag 73 es gl de Peter, DF3LP