Return-Path: X-Spam-DCC: paranoid 1233; 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.2 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_50_60,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 t1ILTrVJ013922 for ; Wed, 18 Feb 2015 22:29:53 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1YOC7q-0005pa-UG for rs_out_1@blacksheep.org; Wed, 18 Feb 2015 21:25:42 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1YOC7q-0005pR-IK for rsgb_lf_group@blacksheep.org; Wed, 18 Feb 2015 21:25:42 +0000 Received: from omr-m1.mx.aol.com ([64.12.224.134]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1YOC7o-0001fn-LE for rsgb_lf_group@blacksheep.org; Wed, 18 Feb 2015 21:25:41 +0000 Received: from mtaout-aao01.mx.aol.com (mtaout-aao01.mx.aol.com [172.27.21.13]) by omr-m1.mx.aol.com (Outbound Mail Relay) with ESMTP id AF2EE3800012E for ; Wed, 18 Feb 2015 16:25:38 -0500 (EST) Received: from White (ipb21bee4a.dynamic.kabel-deutschland.de [178.27.238.74]) by mtaout-aao01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id DB8F938000099 for ; Wed, 18 Feb 2015 16:25:35 -0500 (EST) Message-ID: From: "Markus Vester" To: References: <97CF0B1C-93C3-4667-8AFB-EF3B559FF9AE@iz7pdx.it>, <799A8358-390F-4A95-8B4F-ACF90396344E@iz7pdx.it>, ,<54E2FF75.7175.12D068@roelof.ndb.demon.nl> <7E7DFBB4D102A04DB5ADC88D66628A4A234C4CD6@ICTS-S-MBX1.luna.kuleuven.be> <42D8BC9A2A8A46C79FF84CD152672225@uwePC> <99BCD526551E4B13A520C09453AEF712@uwePC> <170772064B0E4DEDB031E77B175BC796@Clemens0811> <421F1959F2D342BA912EBA839B6CD5FC@uwePC> <2A449761779C4CD9B2DA26915B1391AF@Clemens0811> <54E3A561.6060007@gmx.net> <34041AE6158A41F6A5FD0D941BC0E264@Clemens0811> <0F0E3CDC942D4E5C892E91B5A0ACD5BC@uwePC> <035419E6F8C247F5B9C9C6B64F69392B@Clemens0811> <778BF068A3CC42C59FC5EDD1D898CF17@uwePC> <54E4CA62.30307@gmail.com> Date: Wed, 18 Feb 2015 22:25:34 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1424294738; bh=K18PDjLRRLjKNCEib6wbk/YoFC3j8TlokXI/5JWB8Lc=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=zx287WMk0uQS/8CFeA0dRvz4i0lpfpYvh7Ka1qIhIOHl8E0Q+B4ovzPbwv1jIFjXR d65qIkxLxw/tUw5ek2PKxSEI5Rlge0MEz+jDcRQbV8GIvCYMJxy7Wd46Y2G4YQK06t fJjvTKS18fF2ICs3BCCy2AA47NZn6wE7uAjWVnuE= x-aol-sid: 3039ac1b150d54e5034f7372 X-AOL-IP: 178.27.238.74 X-Scan-Signature: 622b0ca3461797caf37867321c193763 Subject: Re: LF: Re: WSPR 630m Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01D04BC9.CFE4EA60" 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: 2433 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0014_01D04BC9.CFE4EA60 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable If you receive yourself, wspr(x) will decode and display your own = callsign locally, but the spots won't appear in the wsprnet database. = You could circumvent this by modifying your callsign in the wsprx setup = dialog (eg. something like DK1KQ/2), but normally this is not very = useful. BTW those unid dashes on 136.7 kHz actually looked a bit like failed 33% = wspr transmissions, except for wrong frequency, missing modulation, and = slightly short.=20 73, Markus From: DK7FC=20 Sent: Wednesday, February 18, 2015 6:22 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Re: WSPR 630m Hi Uwe, If you can decode other stations, you must of course decode yourselfe as = well. If not, there is either a time- or frequency shift. You will see=20 it in the WSPR-waterfall. As a test, disconnect your RX antenna and look = on your own signal which should be strong enough. It must appear to the=20 right time and frequency band. Maybe you are transmitting 1500 Hz to high? I don't know the Ultimate 3s = but maybe there is the old problem with that "dial" frequency. "dial" is = set to 474.200 kHz. Just try that to be sure... 73, Stefan ... ------=_NextPart_000_0014_01D04BC9.CFE4EA60 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
If you receive yourself, wspr(x) will = decode and=20 display your own callsign locally, but the spots won't appear in = the=20 wsprnet database. You could circumvent this by modifying your = callsign in=20 the wsprx setup dialog (eg. something like DK1KQ/2), but normally this = is not=20 very useful.
 
BTW those unid dashes on 136.7 kHz=20 actually looked a bit like failed 33% wspr transmissions, except = for wrong=20 frequency, missing modulation, and slightly = short. 
 
73, Markus
 

From: DK7FC
Sent: Wednesday, February 18, 2015 6:22 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: Re: LF: Re: WSPR 630m

Hi Uwe,

If you can decode other = stations, you=20 must of course decode yourselfe as
well. If not, there is either a = time- or=20 frequency shift. You will see
it in the WSPR-waterfall. As a test,=20 disconnect your RX antenna and look
on your own signal which should = be=20 strong enough. It must appear to the
right time and frequency = band.
Maybe=20 you are transmitting 1500 Hz to high? I don't know the Ultimate 3s =
but maybe=20 there is the old problem with that "dial" frequency. "dial" is
set = to=20 474.200 kHz. Just try that to be sure...

73, Stefan

... ------=_NextPart_000_0014_01D04BC9.CFE4EA60--