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=-0.7 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_MESSAGE,RATWARE_GECKO_BUILD 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 t61KDrND015086 for ; Wed, 1 Jul 2015 22:13:53 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ZAOL6-00047r-Do for rs_out_1@blacksheep.org; Wed, 01 Jul 2015 21:10:36 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ZAOL6-00047i-1N for rsgb_lf_group@blacksheep.org; Wed, 01 Jul 2015 21:10:36 +0100 Received: from out1.ip07ir2.opaltelecom.net ([62.24.128.243]) by relay1.thorcom.net with esmtp (Exim 4.85) (envelope-from ) id 1ZAOL4-0005rA-Db for rsgb_lf_group@blacksheep.org; Wed, 01 Jul 2015 21:10:34 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BHAgDoSJRVPGV4lk4NT4JFhR6DLrwEglQCgiIBAQEBAQEHAQEBAUGEYgEBAQMjZgsJDwkWCwICCQMCAQIBMRQTCAEBvTxwlwQBAQgCAR+LSoUNFoJSgUMFlBCLYYE6ky2DXYIyHIFTgzYBAQE X-IPAS-Result: A2BHAgDoSJRVPGV4lk4NT4JFhR6DLrwEglQCgiIBAQEBAQEHAQEBAUGEYgEBAQMjZgsJDwkWCwICCQMCAQIBMRQTCAEBvTxwlwQBAQgCAR+LSoUNFoJSgUMFlBCLYYE6ky2DXYIyHIFTgzYBAQE X-IronPort-AV: E=Sophos;i="5.15,388,1432594800"; d="scan'208,217";a="159800414" Received: from host-78-150-120-101.as13285.net (HELO [192.168.1.2]) ([78.150.120.101]) by out1.ip07ir2.opaltelecom.net with ESMTP; 01 Jul 2015 21:10:17 +0100 Message-ID: <55944927.6020601@psk31.plus.com> Date: Wed, 01 Jul 2015 21:10:15 +0100 From: g3zjo User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <7D577AEFBA43411C807FDDFBCF90CCC0@AGB> In-Reply-To: <7D577AEFBA43411C807FDDFBCF90CCC0@AGB> X-Scan-Signature: 64bc660a83b79b15f4c44d2b2147e02d Subject: Re: LF: what causes this on wspr Content-Type: multipart/alternative; boundary="------------050607080203030207060400" 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: 3599 This is a multi-part message in MIME format. --------------050607080203030207060400 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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, > --------------050607080203030207060400 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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,

--------------050607080203030207060400--