Return-Path: X-Spam-DCC: paranoid 1356; Body=1 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=-1.9 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_40_50,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 u3UDTkZY006913 for ; Sat, 30 Apr 2016 15:29:46 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1awUqO-000575-Nt for rs_out_1@blacksheep.org; Sat, 30 Apr 2016 14:22:00 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1awUqM-00056w-NG for rsgb_lf_group@blacksheep.org; Sat, 30 Apr 2016 14:21:58 +0100 Received: from smtp08.smtpout.orange.fr ([80.12.242.130] helo=smtp.smtpout.orange.fr) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1awUqK-0002ML-R4 for rsgb_lf_group@blacksheep.org; Sat, 30 Apr 2016 14:21:57 +0100 Received: from pcn5 ([86.208.26.248]) by mwinf5d43 with ME id odMv1s0055MArty03dMvPf; Sat, 30 Apr 2016 15:21:55 +0200 X-ME-Helo: pcn5 X-ME-Date: Sat, 30 Apr 2016 15:21:55 +0200 X-ME-IP: 86.208.26.248 Message-ID: <3C51D8558FB347FE8D6158E4E672B702@pcn5> From: "F6CNI - Andy - JN19QB" To: "RSGB LF Group" Date: Sat, 30 Apr 2016 15:21:55 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Antivirus: avast! (VPS 160430-0, 30/04/2016), Outbound message X-Antivirus-Status: Not-Tested X-Scan-Signature: f1284eec928b6c66f973fc41cf683e42 Subject: LF: Re: WSPR spotting map anomalies Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01D1A2F4.07BECDC0" 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.11 Status: O X-Status: X-Keywords: X-UID: 7948 Ce message est composi et au format MIME. ------=_NextPart_000_000A_01D1A2F4.07BECDC0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable In complement informations about my last mail : a.. Last month, 5 stations had this problem. and now 4 of them = resolved it.=20 b.. GOSLN said he put a wrong transmitting frequency (0.001500) in the = window =E2=80=9Cdial=E2=80=9D using WSPR-X. He was wrong during 3 weeks = and resolved the problem at 2016/04/28 afternoon ;=20 c.. It seems that M0HGU is now the only station sending wrong QRG. To avoid this problem, perhaps the easiest way is to use the CAT mode. = Using the WSJT-X V 1.7.0 is also a good option, because you cannot = change the dial QRG in the main window (you need to go in menu = File/Setting/Frequencies) Sorry my poor English... From: F6CNI - Andy - JN19QB=20 Sent: Saturday, April 30, 2016 12:14 PM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: Re: WSPR spotting map anomalies Hello Eddie. Yes and the problem was coming for the first time about 3 weeks ago. You = can see an example in the join file. All the stations spotted 3 days ago = was active using WSPR on the 40 m band. I sent to Nick M0HGU, 2 messages on his personnal email address (found = on QRZ.com). I displayed him friendly and politely the problem and how to solve it, = but I do not received any answer. 73 de Andy - F6CNI -----Message d'origine-----=20 From: g3zjo=20 Sent: Saturday, April 30, 2016 10:26 AM=20 To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: AW: WSPR spotting map anomalies=20 On 30/04/2016 09:00, Markus Vester wrote: > The database shows the frequency of those spots as 0.0015x MHz (i.e.=20 > audio rather than RF). Yes looks like Uman error, it happened 5 days ago around 20:00 UTC, over = 10,000 Spots all reported in error. I am sure M0HGU would like to know=20 if we / someone can contact him by e-mail. 73 Eddie G3ZJO ------=_NextPart_000_000A_01D1A2F4.07BECDC0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
In complement informations about my last mail :
  • Last month, 5 stations had this problem. and now 4 of them = resolved it.=20
  • GOSLN said he put a wrong transmitting frequency (0.001500) in the = window=20 =E2=80=9Cdial=E2=80=9D using WSPR-X. He was wrong during 3 weeks and = resolved the problem at=20 2016/04/28 afternoon ;=20
  • It seems that M0HGU is now the only station sending wrong = QRG.
To avoid this problem, perhaps the easiest way is to use the CAT = mode.=20 Using the WSJT-X V 1.7.0 is also a good option, because you cannot = change the=20 dial QRG in the main window (you need to go in menu=20 File/Setting/Frequencies)
 
Sorry my poor English...
 
Sent: Saturday, April 30, 2016 12:14 PM
Subject: LF: Re: WSPR spotting map anomalies
 
Hello Eddie.
 
Yes and the problem was coming for the first time about 3 weeks = ago. You=20 can see an example in the join file. All the stations spotted 3 days ago = was=20 active using WSPR on the 40 m band.
 
I sent to Nick M0HGU, 2 = messages on=20 his personnal email address (found on QRZ.com).
 
I displayed him friendly and politely the problem and how to solve = it, but=20 I do not received any answer.
 
73 de Andy - F6CNI
 
 
-----Message d'origine-----
From: g3zjo
Sent: Saturday, April 30, 2016 10:26 AM
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: AW: WSPR spotting map anomalies
 
On 30/04/2016 09:00, Markus Vester wrote:
> The database shows the frequency of those spots as 0.0015x MHz = (i.e.=20
> audio rather than RF).
 
Yes looks like Uman error, it happened 5 days ago around 20:00 UTC, = over=20
10,000 Spots all reported in error. I am sure M0HGU would like to = know=20
if we / someone can contact him by e-mail.
 
73 Eddie G3ZJO
------=_NextPart_000_000A_01D1A2F4.07BECDC0--