Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-ma06.r1000.mx.aol.com (Internet Inbound) with ESMTP id BE0D03800008C; Tue, 28 Feb 2012 05:34:41 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1S2KNZ-0003sL-Hy for rs_out_1@blacksheep.org; Tue, 28 Feb 2012 10:33:57 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1S2KNZ-0003sC-44 for rsgb_lf_group@blacksheep.org; Tue, 28 Feb 2012 10:33:57 +0000 Received: from out1.ip02ir2.opaltelecom.net ([62.24.128.238]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1S2KNX-0001pj-O7 for rsgb_lf_group@blacksheep.org; Tue, 28 Feb 2012 10:33:57 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak4FAMGsTE9Ok80c/2dsb2JhbAA9BolyqgaBCIFuBQEBBAEIAQEDSQITEwYBAQMFAgEDEQQBAQEJHgcUAQQaBg0JCAYTCgECAgEBh3AJuBuJEHWCdgULBRcCAlIJAgEBhQAPM0aDHgSIHIU6mlk X-IronPort-AV: E=Sophos;i="4.73,495,1325462400"; d="scan'208";a="386529738" Received: from host-78-147-205-28.as13285.net (HELO xphd97xgq27nyf) ([78.147.205.28]) by out1.ip02ir2.opaltelecom.net with SMTP; 28 Feb 2012 10:33:45 +0000 Message-ID: <001901ccf604$72b33130$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <74845C11BC3444D79B63A207E428BDE0@lindavideo> <1205576556-1330352309-cardhu_decombobulator_blackberry.rim.net-124445598-@b27.c11.bise7.blackberry> <005701ccf561$cd9d4250$0401a8c0@xphd97xgq27nyf> <098856018E3A46AB96BA9F9FC6C8FFCD@JimPC> <58AD05C381A841E9B1C5A0FEDD3E3043@lindavideo> Date: Tue, 28 Feb 2012 10:33:39 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: Re: RE: Re: NDBs & WRC-12 LF band allocation 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 x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:500979552:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d600e4f4cadc031f7 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Ken It could be tight at times especially for those with a good RX/Antenna therefore the ability to hear a good many NDB'S and try to squeeze into a vacant slot. Another problem for those with Ferrite rod and uProbe RX antennas they will not hear a lot of these Beacons and therefore could well be transmitting on top of them. This was an unusual slot to pick for radio amateur use. de mal/g3kev ----- Original Message ----- From: "Ken" To: Sent: Tuesday, February 28, 2012 10:10 AM Subject: LF: RE: Re: NDBs & WRC-12 LF band allocation > 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 > > > >