Message-ID: <508FD677.2050807@iup.uni-heidelberg.de>
Date: Tue, 30 Oct 2012 14:30:31 +0100
From: =?ISO-8859-1?Q?Stefan_Sch=E4fer?= <Stefan.Schaefer@iup.uni-heidelberg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <8D468B5D9DCA4B6D90ED557E68BB66AF@White> <508F157E.9040108@iup.uni-heidelberg.de> <508FAB27.2050909@psk31.plus.com>
In-Reply-To: <508FAB27.2050909@psk31.plus.com>
Subject: Re: LF: JT9-1 and 2, echoes, waterfall
Content-Type: multipart/alternative;
 boundary="------------030205040201090201010305"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


This is a multi-part message in MIME format.
--------------030205040201090201010305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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

--------------030205040201090201010305
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Eddie, LF,<br>
<br>
Am 30.10.2012 11:25, schrieb g3zjo:
<blockquote cite="mid:508FAB27.2050909@psk31.plus.com" type="cite">
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
Hi Stefan<br>
  <br>
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.<br>
I feel there were other periods of unexplained non de-codes too.<br>
  <br>
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.<br>
  <br>
Eddie<br>
</blockquote>
<br>
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.<br>
<br>
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)&nbsp; (no decodes
though). On my Win7 PC (32 bit, 4GB RAM) there were no problems and i
got successful decodes.<br>
<br>
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.<br>
<br>
It's one of the first releases of the software so we obviously have to
be patient for some more time.<br>
<br>
<b>On request of DU1GM i will transmit JT9-30, beginning arround 15 UTC
on 137.44 kHz (+- a few Hz), full power!</b><br>
<br>
73, Stefan/DK7FC<br>
</body>
</html>

--------------030205040201090201010305--