Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: Re: RE: Alignment of (Narrow Band) DATA and WSPR frequency’s

To: <[email protected]>
Subject: Re: LF: Re: RE: Alignment of (Narrow Band) DATA and WSPR frequency’s on the 500 KHz band.
From: "Graham" <[email protected]>
Date: Tue, 15 Feb 2011 19:46:13 -0000
Importance: Normal
In-reply-to: <002d01cbcd02$77e22890$0401a8c0@xphd97xgq27nyf>
References: <6AD920D46A4546ECB1E0FF76E739307C@AGB> <BF4A524700075746A6467658DFC7102C88B050FEB0@ICTS-S-EXC2-CA.luna.kuleuven.be> <002d01cbcd02$77e22890$0401a8c0@xphd97xgq27nyf>
Reply-to: [email protected]
Sender: [email protected]
Thanks  to  'all'
 
This   is the  main  point  of  'post'
 
Due  to  ==Ae  bandwidth and  perhaps  alignment  with   other   band’s==,  I   would  suggest the original WSPR  502.4K is  replaced  with the  lower frequency  of  495.9K , thus  restoring the  System’s  coverage and  facilitating  changes  of mode etc within a  narrow bandwidth
 
Im not  convinced on the  separation  of the  wspr  'band's  in band'  exists  purely  to  prevent  interference, as  once  the  station  separation exceeds  round  75  miles the  ground  signal  has substantially  diminished , moreover  , with  a reasonable   receiver and  soundcard or  direct  conversion, the  dynamic range is quite  sufficient  to  enable  adjacent  decode's ?
 
As  a transmitting  station , I find  I am  unable to  qsy  from the top to  the  bottom of the  band without  incurring  a substantial  increase in the reflected power , due to the  Q of the  'small array' I'm sure other  transmitting  stations  are  also  in this position  , which makes  frequency  changing  some what  laborious  (and  wet if its raining) , the  fixed beacons  in the  USA are  now centred on the  lower frequency .
 
Its now  common to  find  stations  monitoring  ,one  or the other  of the  frequency's  for  wspr  , which effectively  prevents the  spot  capture of  any  TA opening by  EU based stations  monitoring  502.4  and  vice  versa , In point, Last  Sunday  night  at  21:30  gmt  Joe  VO1NA  decoded  my  ROS  data  signal.  while  - NO TA - spots where  showing on wspr , usa and  eu  where monitoring each owns  frequency  slots
 
Band Police :
 
Well  as  recently  demonstrated  in Egypt  even the  police  can  feel  hard done  by , Those  based in the  Uk may well  be  veterans  of the 'war of the  beacons' a sort variation  of the  HG well's  war of the  worlds , where  automated  mania set in and by the  discovery of  ground wave ,  destroyed reception  south  of  Watford gap , so I can understand there  may be a  little  residual  'high tension' in the  'air'
 
 
Summery
 
Side  band  interference  from the  504 signal seems  to  be wider  and  is  causing  problems  with  ROS  and  WSPR decodes (no sun spots ?)
 
TA monitoring  has become  divided rendering  it ineffective and not  capable of  catching  'flash' TA or  other   openings
 
ROS  MF (100hz)  data  mode  frequency  has been  re defined  as  500K dial  set  , putting  it  500Hz  inside the  lower band  edge
 
Ae  bandwidth  considerations prevent  TX stations  from  frequency  change  , hampering   wspr QSY
 
 
Each to  his  own of  course , but a little  alignment  always  helps   !
 
G ..
 
 
 
 
 
 
 
 

Sent: Tuesday, February 15, 2011 11:21 AM
Subject: LF: Re: RE: Alignment of (Narrow Band) DATA and WSPR frequency’s on the 500 KHz band.

This seems a sensible approach. Time division. Keep to the same freq in time slots.
g3kev
 
----- Original Message -----
Sent: Tuesday, February 15, 2011 7:23 AM
Subject: LF: RE: Alignment of (Narrow Band) DATA and WSPR frequency’s on the 500 KHz band.

Hello Graham,
 
I would suggest to have all digital modes as close as possible to the band edges, leaving the band centre for CW.
For WSPR there are currently 2 segments: one for EU stations to transmit on (503.9kHz +/- 100Hz) and one NA stations to transmit on (501.1kHz +/- 100Hz) to avoid local QRM (or better said RX overload).
So 503.7kHz +/- 100Hz and/or 501.3kHz +/- 100Hz for other digimodes ?
It would be possible to have a single data segment for EU and NA it we go from frequency division to time division: if all EU stations would transmit in the xx:00-xx:02, xx:04-xx:06, xx:08-xx:10 ... time slots and all NA stations in the xx:02-xx:04, xx:06-xx-08 ... time slots they can use the same frequency without local QRM.
But this would require a minor chang in the WSPR software (and maybe also other software).
 
73, Rik  ON7YD - OR7T
 

Van: [email protected] [[email protected]] namens Graham [[email protected]]
Verzonden: dinsdag 15 februari 2011 2:20
Aan: [email protected]
CC: Joe Taylor
Onderwerp: LF: Alignment of (Narrow Band) DATA and WSPR frequency’s on the 500 KHz band.

Alignment of  (Narrow Band) DATA  and  WSPR  frequency’s on the  500 KHz  band.

 

The  original wspr frequency   502.4  was  defined  as the  working  frequency  to  utilise the  ‘clean’ 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 ‘dial setting’s’ in use both sides of the Atlantic.

 

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  

 

Due  to  Ae  bandwidth and  perhaps  alignment  with   other   band’s,  I   would  suggest the original WSPR  502.4K is  replaced  with the  lower frequency  of  495.9K , thus  restoring the  System’s  coverage and  facilitating  changes  of mode etc within a  narrow bandwidth.

 

I don’t  see  this  detracting  from the monitoring  of spot  frequency  beacons  over 505Khz , but more  appropriate   to  transmitting  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.

 

Comments  or  suggestions please ?.

 

Graham

G0NBD

 





<Prev in Thread] Current Thread [Next in Thread>