Return-Path: Received: from rly-mc06.mx.aol.com (rly-mc06.mail.aol.com [172.21.164.90]) by air-mc02.mail.aol.com (v125.7) with ESMTP id MAILINMC021-d7f4a9ad4bf1ab; Sun, 30 Aug 2009 15:36:41 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mc06.mx.aol.com (v125.7) with ESMTP id MAILRELAYINMC067-d7f4a9ad4bf1ab; Sun, 30 Aug 2009 15:36:33 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1MhqBq-0000VN-WE for rs_out_1@blacksheep.org; Sun, 30 Aug 2009 20:35:50 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1MhqBq-0000VE-Fc for rsgb_lf_group@blacksheep.org; Sun, 30 Aug 2009 20:35:50 +0100 Received: from smtp5.freeserve.com ([193.252.22.151] helo=smtp6.freeserve.com) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1MhqAz-0006sd-77 for rsgb_lf_group@blacksheep.org; Sun, 30 Aug 2009 20:34:58 +0100 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3509.me.freeserve.com (SMTP Server) with ESMTP id 2CE907000089 for ; Sun, 30 Aug 2009 21:35:38 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3509.me.freeserve.com (SMTP Server) with ESMTP id 2006C700008A for ; Sun, 30 Aug 2009 21:35:38 +0200 (CEST) Received: from AGB (unknown [91.109.40.206]) by mwinf3509.me.freeserve.com (SMTP Server) with SMTP id 538267000089 for ; Sun, 30 Aug 2009 21:35:35 +0200 (CEST) X-ME-UUID: 20090830193535342.538267000089@mwinf3509.me.freeserve.com Message-ID: <40274402B60647A2AD99F8612AF7FA44@AGB> From: "Graham" To: References: <211F6B38DA2544AD84B814000D47EDF6@AGB> <0F69884C983F4F198A9B4B4F276326AD@radiorummet> In-Reply-To: <0F69884C983F4F198A9B4B4F276326AD@radiorummet> Date: Sun, 30 Aug 2009 20:35:33 +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-Karma: unknown: X-Spam-Score: 0.3 (/) X-Spam-Report: autolearn=disabled,HTML_FONT_BIG=0.256,HTML_MESSAGE=0.001 Subject: LF: Quite please , beacons running close to 504 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0050_01CA29B1.6C007540" 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_0050_01CA29B1.6C007540 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ok Gus =20 That's ok but for example 508 is a long way from the uk band ,= which presents a problem if you set up a wspr monitor either side= of the pond .. as to what do you receive on ..508 or 504 .....?= =20 G ..=20 from a previous post >>> 090826 0012 7 -17 -0.3 0.508513 W22XGR= FN31 57=20 From: Gus=20 Sent: Sunday, August 30, 2009 1:25 PM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: Re: Fw: Quite please , beacons running close to 504=20 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 ----------------------------------------------------------------------= ---------- No virus found in this incoming message. Checked by AVG - www.avg.com=20 Version: 8.5.409 / Virus Database: 270.13.71/2335 - Release Date: 08/3= 0/09 06:36:00 ------=_NextPart_000_0050_01CA29B1.6C007540 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ok Gus 
 
That's  ok but for  example=   =20 508  is a long way from the  uk band , which presents a prob= lem if=20 you  set up a wspr  monitor  either side of the pond ..= as=20 to  what do  you  receive on ..508  or  504&n= bsp;=20 .....?
 
G ..
 
from a=20 previous  post >>> 090826 0012   7 -17 = =20 -0.3   0.508513  W22XGR FN31 57
 

From: Gus
Sent: Sunday, August 30, 2009 1:25 PM
Subject: LF: Re: Fw: Quite please , beacons running close= to 504=20

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 .
 
 
 
 


No virus found in this incoming message.
Checked by AVG= -=20 www.avg.com
Version: 8.5.409 / Virus Database: 270.13.71/2335 - Re= lease=20 Date: 08/30/09 06:36:00
------=_NextPart_000_0050_01CA29B1.6C007540--