Return-Path: Received: from rly-md04.mx.aol.com (rly-md04.mail.aol.com [172.20.29.142]) by air-md02.mail.aol.com (v125.7) with ESMTP id MAILINMD023-8fa4a99b50839; Sat, 29 Aug 2009 19:09:15 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-md04.mx.aol.com (v125.7) with ESMTP id MAILRELAYINMD042-8fa4a99b50839; Sat, 29 Aug 2009 19:08:58 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1MhX1u-00035K-2W for rs_out_1@blacksheep.org; Sun, 30 Aug 2009 00:08:18 +0100 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1MhX1t-00035A-In for rsgb_lf_group@blacksheep.org; Sun, 30 Aug 2009 00:08:17 +0100 Received: from smtp5.freeserve.com ([193.252.22.151] helo=smtp6.freeserve.com) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1MhX1m-00052I-2U for rsgb_lf_group@blacksheep.org; Sun, 30 Aug 2009 00:08:12 +0100 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3518.me.freeserve.com (SMTP Server) with ESMTP id 99AF31C00085 for ; Sun, 30 Aug 2009 01:08:02 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3518.me.freeserve.com (SMTP Server) with ESMTP id 763901C00086 for ; Sun, 30 Aug 2009 01:08:02 +0200 (CEST) Received: from AGB (unknown [91.109.32.120]) by mwinf3518.me.freeserve.com (SMTP Server) with SMTP id 039991C00085 for ; Sun, 30 Aug 2009 01:08:01 +0200 (CEST) X-ME-UUID: 20090829230802148.039991C00085@mwinf3518.me.freeserve.com Message-ID: From: "Graham" To: Date: Sun, 30 Aug 2009 00:08:07 +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,HTML_MESSAGE=0.001 Subject: LF: Quite please , beacons running close to 504 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B1_01CA2905.F3B214F0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE, 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 ------=_NextPart_000_00B1_01CA2905.F3B214F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just WSPR hihi=20 Nice signal from Jim 504 - and Gus 504 + just the other side of 504= Gary also running with a good signal from his 'new' hf to mf convertor ...all showing >>> http://www.wireless.org= .uk/grab/ The big spread of wspr beacon frequency's is / will make wspr mo= nitoring a problem this winter and beyond as the separation falls = out side the bandwidth of the software, the uk frequency, just unde= r 504 was to make use of the quite window close to the 504 carrier'= s noise band , just inside the top of the uk 501>504 allocation. 'We' could re define the 'UK' dial set frequency higher to allow= reception over 504 , but this dose bring with it a strong carrier= in the pass band and the side band noise from 504 .. and will also= increase the possibility of collisions within the uk allocation= should activity increase=20 Any ideas ? Graham .=20 ------=_NextPart_000_00B1_01CA2905.F3B214F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Just   WSPR  hihi
 
Nice signal from Jim 504 - and Gus 50= 4 + just=20 the  other side of 504  Gary also  running with a good&= nbsp;=20 signal from his
'new' hf to  mf  convertor= ...all showing=20 >>>  http://www.wireless.org.uk/grab/
 
The  big  spread of = wspr beacon=20 frequency's is / will  make  wspr  monitoring a problem= =20 this  winter and beyond as the  separation falls  out= side the=20 bandwidth of the  software, the  uk frequency, just under 50= 4 was=20 to  make use of the  quite window close to the 504 =20 carrier's  noise band , just inside the  top of the uk 501&g= t;504=20 allocation.
 
'We' could  re define the = 'UK' dial set=20 frequency  higher to  allow  reception over 504 , but= this =20 dose bring with it a strong carrier in the  pass band and the&nbs= p; side=20 band noise from 504 .. and  will also increase the  possibil= ity=20 of  collisions  within the  uk allocation should = =20 activity  increase
 
Any  ideas ?
 
Graham .
 
 
 
 
------=_NextPart_000_00B1_01CA2905.F3B214F0--