Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mj05.r1000.mx.aol.com (Internet Inbound) with ESMTP id ADB073800008D; Sat, 10 Nov 2012 12:26:17 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TXEnu-0005nr-1U for rs_out_1@blacksheep.org; Sat, 10 Nov 2012 17:25:10 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TXEnt-0005ni-IG for rsgb_lf_group@blacksheep.org; Sat, 10 Nov 2012 17:25:09 +0000 Received: from imr-ma02.mx.aol.com ([64.12.206.40]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TXEnr-0000fn-2Q for rsgb_lf_group@blacksheep.org; Sat, 10 Nov 2012 17:25:08 +0000 Received: from mtaout-mb05.r1000.mx.aol.com (mtaout-mb05.r1000.mx.aol.com [172.29.41.69]) by imr-ma02.mx.aol.com (Outbound Mail Relay) with ESMTP id DA16A1C000070 for ; Sat, 10 Nov 2012 12:25:04 -0500 (EST) Received: from White (nrbg-4d0577d3.pool.mediaWays.net [77.5.119.211]) by mtaout-mb05.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id A5FF0E0000F9 for ; Sat, 10 Nov 2012 12:25:03 -0500 (EST) Message-ID: <8DC8508D438740DCB519C2F86936961D@White> From: "Markus Vester" To: References: <509E6577.27035.10C1B7F@mike.dennison.ntlworld.com> Date: Sat, 10 Nov 2012 18:25:02 +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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1352568304; bh=1HGeyqdJtfcFpkl+4P74SheKKS+8uTWWd3bp+voaCgs=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=W6pr6T3ceZF5ybjqX8AF9gigxduETR1gxFZq7rGpaMisE7RcZX+1ygsagqHsvFAV2 Pf+sbZoCYz1RfAN8kNZiXUFbKuhb3x+n9UECX5Ab9/1WSJ8XCa7NsLJwYnHLDkTazv zGejcsWmzcovPxC0uhciJxNTLjM8smUN/yvoJmbY= X-AOL-SCOLL-SCORE: 0:2:334597504:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: -0.4 (/) 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: Mike, looking at JT9-1 and -2, transmissions appear to start one second after (not before) the minute tick, and end about 10 seconds before the next one. I find that this is also correctly displayed on the waterfall, ie. with a small empty gap between the minute marker and the start of the carrier, and a larger gap at the end. [...] Content analysis details: (-0.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [64.12.206.40 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: b4085bc26841e34d79a2f3beb8f287b1 Subject: Re: LF: WSJT-X timing Content-Type: multipart/alternative; boundary="----=_NextPart_000_0044_01CDBF70.B2DB20C0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, 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-global-disposition: G X-AOL-SCOLL-AUTHENTICATION: mtain-mj05.r1000.mx.aol.com ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d7b99509e8e39601a X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0044_01CDBF70.B2DB20C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mike, looking at JT9-1 and -2, transmissions appear to start one second after = (not before) the minute tick, and end about 10 seconds before the next = one. I find that this is also correctly displayed on the waterfall, ie. = with a small empty gap between the minute marker and the start of the = carrier, and a larger gap at the end. I have no explanation for your observation that incoming signals seem to = start before the minute marker. Did you see this on a local test signal = from a second program instance? Or from a remote station, whose clock = might have been running ahead? Best 73, Markus (DF6NM) From: Mike Dennison=20 Sent: Saturday, November 10, 2012 3:32 PM To: rsgb_lf_group@blacksheep.org=20 Cc: rsgb_lf_group@yahoogroups.co.uk=20 Subject: LF: WSJT-X timing I notice by zooming in on the waterfall display (Pixel =3D 1) that,=20 despite my computer clock being synchronised with a time server, the=20 transmissions seem to start about one second before the waterfall=20 line indicating the start of the time period, and end a few seconds=20 before the next line. Do others see this, or is there space before and after the=20 transmission on your waterfall? Is this a clue to my unreliable=20 reception (ie that my receive setup is slightly behind the=20 transmitted signals)? MIke, G3XDV ------=_NextPart_000_0044_01CDBF70.B2DB20C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Mike,
 
looking at JT9-1 and = -2, transmissions=20 appear to start one second after (not before) the minute = tick, and end=20 about 10 seconds before the next one. I find that this is also = correctly=20 displayed on the waterfall, ie. with a small empty gap between the = minute=20 marker and the start of the carrier, and a larger gap at the = end.
 
I have no explanation for your = observation=20 that incoming signals seem to start before the minute = marker. Did=20 you see this on a local test signal from a second program = instance? Or=20 from a remote station, whose clock might have been running=20 ahead?
 
Best 73,
Markus (DF6NM)
 
 
Sent: Saturday, November 10, 2012 3:32 PM
Subject: LF: WSJT-X timing

I notice by=20 zooming in on the waterfall display (Pixel =3D 1) that,
despite my = computer=20 clock being synchronised with a time server, the
transmissions seem = to start=20 about one second before the waterfall
line indicating the start of = the time=20 period, and end a few seconds
before the next line.

Do others = see=20 this, or is there space before and after the
transmission on your = waterfall?=20 Is this a clue to my unreliable
reception (ie that my receive setup = is=20 slightly behind the
transmitted signals)?

MIke,=20 G3XDV

------=_NextPart_000_0044_01CDBF70.B2DB20C0--