To: | <[email protected]> |
---|---|
Subject: | LF: Re: NDBs & WRC-12 LF band allocation |
From: | "James Moritz" <[email protected]> |
Date: | Tue, 28 Feb 2012 00:02:35 -0000 |
Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=btopenworld.com; s=s1024; t=1330387357; bh=LPBkJfMBZ3hy3+tcFCpN6L8MucbbqOQj/YILQzjN21A=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:From:To:References:In-Reply-To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=xIT9TQIgTac6jpyL5VPqxrcG+z01RLSB8HZP61rC6W5Cqj7/J8Y5lkX7/3IgeY4T3MHdz9DAP7kog2Dt3DIzC/21OV9PKQs6/+iBrVatfECbSnkVB8RXd0GT39zdVTMYTF1FgzKPwUuj65w1xFl+LGSjj6y6+SUCyHqNghl93Vg= |
Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btopenworld.com; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:From:To:References:In-Reply-To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=d7FL8xkbmhvBuEI6n7FgpLQGYtdhU6wJsXUD/FlK2AZFViPGz7crgOBdVbtODFWfOiTUwfFRjBkNC9QbcK+4HshOfA9guL2B9S74QK5xcz+GnCUZOjxUBUkL7XAS4FylqRLiAE30IlWGeen8wMZawT7YNd+aS8roZM6UHGEShnM= ; |
Domainkey-status: | good (testing) |
In-reply-to: | <005701ccf561$cd9d4250$0401a8c0@xphd97xgq27nyf> |
References: | <74845C11BC3444D79B63A207E428BDE0@lindavideo> <C4EE404465AB4B2C89B9809DE06DD805@oem92799c6e374> <1205576556-1330352309-cardhu_decombobulator_blackberry.rim.net-124445598-@b27.c11.bise7.blackberry> <005701ccf561$cd9d4250$0401a8c0@xphd97xgq27nyf> |
Reply-to: | [email protected] |
Sender: | [email protected] |
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 |
Previous by Date: | LF: VE1VDM Grabber, Vernon Matheson |
---|---|
Next by Date: | Re: LF: Who is it?, Roman RW3ADB |
Previous by Thread: | Re: LF: Re: NDBs & WRC-12 LF band allocation, M0FMT |
Next by Thread: | LF: Re: NDBs & WRC-12 LF band allocation, Dave Sergeant |
Indexes: | [Date] [Thread] [Top] [All Lists] |