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 wA9MUn8o005872 for ; Fri, 9 Nov 2018 23:30:56 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gLFCN-0008SW-0b for rs_out_1@blacksheep.org; Fri, 09 Nov 2018 22:24:19 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gLFA7-0008SL-DS for rsgb_lf_group@blacksheep.org; Fri, 09 Nov 2018 22:21:59 +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 1gLFA3-0003bK-H3 for rsgb_lf_group@blacksheep.org; Fri, 09 Nov 2018 22:21:58 +0000 X-KULeuven-Envelope-From: rik.strobbe@kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: 9418A120009.A0CF2 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 9418A120009 for ; Fri, 9 Nov 2018 23:21:49 +0100 (CET) Received: from ICTS-S-EXMBX5.luna.kuleuven.be (icts-s-exmbx5.luna.kuleuven.be [10.112.11.13]) (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 85EB540B4; Fri, 9 Nov 2018 23:21:49 +0100 (CET) Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX5.luna.kuleuven.be (10.112.11.13) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 9 Nov 2018 23:21:48 +0100 Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 9 Nov 2018 23:21:49 +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; Fri, 9 Nov 2018 23:21:49 +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: SlowJT9: 1st QSO and 2nd bug found Thread-Index: AQHUeHgj8WW+xbidN0KcPoFG+wCAaw== Date: Fri, 9 Nov 2018 22:21:49 +0000 Message-ID: <1541802108924.75066@kuleuven.be> References: <1541712573053.31739@kuleuven.be> <0a5402bd-72b3-f9d7-0eeb-52897ff2a4d4@n1bug.com> <1541715141849.85703@kuleuven.be>,,<1541789098516.95370@kuleuven.be> In-Reply-To: <1541789098516.95370@kuleuven.be> 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: Dear all, I just completed a JT9-2 QSO with Marco, DD7PC: 2141 -11 0.1 1104 2 OR7T DD7PC JN49 2145 -10 0.1 1106 2 OR7T DD7PC JN49 2153 -16 0.0 1105 2 OR7T DD7PC R-13 2157 -12 0.0 1105 2 OR7T DD7PC 73 2201 -16 0.1 1106 2 UFB RIK [...] 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 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: bb13d668bd6c56d236c8970bb5dcbf33 Subject: LF: SlowJT9: 1st QSO and 2nd bug found Content-Type: multipart/alternative; boundary="_000_154180210892475066kuleuvenbe_" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.2 required=5.0 tests=HTML_70_80,HTML_MESSAGE, LINES_OF_YELLING,LINES_OF_YELLING_2 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 --_000_154180210892475066kuleuvenbe_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all, I just completed a JT9-2 QSO with Marco, DD7PC: 2141 -11 0.1 1104 2 OR7T DD7PC JN49 2145 -10 0.1 1106 2 OR7T DD7PC JN49 2153 -16 0.0 1105 2 OR7T DD7PC R-13 2157 -12 0.0 1105 2 OR7T DD7PC 73 2201 -16 0.1 1106 2 UFB RIK During this QSO I discovered a 2nd bug: As can be seen above the time (UTC) is given at odd minutes (eg. Marco's 21= :40 - 21-42 transmission is reported 2141). This because the time is taken = at the moment of decode. For JT9(-1) this is not an issue, because decoding is in the same minute as= the start of transmission, but for JT9-2 and JT9-5 it is because it result= s in a wrong calculation of the cycle (1st or 2nd). As the wrong cycle is g= iven SlowJT9 will transmit in at the same cycle as the station you received= , very inconvenient! I will fix this big after the weekend (sorry, to many other obligations on = Saturday and Sunday). For the time being the workaround is rather easy: if you get a decode you w= ant to reply to (by double clicking on the call) just change the cycle manu= ally (click once on the "TX 1st cycle" checkbox). The good thing is you hav= e plenty of time to do so as there are 20 seconds between the end of a tran= smission and the start of the next cycle. To end with a positive note: during Marco's 2152-2154 transmission there wa= s very deep QSB and his signal dissapeared from the waterfall display for a= lmost 1 minute. But despite that still a good decode, just some dB weaker. ?73, Rik ON7YD - OR7T --_000_154180210892475066kuleuvenbe_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Dear all,


I just completed a JT9-2 QSO with Marco, DD7PC:


2141 -11  0.1 1104 2  OR7T DD7PC JN49       <= br> 2145 -10  0.1 1106 2  OR7T DD7PC JN49       <= br> 2153 -16  0.0 1105 2  OR7T DD7PC R-13       <= br> 2157 -12  0.0 1105 2  OR7T DD7PC 73        &n= bsp;
2201 -16  0.1 1106 2  UFB RIK
               

During this QSO I discovered a 2nd bug: 

As can be seen above the time (UTC) is given at odd minutes (eg. Marco's= 21:40 - 21-42 transmission is reported 2141). This because the time is tak= en at the moment of decode. 


For JT9(-1) this is not an issue, because decoding is in the same minute= as the start of transmission, but for JT9-2 and JT9-5 it is because it res= ults in a wrong calculation of the cycle (1st or 2nd). As the wrong cycle i= s given SlowJT9 will transmit in at the same cycle as the station you received, very inconvenient!


I will fix this big after the weekend (sorry, to many other obligations = on Saturday and Sunday).

For the time being the workaround is rather easy: if you get a deco= de you want to reply to (by double clicking on the call) just change t= he cycle manually (click once on the "TX 1st cycle" checkbox= ). The good thing is you have plenty of time to do so as there are 20 seconds between the end of a transmission and the start of th= e next cycle. 


To end with a positive note: during Marco's 2152-2154 transmission there= was very deep QSB and his signal dissapeared from the waterfall displ= ay for almost 1 minute. But despite that still a good decode, just some dB = weaker.


​73, Rik  ON7YD - OR7T


--_000_154180210892475066kuleuvenbe_--