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 x0VM9Xxl007704 for ; Thu, 31 Jan 2019 23:09:34 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gpKRU-0004f4-Rs for rs_out_1@blacksheep.org; Thu, 31 Jan 2019 22:04:16 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gpKRU-0004ev-7H for rsgb_lf_group@blacksheep.org; Thu, 31 Jan 2019 22:04:16 +0000 Received: from rhcavuit03.kulnet.kuleuven.be ([2a02:2c40:0:c0::25:136]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gpKRO-000664-DV for rsgb_lf_group@blacksheep.org; Thu, 31 Jan 2019 22:04:15 +0000 X-KULeuven-Envelope-From: rik.strobbe@kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: 25C94120002.A422C 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 rhcavuit03.kulnet.kuleuven.be (Postfix) with ESMTP id 25C94120002 for ; Thu, 31 Jan 2019 23:04:05 +0100 (CET) Received: from ICTS-S-EXMBX20.luna.kuleuven.be (icts-s-exmbx20.luna.kuleuven.be [10.112.11.55]) (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 0D83140B4; Thu, 31 Jan 2019 23:04:05 +0100 (CET) Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX20.luna.kuleuven.be (10.112.11.55) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 31 Jan 2019 23:04:04 +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; Thu, 31 Jan 2019 23:04:05 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb-lf-group@groups.io" , "rsgb_lf_group@blacksheep.org" , "600MRG@mailman.qth.net" <600MRG@mailman.qth.net> Thread-Topic: [rsgb-lf-group] SlowJT9 update (v0.9.15.0) Thread-Index: AQHUuW6GReIGNCCA4UORsMuWFMRWM6XJx6gAgAAk02Q= Date: Thu, 31 Jan 2019 22:04:05 +0000 Message-ID: <1548972230834.98198@kuleuven.be> References: <1541712573053.31739@kuleuven.be> <1542362144885.30626@kuleuven.be> <1542721669174.9290@kuleuven.be> <1542902405876.64977@kuleuven.be> <1544631368092.16214@kuleuven.be> <1544826336986.15705@kuleuven.be> <1545855021519.36262@kuleuven.be> <1546865627715.6950@kuleuven.be> <1548945782023.57164@kuleuven.be>,<8eccff54-2e93-4f31-67d6-04a3dbf27d25@n1bug.com> In-Reply-To: <8eccff54-2e93-4f31-67d6-04a3dbf27d25@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: -2.3 (--) 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 the administrator of that system for details. Content preview: Hi Paul, all, SlowJT9 vs WSJT-X: as I mentioned it was pure luck that SlowJT9 performed better that night. But as the only reason I can think of is a small timing difference between both it might be worth to time-s [...] Content analysis details: (-2.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [2a02:2c40:0:c0:0:0:25:136 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 7f2e5481aa97b3cbff3d653a1b2ddfbd Subject: LF: Re: [rsgb-lf-group] SlowJT9 update (v0.9.15.0) 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 x0VM9Xxl007704 Hi Paul, all, SlowJT9 vs WSJT-X: as I mentioned it was pure luck that SlowJT9 performed better that night. But as the only reason I can think of is a small timing difference between both it might be worth to time-shift the incoming audio by small steps, then try to decode each step nd take a "best off" as result. Frequency conversion: I will investigate that furher. Anyway, if I implement this it will be optional (can be switched off). For the moment WX is rather bad here, so the antenna is lowered. But in a few days, when the WX permits I would like to try some TA QSO's on 475 kHz using the slower JT9 modes. Any takers at the other side of the pond? I worked Paul, N1BUG and Eric, NO3M, mid February last year. 73, Rik ON7YD - OR7T ________________________________________ Van: rsgb-lf-group@groups.io namens N1BUG Verzonden: donderdag 31 januari 2019 21:43 Aan: rsgb-lf-group@groups.io; rsgb_lf_group@blacksheep.org; 600MRG@mailman.qth.net Onderwerp: Re: [rsgb-lf-group] SlowJT9 update (v0.9.15.0) Hello Rik, all, Two comments, see below. > Interestingly Rik's SlowJT9 which was running in parallel, > managed to decode a couple of more transmissions than WSJT-X." I have seen this work both ways. Sometimes SlowJT9 will decode something WSJT-X does not. Other times WSJT-X will decode something SlowJT9 does not. Usually they are equal. > 2. Add optional internal frequency conversion to allow reception > at higher frequencies I have done some preliminary tests (based > on the code snippet Wolf, DL4YHF, sent me) and it seems to work > fine. But I am not sure that it will be very useful as frequency > conversion will not increase the usable frequeny range, but just > shit it. Eg: now JT9-10 can be received from 100 Hz to 415 Hz > audio. After USB downconversion with a 1 kHz carrier the range > will be 1100 Hz to 1415 Hz. The only reason I can think of to > want frequency conversion is if you use a fixed frequency (ofen > 800Hz) CW filter, so you can fit the JT9-5 or JT9-10 frequency > range into the filter passband. But this downconversion requires > a Hilbert transform (90 degrees all pass filter) that never can > be perfect and this will cause some distortion (in particular at > the lower and of the passband). So before I start the effort to > implement this in SlowJT9 I would like to know if there is an > audience for it. I think there is justification for it on 2200m if it comes without too high cost in lost sensitivity. Some people cannot easily tune antennas down to 136.4 or so. But if we operate at 137.x then listening stations must adjust their receiver because the usual 136.000 'dial' frequency will not allow receiving JT9-5 or JT9-10. This is not the usual setting for most who also want to monitor WSPR or other modes. For pre-arranged QSOs this will not matter, but for calling CQ it is good to operate where we can be heard without special receiver settings. However, if this feature comes with significant loss of decoding sensitivity, then I would vote to stay as we are. 73, Paul N1BUG -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#8560): https://groups.io/g/rsgb-lf-group/message/8560 Mute This Topic: https://groups.io/mt/29606322/1555778 Group Owner: rsgb-lf-group+owner@groups.io Unsubscribe: https://groups.io/g/rsgb-lf-group/leave/3440736/168031436/xyzzy [rik.strobbe@kuleuven.be] -=-=-=-=-=-=-=-=-=-=-=-