Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id wACL3kPw028670 for ; Mon, 12 Nov 2018 22:03:54 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gMJHZ-00042D-3j for rs_out_1@blacksheep.org; Mon, 12 Nov 2018 20:58:05 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gMJFX-000420-MS for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 20:56:00 +0000 Received: from rhcavuit02.kulnet.kuleuven.be ([2a02:2c40:0:c0::25:130]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91_59-0488984) (envelope-from ) id 1gMJFV-0002kj-Fz for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 20:55:58 +0000 X-KULeuven-Envelope-From: rik.strobbe@kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: 7A6D712000E.A3BCF X-KULeuven-Information: Katholieke Universiteit Leuven Received: from icts-p-smtps-1.cc.kuleuven.be (icts-p-smtps-1e.kulnet.kuleuven.be [134.58.240.33]) by rhcavuit02.kulnet.kuleuven.be (Postfix) with ESMTP id 7A6D712000E for ; Mon, 12 Nov 2018 21:55:55 +0100 (CET) Received: from ICTS-S-EXMBX25.luna.kuleuven.be (icts-s-exmbx25.luna.kuleuven.be [10.112.11.60]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by icts-p-smtps-1.cc.kuleuven.be (Postfix) with ESMTPS id 73B2C40B4; Mon, 12 Nov 2018 21:55:55 +0100 (CET) Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX25.luna.kuleuven.be (10.112.11.60) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 12 Nov 2018 21:55:55 +0100 Received: from ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a]) by ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a%25]) with mapi id 15.00.1395.000; Mon, 12 Nov 2018 21:55:55 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" , "rsgb_lf_group@yahoogroups.co.uk" Thread-Topic: LF: SlowJT9 v0.9.02 Thread-Index: AQHUeqCWAdNbBbcg7k6CVkM+dmLa26VMXf0AgAArkkL///iVAIAAFYJO Date: Mon, 12 Nov 2018 20:55:55 +0000 Message-ID: <1542056154975.15419@kuleuven.be> References: <0ddf61c2-de83-aeef-f929-a87b698f560c@n1bug.com> <1542028810096.76526@kuleuven.be> <1542038390327.50768@kuleuven.be> <1542052074466.76606@kuleuven.be>,<17488f94-c94d-a83f-f268-1fd335872b35@n1bug.com> In-Reply-To: <17488f94-c94d-a83f-f268-1fd335872b35@n1bug.com> Accept-Language: nl-BE, en-GB, en-US Content-Language: nl-BE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.112.50.1] MIME-Version: 1.0 X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Hello Eric, Paul, as Paul says the original JT9-2 and JT9-5 symbol lenghts are probably optimized for "good use" of the 2 minute and 5 minute cycle. JT9(-1) has a exact symbol length of 6912/12000 = 0.576 . For 85 symobls this makes a transmission length of 48,96s (starts at 1 second after the full minute, stops at 50 seconds after the full minute). [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [2a02:2c40:0:c0:0:0:25:130 listed in] [list.dnswl.org] -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 5934134de2d93cab1d5fc440b67de82f Subject: Re: LF: SlowJT9 v0.9.02 Content-Type: text/plain; charset="iso-8859-1" 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=none 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by klubnl.pl id wACL3kPw028670 Hello Eric, Paul, as Paul says the original JT9-2 and JT9-5 symbol lenghts are probably optimized for "good use" of the 2 minute and 5 minute cycle. JT9(-1) has a exact symbol length of 6912/12000 = 0.576 . For 85 symobls this makes a transmission length of 48,96s (starts at 1 second after the full minute, stops at 50 seconds after the full minute). If the symbol length for JT9-2 is exactly 1.28 s (15360/12000 ?) the transmission will take 108.8s or 1m48.8s. Assuming a JT9-2 transmission started at 1s after any even minute it will stop 50 seconds after every odd minute, exactly (within a few tenths of a second) at the same time as a JT9(-1) transmission end. For JT9-5 and a symbol length of 3.41s a transmission wil take 289.85s or 4m49.85s. Thus it will end at almost the same moment as a JT9(-1) transmission and every second time at the same moment as a JT9-1 and JT9-2 transmission. In all 3 cases there is about 10s "response time", what makes sense. Instead of using a scaling factor 2 and 5 (as for now) it is possible to use non-integer scaling factors of +/- 2.2 (for JT9-2) and +/- 5.9 (for JT9-5). It will just make the averaging a bit more complicating, but that shoudn't be a real problem. I am more worried about my plan to allow SlowJT9 to decode JT9(-1), JT9-2 and JT9-5 (seconded by Paul), as in that case up to 3 decodes will have to happen at the same time. So unless there is a good reason to fall back to the original symbol lengths I am not so keen to do that. 73, Rik ON7YD - OR7T ________________________________________ Van: owner-rsgb_lf_group@blacksheep.org namens N1BUG Verzonden: maandag 12 november 2018 21:12 Aan: rsgb_lf_group@blacksheep.org; rsgb_lf_group@yahoogroups.co.uk Onderwerp: Re: LF: SlowJT9 v0.9.02 Eric brings up a good point. Forget what I said the other day about beaconing with a U3S to be received by SlowJT9. I believe that won't work because the U3S uses the original JT9-2, -5, -10, -30 symbol lengths which are different. Probably (a guess) in the original, symbol lengths were chosen to fill as much of the period as possible while leaving enough time at the end for decoding. I would further guess there were specific decoders for each submode, or one decoder whose parameters could be modified for the current submode. 73, Paul N1BUG On 11/12/18 2:47 PM, Rik Strobbe wrote: > Hello Eric, > > > yes, a scale factor of 2 and 5 is used. > > I hadn't any information about the old JT9-2 and JT9-5 modes and > those scale factors seemed the most straightforward to me and > make the conversion to JT9 easy. > > > 73, Rik ON7YD - OR7T > > > > ________________________________ Van: > owner-rsgb_lf_group@blacksheep.org > namens Eric NO3M > Verzonden: maandag 12 november 2018 19:03 Aan: > rsgb_lf_group@blacksheep.org; rsgb_lf_group@yahoogroups.co.uk > Onderwerp: Re: LF: SlowJT9 v0.9.02 > > Rik > > SlowJT9 won't run in Wine in Linux, nothing particularly useful > was output on the command-line. I tried using an old version of > WSJTX (0.95 r 3278) but seems there is some protocol > incompatibility. > > The original JT9 submodes specs give: > > Symbol Length: > > JT9-1 0.58s JT9-2 1.28s JT9-5 3.41s > > Is your program using a 2x and 5x scale factor for JT9-2 and > JT9-5 respectively? If that is the case, the symbol lengths will > be different than the original specs and old versions of WSJTX > will not be compatible. > > 73 Eric NO3M > > > On 11/12/18 10:59 AM, Rik Strobbe wrote: > > I just uploaded a new beta version of SlowJT9: > > > v0.9.02 [12 Nov 2018] Bug fixes: - Non fatal bug that that > corrupted the cycle calculation fixed. Changes: - Calculation of > the report (dB) corrected for JT9-2 and JT9-5. - Beta version > message changed (ignore option added). > > 73, Rik ON7YD - OR7T ?