Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-df04.r1000.mx.aol.com (Internet Inbound) with ESMTP id C07F038000100; Thu, 22 Nov 2012 16:19:02 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Tbe9z-0007s7-6z for rs_out_1@blacksheep.org; Thu, 22 Nov 2012 21:18:11 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Tbe9y-0007ry-MH for rsgb_lf_group@blacksheep.org; Thu, 22 Nov 2012 21:18:10 +0000 Received: from imr-ma04.mx.aol.com ([64.12.206.42]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1Tbe9w-00021H-Dp for rsgb_lf_group@blacksheep.org; Thu, 22 Nov 2012 21:18:09 +0000 Received: from mtaout-mb03.r1000.mx.aol.com (mtaout-mb03.r1000.mx.aol.com [172.29.41.67]) by imr-ma04.mx.aol.com (8.14.1/8.14.1) with ESMTP id qAMLHhZf008444 for ; Thu, 22 Nov 2012 16:17:43 -0500 Received: from White (nrbg-4dbe6c34.pool.mediaWays.net [77.190.108.52]) by mtaout-mb03.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 47AA6E0000A8 for ; Thu, 22 Nov 2012 16:17:42 -0500 (EST) Message-ID: <32170B9A68124B478A79DB8E907611B5@White> From: "Markus Vester" To: References: <50AE3388.6040503@iup.uni-heidelberg.de> <50AE3FBB.2010202@iup.uni-heidelberg.de> <98F81F1DE60D4ADBA02F08350A669EAC@White> <50AE9318.2010705@iup.uni-heidelberg.de> Date: Thu, 22 Nov 2012 22:17:39 +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=1353619063; bh=5WJJ1u628LSrYWys7aTsV8oApOBWtZsNYTVN7hnx0gc=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=L4NPLOUWNHER3li4AxDIl7KoU1raqf/0gi2EyQkgqRy6AucUHfBIjWWsfIpjFlmm5 Gg2Cv23YF9FKRsVu6OEqv1pz8xYoFi65FyZTjZmlEk+hidjLHpmspRSdODD1IMxdQR l63YN9gKuduqZOfRmEKrWut1yv+EBCkqpwddE34Q= X-AOL-SCOLL-SCORE: 0:2:500897920: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: ... sorry Stefan, I think there was a clock error on my side, which might also have caused the missing decodes. Have restarted the NTP software again. I'm using wsjtx v0.4 r2746 here which runs nice and smooth. [...] 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.42 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: 72f3686d3f5e154c987315e88c667a5f Subject: Re: LF: JT9-10 on 137.42 kHz Content-Type: multipart/alternative; boundary="----=_NextPart_000_0055_01CDC8FF.2F0DED70" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50,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-df04.r1000.mx.aol.com ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d40d850ae96c54367 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_0055_01CDC8FF.2F0DED70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ... sorry Stefan, I think there was a clock error on my side, which = might also have caused the missing decodes. Have restarted the NTP = software again. I'm using wsjtx v0.4 r2746 here which runs nice and = smooth. 73, Markus From: Stefan Sch=E4fer=20 Sent: Thursday, November 22, 2012 10:03 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: JT9-10 on 137.42 kHz Thanks Markus,=20 What do you think about the -2.2 time delay? I don't know where it may = come from. The program is driving the transmit converter directly, you = know. I was running a very old version of WSJT-9 and updated to the latest one = a few minutes ago. However i think that should make no difference on the = transmitter side. Is there any noticable difference now? 73, Stefan Am 22.11.2012 21:45, schrieb Markus Vester:=20 Hi Stefan, got the first decode 10 minutes after starting the WSJT-X monitor: 2010 10 14 -2.2 1919.89 0.00 DK7FC JN49IK but for some reason nil from your latest over at 20:30. Your signal = strength now appears to be at its usual level. BTW I don't think it was Joe's intention that we should use below 1.1 = kHz audio. I guess he just didn't yet get around to implement an option = to shift the waterfall display range, with us keeping him so busy on = the decoder... Best wishes, Markus (DF6NM) From: Stefan Sch=E4fer=20 Sent: Thursday, November 22, 2012 4:07 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: JT9-10 on 137.42 kHz Oh, i just remember and see that JT9-10 is intended to run on = 1000...1100 Hz audio frequencies. However the bandplan says that = digimodes are at 137.4...137.6 kHz.=20 So one has to change to 5 FFT bins/pixel to reach 1420 Hz anyway or = simply choose 136.4 kHz "dial" and set the center frequency to 1020 Hz. 73, Stefan/DK7FC ------=_NextPart_000_0055_01CDC8FF.2F0DED70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
... sorry Stefan, I think there = was a clock=20 error on my side, which might also have caused the missing decodes. = Have=20 restarted the NTP software again. I'm using=20 wsjtx v0.4 r2746 here which runs nice and smooth.
 
73, Markus

From: Stefan = Sch=E4fer
Sent: Thursday, November 22, 2012 10:03 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: Re: LF: JT9-10 on 137.42 kHz

Thanks Markus,

What do you think about the -2.2 = time=20 delay? I don't know where it may come from. The program is driving the = transmit=20 converter directly, you know.

I was running a very old version of = WSJT-9=20 and updated to the latest one a few minutes ago. However i think that = should=20 make no difference on the transmitter side.

Is there any = noticable=20 difference now?

73, Stefan


Am 22.11.2012 21:45, = schrieb Markus=20 Vester:=20
Hi Stefan,
 
got the first decode 10 minutes after = starting=20 the WSJT-X monitor:
 
2010 10 14 -2.2 1919.89 0.00 DK7FC=20 JN49IK
 
but for some reason nil from = your=20 latest over at 20:30. Your signal strength now appears to be at = its usual=20 level.
 
BTW I don't think it was Joe's intention = that we=20 should use below 1.1 kHz audio. I guess he just didn't yet get = around to=20 implement an option to shift the waterfall display = range,  with=20 us keeping him so busy on the decoder...   Best wishes, Markus (DF6NM)

Sent: Thursday, November 22, 2012 4:07 PM
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: JT9-10 on 137.42 kHz

Oh, i just remember and see that JT9-10 is intended to = run on=20 1000...1100 Hz audio frequencies. However the bandplan says that = digimodes are=20 at 137.4...137.6 kHz.
So one has to change to 5 FFT bins/pixel to = reach=20 1420 Hz anyway or simply choose 136.4 kHz "dial" and set the center = frequency=20 to 1020 Hz.

73, Stefan/DK7FC
------=_NextPart_000_0055_01CDC8FF.2F0DED70--