Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-de01.r1000.mx.aol.com (Internet Inbound) with ESMTP id B2865380000D9; Tue, 30 Oct 2012 13:25:22 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TTFWw-0002Z1-Re for rs_out_1@blacksheep.org; Tue, 30 Oct 2012 17:23:10 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TTFWw-0002Ys-Ar for rsgb_lf_group@blacksheep.org; Tue, 30 Oct 2012 17:23:10 +0000 Received: from out1.ip02ir2.opaltelecom.net ([62.24.128.238]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TTFWt-0001if-JX for rsgb_lf_group@blacksheep.org; Tue, 30 Oct 2012 17:23:09 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArcBAF0MkFACZMOe/2dsb2JhbAANN4t3uwsBAQEBA0lACwkLBAklDwJGEwgBAbFKgymQN4t3G4ZCA5V1kzE X-IronPort-AV: E=Sophos;i="4.80,680,1344207600"; d="scan'208,217";a="407993236" Received: from host-2-100-195-158.as13285.net (HELO [192.168.2.3]) ([2.100.195.158]) by out1.ip02ir2.opaltelecom.net with ESMTP; 30 Oct 2012 17:23:06 +0000 Message-ID: <50900CFA.20906@psk31.plus.com> Date: Tue, 30 Oct 2012 17:23:06 +0000 From: g3zjo User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <8D468B5D9DCA4B6D90ED557E68BB66AF@White> <508F157E.9040108@iup.uni-heidelberg.de> <508FAB27.2050909@psk31.plus.com> <508FD677.2050807@iup.uni-heidelberg.de> In-Reply-To: <508FD677.2050807@iup.uni-heidelberg.de> X-Spam-Score: 0.0 (/) 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 Stefan 02r2702 seems to have cured the nasty rattle at COM Port release here. Non de-code checks done here today on JT9-2, it looks to me that your TX / RX need to be stable over the 2min period to less than +- 0.78Hz, pretty critical for rigs. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: fb42d311bf65eb51bbb8124890b4f977 Subject: Re: LF: JT9-1 and 2, echoes, waterfall Content-Type: multipart/alternative; boundary="------------000300080304020907010502" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=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-sid: 3039ac1d40c950900d821bcd X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. --------------000300080304020907010502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi Stefan 02r2702 seems to have cured the nasty rattle at COM Port release here. Non de-code checks done here today on JT9-2, it looks to me that your TX / RX need to be stable over the 2min period to less than +- 0.78Hz, pretty critical for rigs. Eddie G3ZJO On 30/10/2012 13:30, Stefan Schäfer wrote: > Hi Eddie, LF, > > Am 30.10.2012 11:25, schrieb g3zjo: >> Hi Stefan >> >> I found the lack / loss of decodes annoying, one cause was slight >> frequency drift in my transverter, WSPR is not effected but JT9-2 is. >> I feel there were other periods of unexplained non de-codes too. >> >> Was it you who mentioned the burst at the end of the signal. I was >> hearing a tuneful diddle at the end of G3XIZ transmission, I hear a >> burst of distorted rattle on my own signal. >> >> Eddie > > No, it was DF6NM who mentioned the burst at the end but i saw it as > well. It was part of the end of my signal. > > With the new version things became a bit better. The initial crashes > didn't happen any more for me. As i assume, this is probably due to > the decoder that has to much work to do in a 1 minute period when the > range is set to center+-50 Hz and if the CPU power is relatively low > or other task have to be performed to the same time. When reducing the > range to e.g. +-10 Hz there was no problem on my XP PC (512 MB RAM) > (no decodes though). On my Win7 PC (32 bit, 4GB RAM) there were no > problems and i got successful decodes. > > Probably there have to be some improvements on the decoder. We all > confirmed that these problems are not present in WSPR, so Joe may > already know what the culprit is. > > It's one of the first releases of the software so we obviously have to > be patient for some more time. > > *On request of DU1GM i will transmit JT9-30, beginning arround 15 UTC > on 137.44 kHz (+- a few Hz), full power!* > > 73, Stefan/DK7FC > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2221 / Virus Database: 2441/5362 - Release Date: 10/29/12 > --------------000300080304020907010502 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Stefan

02r2702 seems to have cured the nasty rattle at COM Port release here.

Non de-code checks done here today on JT9-2, it looks to me that your TX / RX need to be stable over the 2min period to less than +- 0.78Hz, pretty critical for rigs.

Eddie G3ZJO

On 30/10/2012 13:30, Stefan Schäfer wrote:
Hi Eddie, LF,

Am 30.10.2012 11:25, schrieb g3zjo:
Hi Stefan

I found the lack / loss of decodes annoying, one cause was slight frequency drift in my transverter, WSPR is not effected but JT9-2 is.
I feel there were other periods of unexplained non de-codes too.

Was it you who mentioned the burst at the end of the signal. I was hearing a tuneful diddle at the end of G3XIZ transmission, I hear a burst of distorted rattle on my own signal.

Eddie

No, it was DF6NM who mentioned the burst at the end but i saw it as well. It was part of the end of my signal.

With the new version things became a bit better. The initial crashes didn't happen any more for me. As i assume, this is probably due to the decoder that has to much work to do in a 1 minute period when the range is set to center+-50 Hz and if the CPU power is relatively low or other task have to be performed to the same time. When reducing the range to e.g. +-10 Hz there was no problem on my XP PC (512 MB RAM)  (no decodes though). On my Win7 PC (32 bit, 4GB RAM) there were no problems and i got successful decodes.

Probably there have to be some improvements on the decoder. We all confirmed that these problems are not present in WSPR, so Joe may already know what the culprit is.

It's one of the first releases of the software so we obviously have to be patient for some more time.

On request of DU1GM i will transmit JT9-30, beginning arround 15 UTC on 137.44 kHz (+- a few Hz), full power!

73, Stefan/DK7FC

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5362 - Release Date: 10/29/12


--------------000300080304020907010502--