Return-Path: X-Spam-DCC: paranoid 1290; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_MESSAGE autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id t61KmrBc015178 for ; Wed, 1 Jul 2015 22:48:53 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ZAOsl-0004H3-QL for rs_out_1@blacksheep.org; Wed, 01 Jul 2015 21:45:23 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ZAOsl-0004Gu-GH for rsgb_lf_group@blacksheep.org; Wed, 01 Jul 2015 21:45:23 +0100 Received: from smtpout2.wanadoo.co.uk ([80.12.242.42] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.85) (envelope-from ) id 1ZAOsj-0005zO-O8 for rsgb_lf_group@blacksheep.org; Wed, 01 Jul 2015 21:45:22 +0100 Received: from AGB ([95.150.80.230]) by mwinf5d29 with ME id n8lK1q00X4y94kF038lL4r; Wed, 01 Jul 2015 22:45:21 +0200 X-ME-Helo: AGB X-ME-Date: Wed, 01 Jul 2015 22:45:21 +0200 X-ME-IP: 95.150.80.230 Message-ID: <7F06C09E9A224575A448D3C4EA77D42F@AGB> From: "Graham" To: References: <7D577AEFBA43411C807FDDFBCF90CCC0@AGB> <55944927.6020601@psk31.plus.com> In-Reply-To: <55944927.6020601@psk31.plus.com> Date: Wed, 1 Jul 2015 21:45:19 +0100 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-Scan-Signature: 96c1546db5321e0e52b4c66d17932f07 Subject: Re: LF: what causes this on wspr Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A5_01D0B447.39C9D270" 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-Scanned-By: MIMEDefang 2.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 3600 This is a multi-part message in MIME format. ------=_NextPart_000_00A5_01D0B447.39C9D270 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Ed,=20 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=20 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=20 and leaves FM of the main carrier ..=20 This takes some doing ...... but how to do it ?=20 Take 2=20 G, =20 From: g3zjo=20 Sent: Wednesday, July 01, 2015 9:10 PM To: rsgb_lf_group@blacksheep.org=20 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:=20 what causes this on wspr=20 This takes some doing ...... but how to do it ? G, ------=_NextPart_000_00A5_01D0B447.39C9D270 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Ed,
 
Andys  email might  of been  slightly  miss = directed=20 ,  however ,  the  image  comes  = from   down=20 under and we don't  have the  angle on  who  = the =20 tx  is  or  the  Rx type
 
The  signal  causes   '' I am = getting=20 multiple entries printed in the receive area''   so  = what  ever is  going  on , the  TX is  = producing =20 a  spectrum  ... which  is  being =20 individually  decoded ,  which  , thinking  = about  it=20 ,  sort  of  knocks  the  pll  lock =20 up   time
and  leaves  FM  of  the  main =20 carrier  ..=20
 
This  takes  some  doing  ...... but  = how =20 to  do  it  ?
 
Take 2
 
G,
 
   

From: g3zjo
Sent: Wednesday, July 01, 2015 9:10 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: Re: LF: what causes this on wspr

Hi G

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

Hilary Briss is the Butcher in Royston Vasey.

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

Re the U3S problem, I = don't know=20 who thought they were key clicks. I identified them as PLL glitches 5 = months=20 ago. They don't produce parallel  spaced sidebands as in your = capture,=20 they, (like key clicks, would be horizontal in your capture) are spikes = which=20 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=20 that Andy understands this problem well.

73 = Eddie



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


------=_NextPart_000_00A5_01D0B447.39C9D270--