Return-Path: Received: (qmail 1184 invoked from network); 1 Jan 2001 17:34:22 -0000 Received: from unknown (HELO warrior-inbound.servers.plus.net) (212.159.14.227) by excalibur.plus.net with SMTP; 1 Jan 2001 17:34:22 -0000 Received: (qmail 9267 invoked from network); 1 Jan 2001 17:29:05 -0000 Received: from unknown (HELO post.thorcom.com) (212.172.148.70) by warrior with SMTP; 1 Jan 2001 17:29:05 -0000 Received: from majordom by post.thorcom.com with local (Exim 3.16 #1) id 14D8dj-0007Td-00 for rsgb_lf_group-outgoing@blacksheep.org; Mon, 01 Jan 2001 17:20:55 +0000 Received: from mta03.talk21.com ([62.172.192.172] helo=t21mta03-app.talk21.com) by post.thorcom.com with esmtp (Exim 3.16 #1) id 14D8di-0007TY-00 for rsgb_lf_group@blacksheep.org; Mon, 01 Jan 2001 17:20:54 +0000 Received: from dave ([213.120.25.96]) by t21mta03-app.talk21.com (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20010101172151.KDBS1799.t21mta03-app.talk21.com@dave> for ; Mon, 1 Jan 2001 17:21:51 +0000 Message-ID: <000b01c07416$f675ed40$601978d5@dave> From: "Dave Sergeant" To: rsgb_lf_group@blacksheep.org References: Subject: LF: Re: LF Test freqs Date: Mon, 1 Jan 2001 17:11:12 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group Sender: >From Dave G3YMC At the expense of increasing the digital divide on 136!! The 136kHz band is slightly different from other hf bands in so far that it is rather narrow, and there is a far greater conflict between the various modes of transmission which are all fighting for space. To date we have had CW, QRSS, BPSK and associated data modes, and now we are getting slow voice which requires its own space. It is therefore always going to be difficult to provide enough space for all users without mutual interference. The band plan which has been worked out (admittedly a couple of years ago when some of the modes were not active) was produced in good faith, and like the band plans on the higher bands it makes life easier for us all if they are followed. Up to recently most of the slow CW and data communication has indeed been confined to their allocated parts of the band, and this has worked well, with very little mutual interference between normal CW and the data modes. However a conflict in situations both here and in Canada/USA threatens to upset this relationship. There is an analogy between unwanted mixing of SSB and CW on hf, whereas an SSB QSO can be conducted with CW interference in the background, whereas the SSB signal gives significant interference problems to the CW operator. In a similar way, users of slow CW and other spectrogram modes have so much more selectivity in their digital processors that they are not usually effected by signals 10s of Hz away unless these are very strong local ones. The normal CW op, using normal receive filters assisted with audio filtering, can find such adjacent signals disasterous. And the inability to identify in normal CW and respond when transmitting such digital modes seems rather unsatisfactory. I would strongly urge all operation on slow CW and other data modes to continue to be made in the recognised parts of the band, and leave 136.0-137.4 for normal CW. There are indeed times when this part of the band may be quiet and unused, but at busy times (eg Sunday mornings) it is barely adequate. If it is possible to get Jack to move his test transmissions out of this section it would be appreciated - although Jack's signal is unlikely to affect a normal CW operator, the unintentional QRM caused by an operator who does not know he is there could be a problem. Hopefully there will not be a repeat of the events of Saturday night. 73s Dave G3YMC (on the analogue side of the digital divide...) sergeantd@compuserve.com dsergeant@iee.org http://ourworld.compuserve.com/homepages/sergeantd