Return-Path: Received: (qmail 15335 invoked from network); 16 May 2002 18:01:10 -0000 Received: from unknown (HELO murphys-inbound.services.quay.plus.net) (212.159.14.225) by exhibition.plus.net with SMTP; 16 May 2002 18:01:10 -0000 Received: (qmail 12896 invoked from network); 16 May 2002 18:00:51 -0000 Received: from unknown (HELO post.thorcom.com) (193.82.116.70) by murphys.services.quay.plus.net with SMTP; 16 May 2002 18:00:51 -0000 Received: from majordom by post.thorcom.com with local (Exim 3.33 #2) id 178PWG-0000Dn-00 for rsgb_lf_group-outgoing@blacksheep.org; Thu, 16 May 2002 18:58:28 +0100 Received: from mta7-svc.business.ntl.com ([62.253.164.47]) by post.thorcom.com with esmtp (Exim 3.33 #2) id 178PWF-0000Di-00 for rsgb_lf_group@blacksheep.org; Thu, 16 May 2002 18:58:27 +0100 Received: from l8p8y6 ([62.252.228.169]) by mta7-svc.business.ntl.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020516175825.SWRG8332.mta7-svc.business.ntl.com@l8p8y6> for ; Thu, 16 May 2002 18:58:25 +0100 Message-ID: <002501c1fd03$6ce28bc0$1ee8fc3e@l8p8y6> From: "hamilton mal" To: rsgb_lf_group@blacksheep.org References: <5.1.0.14.0.20020516141438.00a7dd28@gemini.herts.ac.uk> Subject: LF: Re: Re: USA 136kHz proposals Date: Thu, 16 May 2002 18:58:54 +0100 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.4807.1700 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: ----- Original Message ----- From: "James Moritz" To: Sent: Thursday, May 16, 2002 4:24 PM Subject: LF: Re: USA 136kHz proposals > Dear Dave, LF Group > > At 11:28 16/05/2002 +0100, you wrote: > >I see from yesterday's ARRL Letter that the proposal for the USA 136 band > >is for 1W > >ERP and bandwidth less than 100Hz. I am puzzled why they are putting this > >stipulation on bandwidth, > > I suppose it makes sense - otherwise someone could decide to monopolise the > entire band sending SSTV or something. > > > It could be a > >disincentive for normal CW operation (although hopefully most CW will be > >in this > >bandwidth), and presumably will be difficult to enforce. > > It's very easy to measure the bandwidth of signals with spectrogram > software, or a spectrum analyser. Some people would be surprised to see > what their signals look like! How difficult it would be to maintain that > bandwidth depends on the complete specification - how many dB down at 100Hz > BW? If it is 20dB down, no problem, but if it is 60dB down, difficult in > any mode - the mains hum sidebands are usually more than that. > > On a similar note, it would seem premature to start rushing in to band > plans again - remember that the original reason for having the > "transatlantic" signals at the bottom of the band was to avoid CFH on > 137.0kHz in the middle of the band - It is still there, and in the > north-east US states this will certainly have a very direct influence on > operating frequencies for all modes, which could well end up rather > different to those in Europe. Arbitrarily imposing a band plan at this > stage would be less than helpful, and it would be better to wait until US > amateurs have a chance to gain operating experience on the band. I think Jim you have missed the point about the band plan. In EU as you say we operate at the bottom end of the band 135.920 khz approx to avoid a receive problem at the Canadian and USA end because of CFH, which hardly effects us here in Europe, and therefore if they transmit on 137.6 khz approx that avoids any problem. So what is your point!!!!! A lot of experience has already been gained over this past couple of years transatlantic about how to conduct a LF QSO. We need a plan for QRS as I suggested before and above and normal CW operations. These will be the most popular modes and have worked well so far. Other modes FSK/BPSK/JASON etc that take up more b/width will have to be kept separate to avoid qrm and frequency swamping. This is normal procedure for HF dxing ie split frequency working to avoid blocking the dx frequency and mode separation designated frequency areas G3KEV G3KEV > > Cheers, Jim Moritz > 73 de M0BMU > > >