Return-Path: Received: from mtain-mc06.r1000.mx.aol.com (mtain-mc06.r1000.mx.aol.com [172.29.96.78]) by air-da10.mail.aol.com (v129.4) with ESMTP id MAILINDA102-861a4d59d54d243; Mon, 14 Feb 2011 20:22:21 -0500 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mc06.r1000.mx.aol.com (Internet Inbound) with ESMTP id 29B5C380000AE; Mon, 14 Feb 2011 20:22:19 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Pp9b9-0003Hf-5C for rs_out_1@blacksheep.org; Tue, 15 Feb 2011 01:20:59 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Pp9b8-0003HW-Gw for rsgb_lf_group@blacksheep.org; Tue, 15 Feb 2011 01:20:58 +0000 Received: from smtp6.freeserve.com ([193.252.22.190]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1Pp9b6-0000wh-NE for rsgb_lf_group@blacksheep.org; Tue, 15 Feb 2011 01:20:58 +0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3631.me.freeserve.com (SMTP Server) with ESMTP id 267E97000095; Tue, 15 Feb 2011 02:20:50 +0100 (CET) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3631.me.freeserve.com (SMTP Server) with ESMTP id 1AE507000096; Tue, 15 Feb 2011 02:20:50 +0100 (CET) Received: from AGB (unknown [91.109.19.29]) by mwinf3631.me.freeserve.com (SMTP Server) with SMTP id 624167000095; Tue, 15 Feb 2011 02:20:49 +0100 (CET) X-ME-UUID: 20110215012049402.624167000095@mwinf3631.me.freeserve.com Message-ID: <6AD920D46A4546ECB1E0FF76E739307C@AGB> From: "Graham" To: Cc: "Joe Taylor" Date: Tue, 15 Feb 2011 01:20:48 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Antivirus: avast! (VPS 110214-1, 14/02/2011), Outbound message X-Antivirus-Status: Clean X-Spam-Score: 1.5 (+) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001,SUBJECT_ENCODED_TWICE=1.543 Subject: LF: =?utf-8?Q?Alignment_of__=28Narrow_Band=29_DATA?= =?utf-8?Q?__and__WSPR__frequency=E2=80=99s_on_the_?= =?utf-8?Q?_500_KHz__band.?= Content-Type: multipart/alternative; boundary="----=_NextPart_000_02BF_01CBCCAE.93AAA100" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.2 required=5.0 tests=HTML_60_70,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-global-disposition: G x-aol-sid: 3039ac1d604e4d59d54b4fe3 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none ------=_NextPart_000_02BF_01CBCCAE.93AAA100 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Alignment of (Narrow Band) DATA and WSPR frequency=E2=80=99s on th= e 500 KHz band. =20 The original wspr frequency 502.4 was defined as the working = frequency to utilise the =E2=80=98clean=E2=80=99 area just under= the 504 harmonic, whilst avoiding the various beacons running = across the 501/504 band at the time. However, time has moved on= and there are now numerous =E2=80=98dial setting=E2=80=99s=E2=80=99= in use both sides of the Atlantic. =20 Due to an apparent increase in the side band noise from the 504= signal , possibly by enhanced propagation , the ROS MF (100 hz= b/w) working frequency is to be re defined as 500 USB dial set= giving a centre carrier frequency of 501.500 =20 =20 Due to Ae bandwidth and perhaps alignment with other band=E2= =80=99s, I would suggest the original WSPR 502.4K is replaced = with the lower frequency of 495.9K , thus restoring the System= =E2=80=99s coverage and facilitating changes of mode etc within a= narrow bandwidth.=20 =20 I don=E2=80=99t see this detracting from the monitoring of spot= frequency beacons over 505Khz , but more appropriate to transm= itting stations , which by the nature of the antenna arrays are = not able comfortably to qsy from top to bottom of the band= without re-tuning, not always a simple option. =20 Comments or suggestions please ?. =20 Graham G0NBD =20 ------=_NextPart_000_02BF_01CBCCAE.93AAA100 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Alignment of  (Narrow=20 Band) DATA &nbs= p;and  WSPR  frequency=E2=80=99s on= the  500 KHz =20 band.

 

= The  original wspr fre= quency   502.4  was  defined  as the  working  frequency<= SPAN style=3D"mso-spacerun: yes">  to =20 utilise the  =E2= =80=98clean=E2=80=99=20 area  just under the  504  harmonic, whilst avoiding the  various  beacons&n= bsp; running  a= cross  the  501/504  band at the 

= Due to  an apparent  increase  in the  side band&n= bsp; noise  fro= m the  504 signal , po= ssibly by  enhanced  propagation , the  <= SPAN lang=3DEN-GB>ROS  MF  (100 hz b/w) working  frequency is  to be re defined as  500  USB dial&nbs= p; set  giving= a  centre  carrier  frequency of 501.500  

 

= Due  to =20 Ae  bandwidth and=   perhaps  alignment  with&nbs= p;  other   band=E2=80=99s,  I   <= /SPAN>would  suggest= the original WSPR  50= 2.4K is  replaced  with the  lower frequency  of = =20 495.9K , thus  re= storing=20 the  System=E2=80=99s  coverage and  facilitating  changes  of mode etc within a  narrow bandwidth.

 

= I don=E2=80=99t  see =20 this  detracting<= SPAN style=3D"mso-spacerun: yes">  from the monitoring  of spot  frequency  beacons&= nbsp; over 505Khz , but more  appropriate &n= bsp; to  transm= itting  stations , whi= ch  by the  nature of the  antenna arrays are  not&n= bsp; able  comf= ortably  to =20 qsy  from  top  to = =20 bottom of the  ba= nd=20 without  re-tuning, not  always a  simple =20 option.

 

= Comments  or =20 suggestions please ?.

 

Graham

G0NBD

 



------=_NextPart_000_02BF_01CBCCAE.93AAA100--