From: Rik Strobbe <rik.strobbe@kuleuven.be>
To: "600MRG@mailman.qth.net" <600MRG@mailman.qth.net>,
        "rsgb_lf_group@blacksheep.org" <rsgb_lf_group@blacksheep.org>
Thread-Topic: MF JT9-2 report
Thread-Index: AQHUeoHpEHqF4lWtk0efxB9V/GWCoaVMFv73
Date: Mon, 12 Nov 2018 13:02:26 +0000
Message-ID: <1542027746735.33850@kuleuven.be>
References: <0ddf61c2-de83-aeef-f929-a87b698f560c@n1bug.com>
In-Reply-To: <0ddf61c2-de83-aeef-f929-a87b698f560c@n1bug.com>
Accept-Language: nl-BE, en-GB, en-US
Content-Language: nl-BE
MIME-Version: 1.0
Subject: LF: Re: MF JT9-2 report
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Content-Transfer-Encoding: 8bit

Hello Paul,

currently you have to subtract 3dB for JT9-2 and 7dB for JT9-5 to get the "true" SNR.
A new version of SlowJT9, with correct reports and the cycle bug fixed, will be uploaded later today.

Regarding the drift: keep in mind that in the JT9-2 -> JT9 conversion process frequencies are doubled, so any drift also will inevitably be doubled in that process.

About the crash: what was the content of the decoded.txt file? Maybe that will give me a clue what happened.
I have SlowJT9 (in JT9-2 mode) running since 9 Nov 20 UTC and it was still running this morning (12 Nov 6 UTC). It is running side by side with WSJT-X and Google Chrome, no other apps.
I must admit that I haven't paid much attention to intercepting errors so far, another item to add to my to-do list.

73, Rik  ON7YD - OR7T

________________________________________
Van: owner-rsgb_lf_group@blacksheep.org <owner-rsgb_lf_group@blacksheep.org> namens N1BUG <paul@n1bug.com>
Verzonden: maandag 12 november 2018 13:15
Aan: 600MRG@mailman.qth.net; rsgb_lf_group@blacksheep.org
Onderwerp: LF: MF JT9-2 report

I decoded 4 stations on JT9-2 last night: KU4XR, N2END, WB4JWM,
K5DNL. KU4XR was visible many times on the waterfall without decodes
but he did have drift varying from 3 Hz / period to 8 Hz / period. I
never saw any decodes reported below -24 SNR, which if I understand
correctly is really -27. This is no better than JT9-1 but may be
just a matter of not enough data collected, no really weak signals
during the test period.

Let's keep the tests going! I need to see some weaker signals to
test the mode. As soon as I can get out to the antenna site to
install the variometer and transformer, I will join in for some
transmitting and QSOs.

This morning I tried to check for additional overnight decodes but I
found the program had exited (crashed) sometime during the night. I
looked in the program folder and found a decoded.txt file with just
one line in it. I guess that was the last decode before the crash?

73,
Paul N1BUG