Return-Path: Received: from rly-md05.mx.aol.com (rly-md05.mail.aol.com [172.20.29.143]) by air-md10.mail.aol.com (v125.7) with ESMTP id MAILINMD103-9024a9a6fd4350; Sun, 30 Aug 2009 08:26:04 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-md05.mx.aol.com (v125.7) with ESMTP id MAILRELAYINMD052-9024a9a6fd4350; Sun, 30 Aug 2009 08:25:58 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1MhjTC-0006UU-5I for rs_out_1@blacksheep.org; Sun, 30 Aug 2009 13:25:18 +0100 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1MhjTB-0006UL-KT for rsgb_lf_group@blacksheep.org; Sun, 30 Aug 2009 13:25:17 +0100 Received: from fwx.uvtc.net ([195.22.25.2] helo=uvtcmail.se) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1MhjT4-0004uA-89 for rsgb_lf_group@blacksheep.org; Sun, 30 Aug 2009 13:25:12 +0100 thread-index: AcopbOWrytsrYcq/RP2biWsPJwL35w== X-MEFilter-Version: 6.5.0 Received: from ([127.0.0.1]) with MailEnable ESMTP; Sun, 30 Aug 2009 13:25:00 +0100 Message-ID: <0F69884C983F4F198A9B4B4F276326AD@radiorummet> From: "Gus" To: References: <211F6B38DA2544AD84B814000D47EDF6@AGB> In-Reply-To: <211F6B38DA2544AD84B814000D47EDF6@AGB> Date: Sun, 30 Aug 2009 14:25:01 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18005 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325 Content-Class: urn:content-classes:message Importance: normal X-ME-Bayesian: 0.000000 X-CHK: uvtcmail.se X-Spam-Score: 0.3 (/) X-Spam-Report: autolearn=disabled,HTML_FONT_BIG=0.256,HTML_MESSAGE=0.001,UNPARSEABLE_RELAY=0.001 Subject: LF: Re: Fw: Quite please , beacons running close to 504 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01CA297D.A91FBA00" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.7 required=5.0 tests=HTML_40_50,HTML_FONT_BIG, 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_0009_01CA297D.A91FBA00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Graham, for me there is no problem to tramsmit under 504 kHz. Why not run WSPR beacon from 503.900- 504.000 kHz !? de Gus SM6BHZ ----- Original Message -----=20 From: Graham=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Sunday, August 30, 2009 1:29 PM Subject: LF: Fw: Quite please , beacons running close to 504=20 From: Graham=20 Sent: Sunday, August 30, 2009 12:08 AM To: rsgb_lf_group@blacksheep.org=20 Subject: Quite please , beacons running close to 504=20 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.o= rg.uk/grab/ The big spread of wspr beacon frequency's is / will make wspr= monitoring a problem this winter and beyond as the separation fall= s out side the bandwidth of the software, the uk frequency, just un= der 504 was to make use of the quite window close to the 504 carrie= r'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_0009_01CA297D.A91FBA00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Graham,
 
for me there is no problem to tramsmit= under 504=20 kHz.
Why not run WSPR beacon from 503.900-= 504.000 kHz=20 !?
 
de Gus SM6BHZ
 
----- Original Message -----
From:=20 Graham
Sent: Sunday, August 30, 2009= 1:29=20 PM
Subject: LF: Fw: Quite please= , beacons=20 running close to 504

 

From: Graham
Sent: Sunday, August 30, 2009 12:08 AM
Subject: Quite please , beacons running close to 504=20

Just   WSPR  hihi =
 
Nice signal from Jim 504 - and Gus= 504 + just=20 the  other side of 504  Gary also  running with a goo= d =20 signal from his
'new' hf to  mf  converto= r ...all=20 showing >>>  http://www.wireless.org.uk/grab/
 
The  big  spread of = wspr beacon=20 frequency's is / will  make  wspr  monitoring a probl= em=20 this  winter and beyond as the  separation falls  out= side the=20 bandwidth of the  software, the  uk frequency, just under= 504 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= >504=20 allocation.
 
'We' could  re define the = ; 'UK' dial=20 set frequency  higher to  allow  reception over 504= , but=20 this  dose bring with it a strong carrier in the  pass ban= d and=20 the  side band noise from 504 .. and  will also increase= the =20 possibility of  collisions  within the  uk allocation= =20 should  activity  increase
 
Any  ideas ?
 
Graham .
 
 
 
 
------=_NextPart_000_0009_01CA297D.A91FBA00--