Return-Path: Received: from mtain-da07.r1000.mx.aol.com (mtain-da07.r1000.mx.aol.com [172.29.64.79]) by air-da02.mail.aol.com (v129.4) with ESMTP id MAILINDA023-863a4be25b51a9; Thu, 06 May 2010 02:01:53 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-da07.r1000.mx.aol.com (Internet Inbound) with ESMTP id DD9CF380000E8; Thu, 6 May 2010 02:01:51 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1O9u89-0001nJ-PV for rs_out_1@blacksheep.org; Thu, 06 May 2010 07:00:17 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1O9u89-0001nA-9g for rsgb_lf_group@blacksheep.org; Thu, 06 May 2010 07:00:17 +0100 Received: from moutng.kundenserver.de ([212.227.126.186]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1O9u87-0003mU-5b for rsgb_lf_group@blacksheep.org; Thu, 06 May 2010 07:00:17 +0100 Received: from [192.168.1.64] (188-221-89-85.zone12.bethere.co.uk [188.221.89.85]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MKKYA-1OASMQ3Iec-002Bn2; Thu, 06 May 2010 08:00:08 +0200 From: "Dave Sergeant" To: rsgb_lf_group@blacksheep.org Date: Thu, 06 May 2010 07:00:07 +0100 MIME-Version: 1.0 Message-ID: <4BE25AE7.17008.1C21E7@dave.davesergeant.com> In-reply-to: References: X-mailer: Pegasus Mail for Windows (4.52) Content-description: Mail message body X-Provags-ID: V01U2FsdGVkX1+Zab81S23TO8o1CmXubfolJ8+4AlIdBGMXgSW MtAMJhYyCgHJi45sATqpIEwHgm9PhPHwn6SMI9nreBIJMyt0vv DDouA455yCQ0BnsQtBC7rJqdXcEd7NQ X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: =?UTF-8?Q?Re:_500_Permit_emission=E2=80=99s_bandwidth=3F__EU_and_Global_=3F=3F?= Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: Quoted-printable 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-sid: 3039ac1d404f4be25b4f1171 X-AOL-IP: 193.82.116.20 On 5 May 2010 at 22:39, Graham wrote: > Can any one indicated what is the permitted ~telegraphyTM bandwidth= =20 > of the various ~newTM 500KHz licences or special permits issued round > the EU and now the rest of the Globe ?=20 >=20 > I have the impression that 100 Hz is the maximum ~telegraphyTM > transmission bandwidth, in some cases, eg , Belgium at 100 Hz . Others > appear to be some what wider or not defined ?. =20 >=20 > Norway is CW only ? what is the Dutch allocation ? Southern Ireland > ? ... etc=20 > Are Beacons defined by mode or bandwidth ? It is important to differentiate between 'permitted' as a licence=20 requirement or 'actual' bandwidth. The UK has never had bandwidth (for=20 any mode) specified in its licence for any band, only a general note=20 (note (a) on p. 14) that it should be the minimum that the technology=20 and nature of transmission permit. My 500kHz NOV says nothing=20 whatsoever about bandwidth (only spurious emissions), and for what it=20 is worth at my request is for CW (A1A) only, ie no data. Norway I think=20 is the only country with a permit that does stipulate 100Hz as a=20 licence condition. 100Hz may be the 'actual' bandwidth of a typical CW signal at normal=20 speeds - though will be higher at >60wpm or so, which I have not yet=20 heard on 500kHz. The IARU Region 1 bandplans stipulate that the=20 telegraphy only parts of the bands have a bandwidth of under 200Hz. Also needs to be considered is the receiver bandwidth. Most CW ops will=20 be using 300-400Hz filters, occasionally going to 100-200Hz to=20 eliminate QRM problems. Much has been said about the very narrow=20 bandwidth of some of the data modes, but this is largely irrelevant to=20 the CW op who will still be using much wider filters. A point to be=20 taken into account when deciding which parts of the bands to put CW and=20 data (on any band, not just 136/500). 73 Dave G3YMC http://www.davesergeant.com