Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dc02.r1000.mx.aol.com (Internet Inbound) with ESMTP id ADFBB38000115; Sat, 17 Nov 2012 08:17:24 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TZiGH-0003i6-KS for rs_out_1@blacksheep.org; Sat, 17 Nov 2012 13:16:41 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TZiGH-0003hx-3D for rsgb_lf_group@blacksheep.org; Sat, 17 Nov 2012 13:16:41 +0000 Received: from imr-da04.mx.aol.com ([205.188.105.146]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TZiGE-0001lq-Hh for rsgb_lf_group@blacksheep.org; Sat, 17 Nov 2012 13:16:39 +0000 Received: from mtaomg-da03.r1000.mx.aol.com (mtaomg-da03.r1000.mx.aol.com [172.29.51.139]) by imr-da04.mx.aol.com (8.14.1/8.14.1) with ESMTP id qAHDGVSk020486 for ; Sat, 17 Nov 2012 08:16:31 -0500 Received: from core-dfd004c.r1000.mail.aol.com (core-dfd004.r1000.mail.aol.com [172.29.55.79]) by mtaomg-da03.r1000.mx.aol.com (OMAG/Core Interface) with ESMTP id DBCB0E000088 for ; Sat, 17 Nov 2012 08:16:30 -0500 (EST) References: <50A6A3E1.2040705@princeton.edu> To: rsgb_lf_group@blacksheep.org In-Reply-To: <50A6A3E1.2040705@princeton.edu> X-MB-Message-Source: WebUI MIME-Version: 1.0 From: Markus Vester X-MB-Message-Type: User X-Mailer: Webmail 37185-BASIC Received: from 77.191.153.66 by webmail-m078.sysops.aol.com (64.12.141.36) with HTTP (WebMailUI); Sat, 17 Nov 2012 08:16:30 -0500 Message-Id: <8CF92DCE46211F5-18F8-1F55E@webmail-m078.sysops.aol.com> X-Originating-IP: [77.191.153.66] Date: Sat, 17 Nov 2012 08:16:30 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20110426; t=1353158191; bh=IP6n8RVB6xyh6GK9GPLZK/fTqj2fYRAirPkZYNYTXRE=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=ympp6T4+GZgkEyIxApA3OjxiDih16npBnJfjvRZY77ghFCeoqdkwpzKc0n5Q2yued U1VsAa1PcJCzmdSPmU+/pryH5T5rkBBn5zPSnIqnzJThkgNkXDGL8gQ1KQLHDLS7dH dVQuh5LP+RKEYAYmz/Wz/d+TmrNTaytXz91NAcTE= X-AOL-SCOLL-SCORE: 0:2:463567584:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: -0.1 (/) 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: Hi Joe,  my fault... initially I didn't have the NTP software running. When I started it in the middle of the QSO it corrected a 1.5 second clock error. This unintended experiment confirms that JT9 v0.4 is indeed much more robust than prior versions.  Many thanks for this great piece of work!  Best 73, Markus (DF6NM) [...] Content analysis details: (-0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [205.188.105.146 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.1 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: 52d17ee6003fa6763aae891a69410baf Subject: Re: Testing JT9-1 on LF: Content-Type: multipart/alternative; boundary="--------MB_8CF92DCE46B9779_18F8_70C00_webmail-m078.sysops.aol.com" 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_FONTCOLOR_UNKNOWN, 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-SCOLL-AUTHENTICATION: mtain-dc02.r1000.mx.aol.com ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d408250a78e6474a1 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ----------MB_8CF92DCE46B9779_18F8_70C00_webmail-m078.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Hi Joe, =C2=A0 my fault... initially I didn't have=C2=A0the NTP software running. When=C2= =A0I started it=C2=A0in the middle of the QSO it corrected a 1.5 second clo= ck error. This unintended experiment confirms that JT9 v0.4=C2=A0is indeed = much more robust than prior versions. =C2=A0 Many thanks for this great piece of work! =C2=A0 Best 73,=20 Markus (DF6NM) -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Joe Taylor <joe@Princeton.EDU> An: rsgb_lf_group <rsgb_lf_group@blacksheep.org> Verschickt: Fr, 16 Nov 2012 8:37 pm Betreff: Re: Testing JT9-1 on LF: Hi Markus, Stefan, and all,=20 =20 It appears that you have things working reasonably well in JT9-1. Here =20 are the decodes Markus received from Stefan:=20 =20 UTC Sync dB DT Freq Drift Message=20 ----------------------------------------------------=20 1916 10 4 1.4 1940. 0.0 DF6NM DK7FC -03=20 1918 10 -2 1.5 1940. 0.0 DF6NM DK7FC -03=20 1920 10 -3 1.4 1940. 0.0 HURRAAAAAAAAA=20 1922 10 -4 1.4 1940. 0.0 HR 30W TX PWR=20 1924 10 -2 1.5 1940. 0.0 MENSCH MARKUS=20 1926 10 0 1.5 1940. 0.0 PSE AGN RPRT=20 1928 10 1 1.5 1940. 0.0 PSE AGN RPRT=20 1930 5 4 1.5 1940. 0.0 UR -3...+5DB=20 1932 10 -9 1.6 1940. 0.0 NW 5W TX PWR=20 1934 1 -6 1.5 1940. 0.0 HALLO MAX 4TS=20 1936 10 11 1.6 1940. 0.0 NUR80 CPI=20 1938 10 3 -1.3 1945. 0.0=20 1940 10 4 -0.1 1940. 0.0 SPITZEN SACHE=20 1942 10 9 -0.0 1940. 0.0 YOU HAVE A CA=20 1944 10 -3 0.0 1940. 0.0 UR -7...+5DB=20 1946 10 16 0.0 1940. 0.0 1943 AGN PSE=20 1948 10 18 -0.0 1940. 0.0 1943 AGN PSE=20 1950 10 12 0.0 1940. 0.0 OK73NM FC SK=20 1952 10 6 0.1 1940. 0.0 CIAO MARKUS55=20 1954 2 -37 0.0 1918. 0.0=20 =20 What happened between the transmissions at 1936 and 1940? The measured =20 clock offset DT changed from about +1.5 s to nearly zero. (Note that =20 +1.5 s is an unusually large offset, possibly indicating a problem. In =20 general, with good NTP synchronization at both ends, DT should be nearly = =20 constant and in the range +/- 1 s.)=20 =20 --- Joe, K1JT=20 ----------MB_8CF92DCE46B9779_18F8_70C00_webmail-m078.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
Hi Joe,
 
my fault..= . initially I didn't have the NTP software running. When I starte= d it in the middle of the QSO it corrected a 1.5 second clock error. T= his unintended experiment confirms that JT9 v0.4 is indeed much more r= obust than prior versions.
 
Many thank= s for this great piece of work!
 
Best 73, <= /div>
Markus (DF= 6NM)


-----Urspr=C3=BCngliche Mitteilung-----
Von: Joe Taylor <joe@Princeton.EDU>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Fr, 16 Nov 2012 8:37 pm
Betreff: Re: Testing JT9-1 on LF:


Hi Markus, Stefan, and all, 

It appears that you have things working reasonably well in JT9-1. Here are the decodes Markus received from Stefan:

UTC Sync dB DT Freq Drift Message
----------------------------------------------------
1916 10 4 1.4 1940. 0.0 DF6NM DK7FC -03
1918 10 -2 1.5 1940. 0.0 DF6NM DK7FC -03
1920 10 -3 1.4 1940. 0.0 HURRAAAAAAAAA
1922 10 -4 1.4 1940. 0.0 HR 30W TX PWR
1924 10 -2 1.5 1940. 0.0 MENSCH MARKUS
1926 10 0 1.5 1940. 0.0 PSE AGN RPRT
1928 10 1 1.5 1940. 0.0 PSE AGN RPRT
1930 5 4 1.5 1940. 0.0 UR -3...+5DB
1932 10 -9 1.6 1940. 0.0 NW 5W TX PWR
1934 1 -6 1.5 1940. 0.0 HALLO MAX 4TS
1936 10 11 1.6 1940. 0.0 NUR80 CPI
1938 10 3 -1.3 1945. 0.0
1940 10 4 -0.1 1940. 0.0 SPITZEN SACHE
1942 10 9 -0.0 1940. 0.0 YOU HAVE A CA
1944 10 -3 0.0 1940. 0.0 UR -7...+5DB
1946 10 16 0.0 1940. 0.0 1943 AGN PSE
1948 10 18 -0.0 1940. 0.0 1943 AGN PSE
1950 10 12 0.0 1940. 0.0 OK73NM FC SK
1952 10 6 0.1 1940. 0.0 CIAO MARKUS55
1954 2 -37 0.0 1918. 0.0

What happened between the transmissions at 1936 and 1940? The measured clock offset DT changed from about +1.5 s to nearly zero. (Note that
+1.5 s is an unusually large offset, possibly indicating a problem. In general, with good NTP synchronization at both ends, DT should be nearly <= br> constant and in the range +/- 1 s.)

--- Joe, K1JT


----------MB_8CF92DCE46B9779_18F8_70C00_webmail-m078.sysops.aol.com--