Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dc04.r1000.mx.aol.com (Internet Inbound) with ESMTP id 3533738000084; Tue, 16 Oct 2012 22:08:42 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TOJ2h-0005zi-Sy for rs_out_1@blacksheep.org; Wed, 17 Oct 2012 03:07:31 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TOJ2h-0005zZ-DT for rsgb_lf_group@blacksheep.org; Wed, 17 Oct 2012 03:07:31 +0100 Received: from mail-pa0-f43.google.com ([209.85.220.43]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77) (envelope-from ) id 1TOJ2f-0008AJ-77 for rsgb_lf_group@blacksheep.org; Wed, 17 Oct 2012 03:07:30 +0100 Received: by mail-pa0-f43.google.com with SMTP id fb1so7459433pad.16 for ; Tue, 16 Oct 2012 19:07:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language :x-gm-message-state; bh=72uxToO2Atp1Y5k/+aJSBc0Vvp2MZ7LyMbjuJaZharA=; b=HcdG1ufnnS1YEpSjag978rFVHo7fwYGOFUAqiI7dSqIfvFR/3lScF4RNosj7BIzeLh eERHMQZ3Hn7YT+QE7CLMdMYgqp1SeDsZ8kcbzP+WV1UmUzDNyvAghgv5u4HJ+pTNpvXV fdHBnFTW5O0LA6TPit0eGIdNIDlXQUYaaBl3eh+EtvSuZOPt/ZelqOnDgLyCpFrfcfiy RurXHyeTwFkOKfvoOb3hu8WiMuZLutaZByrYDDOfUap0BE3y7FygAoAP73FQfbME3U/C eLNmvrg0TiwpK9owunWJ3eJnUoQQsyG5lfK+reMlMLJqtpq/CCUgwz7VUIury9dXalX+ vB4Q== Received: by 10.68.211.99 with SMTP id nb3mr52865368pbc.16.1350439638389; Tue, 16 Oct 2012 19:07:18 -0700 (PDT) Received: from dell810itu ([203.81.88.191]) by mx.google.com with ESMTPS id nm2sm3432578pbc.43.2012.10.16.19.07.15 (version=SSLv3 cipher=OTHER); Tue, 16 Oct 2012 19:07:17 -0700 (PDT) From: Terry GW0EZY To: References: <507D5247.5040100@iup.uni-heidelberg.de> <3clq785amof88d6frrqe43vdhflt34h0p1@4ax.com> <507D57F6.7090809@iup.uni-heidelberg.de> <507D5F1D.1060007@iup.uni-heidelberg.de> <507D9B44.4020803@iup.uni-heidelberg.de> <507D9D8F.9010904@iup.uni-heidelberg.de> <4BFEB0320D3840B6B88F2125BA0ECAEF@White> In-Reply-To: <4BFEB0320D3840B6B88F2125BA0ECAEF@White> Date: Wed, 17 Oct 2012 08:37:01 +0630 Message-ID: <003901cdac0c$1bc93a90$535bafb0$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac2r6tK+XG8YxjUNSeiA2rRfcItSEAAIGJ0w Content-Language: en-gb X-Gm-Message-State: ALoCoQnFNtcsqVp22br47SoPsK2OeQ7IpBAxcznC17qkGao8x8sbzBU8I+ksLGq9SC9O/LgkRYsPaXlU1kULpTSPbrLswwGMc4P2XP+r7fJs2QB4Be6ploxkyEr6f9kwsFf00ggd/x2gR5Wdf/JsATqvCTQ+Sotu4/DQVXYXUAqBuXNKnyHxlgRbh7XM/k3OXDqV5adHmyxr X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Markus I've seen it during the slow WSPR experiments when I had to use a "dial" frequency offset for the speed-changer but I didn't solve the problem as the results of any changes to the slow WSPR parameters take too long to appear! I suspect it may be a "safety" feature in the WSPR upload function to prevent non-amateur reports being sent to the database? [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [209.85.220.43 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 9be3f060697a097db7a337109fbeece1 Subject: RE: LF: WSPR on LF Content-Type: multipart/alternative; boundary="----=_NextPart_000_003A_01CDAC42.9745DE90" 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=HTML_60_70,HTML_MESSAGE 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-global-disposition: G x-aol-sid: 3039ac1d4084507e132a5bf6 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_003A_01CDAC42.9745DE90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Markus I've seen it during the slow WSPR experiments when I had to use a "dial" frequency offset for the speed-changer but I didn't solve the problem as the results of any changes to the slow WSPR parameters take too long to appear! I suspect it may be a "safety" feature in the WSPR upload function to prevent non-amateur reports being sent to the database? 73 Terry XZ/GW0EZY Yesterday I finally got WSPR 2.11 working in IQ-mode with the FiFi-SDR on MF. Today I changed back to LF (which is 0.1355 MHz dial and 2000 Hz BFO here) and got fine decodes, but no uploads, with a persistant error message "frequency changed no upload of spots". Tried all sorts of different settings (which is time consuming) but didn't succeed - anyone out there who has seen and solved this? Now back to WSPR 2.0 with same parameters, running just fine. ------=_NextPart_000_003A_01CDAC42.9745DE90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Markus

 

I’ve seen it during the slow WSPR experiments when I had to use = a “dial” frequency offset for the speed-changer but I = didn’t solve the problem as the results of any changes to the slow = WSPR parameters  take too long to appear! I suspect it may be a = “safety” feature in the WSPR upload function to prevent = non-amateur reports being sent to the database?

 

73 Terry XZ/GW0EZY

 

 

 

Yesterday I = finally got WSPR 2.11 working in IQ-mode with the FiFi-SDR on MF. = Today I changed back to LF (which is 0.1355 MHz dial and 2000 Hz BFO = here) and got fine decodes, but no uploads, with a persistant error = message "frequency changed no upload of spots". Tried all = sorts of different settings (which is time consuming) but didn't succeed = - anyone out there who has seen and solved this? Now back to = WSPR 2.0 with same parameters, running = just fine.

 

------=_NextPart_000_003A_01CDAC42.9745DE90--