Return-Path: Received: from rly-mg03.mx.aol.com (rly-mg03.mail.aol.com [172.20.83.109]) by air-mg10.mail.aol.com (v125.7) with ESMTP id MAILINMG102-a024ab7d2a515d; Mon, 21 Sep 2009 15:23:40 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mg03.mx.aol.com (v125.7) with ESMTP id MAILRELAYINMG034-a024ab7d2a515d; Mon, 21 Sep 2009 15:23:19 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1MpoSi-0007xZ-Ub for rs_out_1@blacksheep.org; Mon, 21 Sep 2009 20:22:12 +0100 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1MpoSi-0007xQ-50 for rsgb_lf_group@blacksheep.org; Mon, 21 Sep 2009 20:22:12 +0100 Received: from smtp5.freeserve.com ([193.252.22.152]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1MpoSW-00079C-7U for rsgb_lf_group@blacksheep.org; Mon, 21 Sep 2009 20:22:04 +0100 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3424.me.freeserve.com (SMTP Server) with ESMTP id CCF311C00084 for ; Mon, 21 Sep 2009 21:21:54 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3424.me.freeserve.com (SMTP Server) with ESMTP id BD36C1C00086 for ; Mon, 21 Sep 2009 21:21:54 +0200 (CEST) Received: from AGB (unknown [91.109.10.186]) by mwinf3424.me.freeserve.com (SMTP Server) with SMTP id 67B8C1C00084 for ; Mon, 21 Sep 2009 21:21:54 +0200 (CEST) X-ME-UUID: 20090921192154424.67B8C1C00084@mwinf3424.me.freeserve.com Message-ID: <7CAF11CF41AF460A8AD0DDF5EE5BB32D@AGB> From: "Graham" To: References: <47C531A902A946C9BE2EEC5C6B7E2EF3@presario1> <1775028CB7C146B496121BA36FB7093D@AGB> <146FC3C1737F42A38DA305D2D83EF4B3@JimPC> In-Reply-To: <146FC3C1737F42A38DA305D2D83EF4B3@JimPC> Date: Mon, 21 Sep 2009 20:21:53 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8064.206 X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8064.206 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: Re: US 500-kHz band plan Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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.1 required=5.0 tests=MISSING_OUTLOOK_NAME 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 That seems to be a reasonable situation Jim ?. After running the wspr system for a considerable time, with the 504 carrier in the pass band, it seems 'not' to cause false decodes as I originally feared, from this, I would suggest that the top section of the band be retained for wspr usage , possibly raising the dial set 100 hz ? As I am 'fortunate' (?) to receive the 504 signal at a level where the 'am' modulation may be resolved at times , it can be observed that a clear window exists close in to the carrier frequency, approaching 100 hz wide, the same exists on the hf side of the signal, wide enough for wspr operations. This may also be beneficial to the g4jnt multi mode beacon, which, due to antenna 'q' may not welcome a change of tx frequency from the top to the bottom of the band dictated by mode ? G .. -------------------------------------------------- From: "James Moritz" Sent: Monday, September 21, 2009 7:30 PM To: Subject: Re: LF: Re: US 500-kHz band plan > > Dear Graham, LF Group, > >> As the European allocation looks to be wider than the Uk, are we >> expecting the UK 3 Khz allocation to remain as is, if and when the >> band is formalised ?, in which case loosing 200 hz may not be the most >> sensible option ... > > As I understand it, there are not yet any formal Europe-wide proposals, > just > what individual regulators have allocated on a case-by-case basis. I think > G, EI, and ON have all allocated 501 - 504. The DL beacons and OK0EMW are > licenced to use spot frequencies around 505kHz. Gus SM6BHZ would be able > to > use 504.0 - 504.1kHz. > >> >> As by definition , if you can transmit wspr you must be able to move >> transmit frequency (noting Andy's new beacon) establishing an over >> lapping 100 hz section may be a reasonable compromise ie move the dial >> frequency to say 502.5 or 499.5 , leaving 100 hz in band for uk access >> > > > > > > >> >> -------------------------------------------------- >> From: "James Moritz" >> Sent: Monday, September 21, 2009 2:14 PM >> To: >> Subject: LF: Re: US 500-kHz band plan >> >>> >>> Dear LF Group, >>> >>> I still haven't replied to Fritz Raab, W1FR, regarding the WD2XSH US >>> band >>> plan which he is apparently coordinating - you may remember I posted the >>> US >>> proposals, which he sent me, a couple of weeks ago, but have not >>> received >>> any comments from other UK/Eu stations. I think I should reply with >>> something, so now is your chance... The proposal relates to the US >>> allocation extending to 495 - 515kHz, and how that would fit in with >>> current >>> UK and Eu beacon operations. The content of the e-mail is below. The >>> issue >>> is that they would like to make a 501.0 - 501.2kHz WSPR sub-band, to fit >>> in >>> with the various other proposals. Various other types of beacon modes >>> are >>> allocated frequencies outside the UK/EI/ON 501 - 504kHz range, while >>> 501.2 - >>> 504kHz is allocated to "general comms". Retaining frequencies just below >>> 504kHz would divide their "general comms" band in two >>> >>> I don't think there is anything preventing us from doing this, it is >>> just >>> the inconvenience of turning the current band "upside-down". Let me know >>> what you think! >>> >>> Cheers, Jim Moritz >>> 73 de M0BMU >>> >>>>>>From W1FR: >>> >>> Greetings: >>> >>> Thanks for the comments on the band plan, passed >>> along to me by W1XP. >>> >>> About a month ago, a modification to the WD2XSH >>> license was approved that adds stations and gives us >>> access to 495 - 510 kHz. Perhaps half of the 42 stations >>> will eventually get on the air. Because of NDBs, some >>> stations are limited to parts of this band and we will >>> have two calling frequencies and two beacon bands. >>> >>> A draft of our new band plan follows. Of particular >>> interest is WSPR. As I see it, our options are: >>> >>> (a) 501.0-501.2: Conveniently on one side of our comms >>> band. Will not overload WSPR receivers near 504 kHz. >>> Apparently in EU CW-beacon band. >>> >>> (b) 503.8-504.0: Apparently same as what you guys are >>> using. Cuts our comms band in the middle. Nearby >>> stations may overload US receivers trying to hear EUs. >>> >>> (c) 503.9-504.1: Same problems as above with cutting >>> comms band in two and overloading. Conveniently >>> straddles both G/ON/EI and Canadian bands. >>> >>> Any further thoughts you may have will be >>> appreciated. >>> >>> >>> 73, Fritz, W1FR >>> >>> Frederick H. (Fritz) Raab, Ph.D. >>> GREEN MOUNTAIN RADIO RESEARCH COMPANY >>> 77 Vermont Avenue, Fort Ethan Allen >>> Colchester, Vermont 05446 USA >>> Tel./Fax.: +1 (802) 655-9670 Home: +1 (802) 862-0997 >>> E-mail: f.raab@ieee.org >>> >>> BASIC BAND PLAN for WD2XSH >>> >>> f, kHz USE >>> >>> 495.0 - 495.1 QRSS, 1-Hz spacing, 40 stations >>> 495.1 - 495.6 CW/PSK beacons midwest, 100-Hz spacing, 10 stations >>> 495.6 - 499.0 Comms >>> 497.5 Calling frequency >>> 499.0 - 501.0 Reserved for heritage stations and special events >>> 501.0 - 501.2 WSPR >>> 501.2 - 505.0 Comms >>> 505.0 - 505.2 DX window >>> 505.2 - 508.5 Comms >>> 507.5 Calling frequency >>> 508.5 - 510.0 CW/PSK beacons east, south, west, Pacific, 50-Hz >>> spacing, >>> 30 >>> stations >>> 510.0 - 511.0 WE2XGR beacons >>> 511.0 - 515.0 WE2XGR SSB and wideband modes >>> >>> >>> OTHER IN-BAND SIGNALS >>> >>> 503.976 NEED LSB >>> 505.0 NEED carrier >>> 506.024 NEED USB >>> >>> 508.976 OF/FA LSB >>> 510.0 OF/FA carrier >>> 511.024 OF/FA USB >>> >>> >>> >> >> >> >>> >>> No virus found in this incoming message. >>> Checked by AVG - www.avg.com >>> Version: 8.5.409 / Virus Database: 270.13.109/2384 - Release Date: >>> 09/20/09 06:22:00 >>> >> >> >> > > > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.409 / Virus Database: 270.13.111/2386 - Release Date: > 09/21/09 05:51:00 >