Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-db05.r1000.mx.aol.com (Internet Inbound) with ESMTP id EE141380000B6; Tue, 28 Feb 2012 05:11:29 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1S2K14-0003So-Jc for rs_out_1@blacksheep.org; Tue, 28 Feb 2012 10:10:42 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1S2K14-0003Sf-4B for rsgb_lf_group@blacksheep.org; Tue, 28 Feb 2012 10:10:42 +0000 Received: from nm4.bt.bullet.mail.ird.yahoo.com ([212.82.108.235]) by relay1.thorcom.net with smtp (Exim 4.63) (envelope-from ) id 1S2K13-0001aM-LY for rsgb_lf_group@blacksheep.org; Tue, 28 Feb 2012 10:10:42 +0000 Received: from [212.82.108.228] by nm4.bt.bullet.mail.ird.yahoo.com with NNFMP; 28 Feb 2012 10:10:36 -0000 Received: from [212.82.108.225] by tm1.bt.bullet.mail.ird.yahoo.com with NNFMP; 28 Feb 2012 10:10:36 -0000 Received: from [127.0.0.1] by omp1002.bt.mail.ird.yahoo.com with NNFMP; 28 Feb 2012 10:10:36 -0000 X-Yahoo-Newman-Id: 52850.46744.bm@omp1002.bt.mail.ird.yahoo.com Received: (qmail 32962 invoked from network); 28 Feb 2012 10:10:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:To:References:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:In-Reply-To:X-MimeOLE:Thread-Index; b=UwynK3mJPNoDn6R+/aZwcMzi4QwAsgj0bdu/IgJP8Edzy11v63QCaOEbRPI9uvCZBK0aRSAxPBk6pTwb0v5MINRxBw4rxwHa1Dvr30N9mlLl0EsGootwjz79icakRNEIr+jFXDoQ5pvXRk0gvYEpFCfkS0Tlo52qJ3fh+Bd9kvw= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1330423835; bh=6ex7T73hDEVFO+ZB3qrW7nHEL715hUt2VbGFx243P3k=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:To:References:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:In-Reply-To:X-MimeOLE:Thread-Index; b=T2MKKjVvkMRzYLHHU7qIqv8R468ak2rkZQa0gQg9e9dWZNCHmC3RZKHOuFh+m0T7n7CRVJeN+iiCo6nkdXYQ/1D7p2EUj+w9vel84Bl6SbeWl2lraCvEgiGEBG9E/WUD5AEmt9Y1EdKJqIJx6h6JaO2txPHhG3hKz8rZemN3hMA= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: QERWcG0VM1nZAX1kr49wkrGH9TAjNwSbTEMZSMu3Trg9WQi KRyPf0gL57ROyylv.fDAoaRNKAj.1Fey4jFW8qB6ajvItSv4HegIvtQ8JLI8 0x76k3SYNlOUyhficag.cU0IkstmeIFEKAePbhz7F49.PX55n7P9LbMyh6JX ZgHr3NHQd6DP3PVd1077B0GjcxkWtdQU37MXY8XdSVwrQf2lW1gkkYwsPYe. Yn1aDO8fLaPS9u3ONC9yj.0OZpWF6VoFEn2u1eEntIWrVKhUabeiiQIHzP4n GjAxEK7.mjTA5VJUP6CWDNTJfFYDxlBhCeaqIDKL8F9kLBnHkSGfX.OfUuo1 DQ3U1IaxznQ.Lmw0WtalDM2LPYd.qRb7iiB_gr2BlbSOZu5f69pe2vgnEgNE Psoou.PsWA0DcwQKLrmYefTnqrMCB7.Eq X-Yahoo-SMTP: 9Y6mUHuswBAgnrOsukIiNdFDf95uy_Dz34nY1hlg2liKgYD952sjbg-- Received: from lindavideo (ken.h.wright@86.149.193.253 with login) by smtp815.mail.ukl.yahoo.com with SMTP; 28 Feb 2012 10:10:35 +0000 GMT From: "Ken" To: References: <74845C11BC3444D79B63A207E428BDE0@lindavideo> <1205576556-1330352309-cardhu_decombobulator_blackberry.rim.net-124445598-@b27.c11.bise7.blackberry> <005701ccf561$cd9d4250$0401a8c0@xphd97xgq27nyf> <098856018E3A46AB96BA9F9FC6C8FFCD@JimPC> Date: Tue, 28 Feb 2012 10:10:33 -0000 Message-ID: <58AD05C381A841E9B1C5A0FEDD3E3043@lindavideo> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <098856018E3A46AB96BA9F9FC6C8FFCD@JimPC> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Thread-Index: Acz1rIdMpttzihVaSq2JOaWAvHP8fwAU8oLw DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,UNPARSEABLE_RELAY=0.001 Subject: LF: RE: Re: NDBs & WRC-12 LF band allocation 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.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 x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:497139584:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m257.1 ; domain : btinternet.com DKIM : fail x-aol-sid: 3039ac1d40594f4ca85160fa X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dear Jim, Mal, LF Group. All I was trying to say in my message was 'if we could hear say 10 or 12 NDBs in the UK, would there be sufficient bandwidth left between each NDB for us to safely operate using whatever modes we are assigned' Sorry if I caused any confussion. 73s Ken M0KHW -----Original Message----- From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of James Moritz Sent: 28 February 2012 00:03 To: rsgb_lf_group@blacksheep.org Subject: LF: Re: NDBs & WRC-12 LF band allocation Dear Mal, Ken, LF Group, G3KEV wrote: >The band should be licensed for CW operators only so that they could >recognize and read the CW beacons and AVOID >them. One does not need to be a morse code expert to realise there is a strong signal repeating the same dots and dashes 24 hours a day on a particular frequency. One just needs a little common sense... >Has OFCOM thought of this. Neither should there be any amateur unattended >BEACONS to jam the Primary user >Beacons even unintentionally. Whether the transmission is a "manual" QSO or automated, or if an NoV for an unattended beacon was being applied for, the important thing for the amateur is to be aware of nearby NDBs and avoid transmitting on their frequencies - this is a matter of observation and advance planning, not operating. If a couple of amateurs are yakking away about the WX on a NDB frequency, in CW or any other mode, there is no way that the NDB will be able to break in at the end of one over and say "excuse me chaps, but there are aircraft trying to get a bearing on this frequency; would you mind QSYing - thank you so much" ;-) Think about this from the Primary User's point of view - if someone navigating an aircraft sets their ADF receiver to a particular beacon frequency and hears an assortment of amateur-generated morse code mixed up with the beacon ID, this is likely to cause confusion or error. So there is a strong argument for amateurs not to use morse code at all in this frequency range. It would be better to use totally different types of transmission that would not be confused with a NDB beacon signal. Cheers, Jim Moritz 73 de M0BMU