Return-Path: <owner-rsgb_lf_group@blacksheep.org>
Received: from rly-mg02.mx.aol.com (rly-mg02.mail.aol.com [172.20.83.108]) by air-mg05.mail.aol.com (v121_r4.4) with ESMTP id MAILINMG052-9fd4971070221c; Fri, 16 Jan 2009 17:15:42 -0500
Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mg02.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINMG027-9fd4971070221c; Fri, 16 Jan 2009 17:15:31 -0500
Received: from majordom by post.thorcom.com with local (Exim 4.14)
	id 1LNwyJ-0007WC-2u
	for rs_out_1@blacksheep.org; Fri, 16 Jan 2009 22:15:23 +0000
Received: from [83.244.159.144] (helo=relay3.thorcom.net)
	by post.thorcom.com with esmtp (Exim 4.14)
	id 1LNwyI-0007W3-IE
	for rsgb_lf_group@blacksheep.org; Fri, 16 Jan 2009 22:15:22 +0000
Received: from imo-m13.mx.aol.com ([64.12.143.101] helo=imo-m13.mail.aol.com)
	by relay3.thorcom.net with esmtp (Exim 4.63)
	(envelope-from <MarkusVester@aol.com>)
	id 1LNwyG-0000kk-5C
	for rsgb_lf_group@blacksheep.org; Fri, 16 Jan 2009 22:15:22 +0000
Received: from MarkusVester@aol.com
	by imo-m13.mx.aol.com  (mail_out_v39.1.) id l.d0c.46106977 (34976)
	 for <rsgb_lf_group@blacksheep.org>; Fri, 16 Jan 2009 17:15:08 -0500 (EST)
Received: from Black (g230032141.adsl.alicedsl.de [92.230.32.141]) by cia-da08.mx.aol.com (v121_r5.5) with ESMTP id MAILCIADA081-88a0497106ea23e; Fri, 16 Jan 2009 17:15:08 -0500
Message-ID: <1F4FBFE39AD245A3B4A2DDAA4361BA7C@Black>
From: "Markus Vester" <markusvester@aol.com>
To: <rsgb_lf_group@blacksheep.org>
References: <F4E8A04C3CBA4C67AE9C3318F2F40C4F@JimPC> <496E6B45.5020100@usa.net> <0F3DBBAC61C545AE85525CD884B642EC@Black> <20090114231729.6b8aea4f@lurcher> <2AD1A31DF27448F495C0CE7FF33CE9DE@Black> <C4F6E432D5814955A1FDD42B0279F472@AGB> <1E6D0A88C4DE49E5A2AF05911187E7A3@Black> <424931F60B3D4F41AB7DCB9E9FCAB3C5@big7368b9a7d3d> <E68E6C5A539A4838ADAC20BE903CBC68@JimPC> <000e01c97703$df2dfcb0$8d01a8c0@JAYDELL> <5E6F6CB3C59741678D3AE19CEA22B373@JimPC> <45AE4BD5B9164F9A929A6A98D89CF1E6@cahal.danet> <008901c9772e$3b16a2f0$8cd9160a@EFREMOV> <49708674.5080009@telia.com> <006701c97814$91b188a0$8cd9160a@EFREMOV>
In-Reply-To: <006701c97814$91b188a0$8cd9160a@EFREMOV>
Date: Fri, 16 Jan 2009 23:15:05 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6000.16480
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16669
X-Spam-Flag:NO
X-Spam-Score: 0.0 (/)
X-Spam-Report: autolearn=disabled,none
Subject: Re: LF: WSPR does not work
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com
X-Spam-Level: 
X-Spam-Status: No, hits=0.1 required=5.0 tests=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-IP: 193.82.116.20


Hi Andrey,

this has been mentioned before - have you checked your ADC samplerate? See http://www.wsprnet.org/drupal/node/339. If tx and rx 
samplerate deviated by say only 0.3% (ie. 36 Hz from 12 kHz), the bit timing would have shifted by half a symbol duration at the end 
of the 162 bit message. I started having doubts about my own DAC rate when Graham reported negative decoding, but the TX audio 
frequency seems to be correct to within a fraction of a Hz. You could roughly check the rx samplerate by injecting a known 1.5 kHz 
tone and use WSPR spectrogram which resolves ~ 0.1%. Regarding other digital modes, I recall that samplerate was very critical for 
WOLF which relies on a coherent bit frame over a long integration period. On the other hand, it's not much of an issue for PSK31 
which is "freerunning" only for a few symbols.

The maximum tolerable PC clock error between tx and rx seems to be 2.2 seconds. This was the last displayed dt offset before I lost 
track of Jim's consistent signal the other morning. My PC clock is slightly slow and would need resetting more often. But you 
mentioned you have that under tight control.

The WSPR program does not seem to be disturbed or overloaded by strong out-of band signals. Inserting a 200 Hz filter before the 
decoder made no difference at all, even though the total audio power was reduced by 20 or 30 dB. I also did not see any degradation 
when I used very low audio levels. The WSPR spectrogram seems to have a display leveling similar to the Argo AGC option, as the 
colours do not change when the audio gain is varied.

Best wishes
Markus, DF6NM

----- Original Message ----- 
From: "Andrey rn3agc" <rn3agc@mail.ru>
To: <rsgb_lf_group@blacksheep.org>
Sent: Friday, January 16, 2009 8:56 PM
Subject: Re: LF: WSPR does not work


Hello Johan, James, LF,
Many thanks for the help! Yesterday WSPR-signal DF6NM
passed here from time to time much more strongly, than the day
before yesterday. But decoding still was not. I have installed WSJT7.
If again the result is negative, the problem most likely in a sound card
means. Though to this case without problems decoded any amateur
digital protocols.

73
Andrey RN3AGC in KO85SV