Return-Path: Received: from rly-mh08.mx.aol.com (rly-mh08.mail.aol.com [172.21.166.144]) by air-mh08.mail.aol.com (v121_r5.5) with ESMTP id MAILINMH082-bee494d4e48122; Sat, 20 Dec 2008 14:58:18 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mh08.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINMH086-bee494d4e48122; Sat, 20 Dec 2008 14:58:04 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LE7xI-0000Lr-Pn for rs_out_1@blacksheep.org; Sat, 20 Dec 2008 19:57:44 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LE7xI-0000Li-3n for rsgb_lf_group@blacksheep.org; Sat, 20 Dec 2008 19:57:44 +0000 Received: from smtp805.mail.ird.yahoo.com ([217.146.188.65]) by relay3.thorcom.net with smtp (Exim 4.63) (envelope-from ) id 1LE7xG-0006RS-De for rsgb_lf_group@blacksheep.org; Sat, 20 Dec 2008 19:57:44 +0000 Received: (qmail 34057 invoked from network); 20 Dec 2008 19:57:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btopenworld.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=YUvC2UqolF/F9c/7gVzIO106dvlI3NUgxXdT2sls73gY6nkxkKqlyF5KrWbP/6Fh9jNL39C/DNDlbPzxOg6wWVXsJRXaeqdqXBvKmE1BkjMVFKq2zhk3iYoYf4AHr2DwbtW97dSzHXSIO7SZOU/RR6wvm9U0Grftsn6zMZKbChM= ; Received: from unknown (HELO w4o8m9) (james.moritz@86.134.108.92 with login) by smtp805.mail.ird.yahoo.com with SMTP; 20 Dec 2008 19:57:35 -0000 X-YMail-OSG: c.8cZg4VM1nk3Lz42PF4Ci6hu7Qmzxyspix0dNTf7a2c4W4myHdi7ESTvWvXDFQhRcQXUmCPHBgQ7aK3zgYf6KRngA8cjJ15Drr5MQZABxBL3BMvBJrnQiN9uWsKxYITGj.r_iUnhCNIixSuGaIlTld3FbWss0iSs7feOfnzb9zBmdrf1ZimxFcsBnHw X-Yahoo-Newman-Property: ymail-3 Received: from 127.0.0.1 (AVG SMTP 7.5.552 [270.9.19/1857]); Fri, 19 Dec 2008 19:56:51 +0000 Message-ID: <000701c96213$ef3e2da0$4201a8c0@home> From: "James Moritz" To: Date: Fri, 19 Dec 2008 19:56:36 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: Re: Extension of the UK's 500kHz NOVs 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-IP: 193.82.116.20 Dear John, LF Group, First, many thanks for your continued efforts in getting us access to these out-of-the-way, but interesting, bits of spectrum, and I certainly look forward to an extension to my NoV. Re - possible limits on transmission bandwidth. Most of the modes that have been used on 500kHz will fit within a 200Hz bandwidth, so having this restriction would rarely be a great hardship . However, I think it is fair to say that none of the current modes have proved ideal for the particular features of this band, in particular the deep QSB, which often mean that DX contacts get interrupted several times during the duration of the contact. The HF-type modes struggle with the poor SNR, while the very low-speed LF modes get chopped up by the QSB. In my opinion, this might be handled well by some kind of specialised ARQ mode designed for weak signal conditions and long fading periods. There has been some good work done on the effectiveness of existing data modes on 500kHz, but these tend to be designed for HF and above, with the expectation of a TX/RX bandwidth of around 3kHz, and so are mostly wider than one would like to use at LF/MF. I guess for software writers, it is difficult to justify all the effort in creating new modes specially for 500k when there is only a very small number of potential users. In the long term, when hopefully 500kHz will become a fully fledged amateur band like 136k, it will probably be neccessary to have an upper limit on the bandwidth just so that a reasonable number of stations can use the band simultaneously. But in the meantime, with only a small pool of band users, quite wide signal bandwidths do not really cause a problem to other amateur stations. Provided the signals stay within the allocated frequency range, it seems unlikely that it would affect other spectrum users, none of whom seem to use frequencies close to the current UK amateur allocation. Perhaps what is needed is a specification on the maximum out-of-band levels permitted? Re: TX ERP levels - Some extra power would always be welcome, although it might not make a massive difference to the actual coverage achieved, especially since the band is currently largely confined to the UK. My antenna experiments suggest that with reasonable"back garden" antennas, 10W ERP at 500k would require TX power levels of the order of 1kW, somewhat less than needed to achieve 1W ERP on 136kHz, and a rather lower antenna voltage than required to achieve 1W ERP on 136k. So actually achieving this ERP level ought to be practical for stations in average locations. Was it stated which services are of particular concern to MCA regarding interference? I guess the activity in mainland Europe and the USA should be a good guide to possible interference problems - I have not yet heard of any serious QRM problems caused by these higher ERP stations. Cheers, Jim Moritz 73 de M0BMU