Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: what causes this on wspr

To: <[email protected]>
Subject: Re: LF: what causes this on wspr
From: "Graham" <[email protected]>
Date: Wed, 1 Jul 2015 21:45:19 +0100
Importance: Normal
In-reply-to: <[email protected]>
References: <7D577AEFBA43411C807FDDFBCF90CCC0@AGB> <[email protected]>
Reply-to: [email protected]
Sender: [email protected]
Hi Ed,
 
Andys  email might  of been  slightly  miss directed ,  however ,  the  image  comes  from   down under and we don't  have the  angle on  who  the  tx  is  or  the  Rx type
 
The  signal  causes   '' I am getting multiple entries printed in the receive area''   so  what  ever is  going  on , the  TX is  producing  a  spectrum  ... which  is  being  individually  decoded ,  which  , thinking  about  it ,  sort  of  knocks  the  pll  lock  up   time
and  leaves  FM  of  the  main  carrier  ..
 
This  takes  some  doing  ...... but  how  to  do  it  ?
 
Take 2
 
G,
 
   

From: g3zjo
Sent: Wednesday, July 01, 2015 9:10 PM
Subject: Re: LF: what causes this on wspr

Hi G

You ask the question as if you know the answer. Again.

Hilary Briss is the Butcher in Royston Vasey.

Are you the RX station in the WSPR X capture?  I ask because the transmission started off normal and after a short time went into overload, was this at the RX end, or did the TX start some odd problem, who's TX is it ? It looks like the same station throughout the capture. At 06:38 plus a short period the transmission was curtailed was there a problem again.

Re the U3S problem, I don't know who thought they were key clicks. I identified them as PLL glitches 5 months ago. They don't produce parallel  spaced sidebands as in your capture, they, (like key clicks, would be horizontal in your capture) are spikes which extend way out of the WSPR capture window and as far as KHz as far as my measurement capabilities show, on the higher frequency bands.

It seems that Andy understands this problem well.

73 Eddie



On 01/07/2015 17:24, Graham wrote:
what causes this  on wspr
 
This  takes  some  doing  ...... but  how  to  do  it  ?
 
G,


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