Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-df01.r1000.mx.aol.com (Internet Inbound) with ESMTP id 18E0A38000087; Fri, 8 Mar 2013 09:09:53 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UDxXm-0002Sv-TS for rs_out_1@blacksheep.org; Fri, 08 Mar 2013 13:41:06 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UDxXm-0002Sm-E3 for rsgb_lf_group@blacksheep.org; Fri, 08 Mar 2013 13:41:06 +0000 Received: from out1.ip03ir2.opaltelecom.net ([62.24.128.239]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1UDxXk-0000yx-Rj for rsgb_lf_group@blacksheep.org; Fri, 08 Mar 2013 13:41:05 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtwCAGLpOVFcGSx4/2dsb2JhbAANLgi9WYQShFCDX2UYFhgDAgECAVgIAQGwFJJtjVeBUoMqA5ZTk3w X-IronPort-AV: E=Sophos;i="4.84,807,1355097600"; d="scan'208";a="416713074" Received: from host-92-25-44-120.as13285.net (HELO [127.0.0.1]) ([92.25.44.120]) by out1.ip03ir2.opaltelecom.net with ESMTP; 08 Mar 2013 13:40:43 +0000 Message-ID: <5139EA5A.6020303@psk31.plus.com> Date: Fri, 08 Mar 2013 13:40:42 +0000 From: g3zjo User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org X-Antivirus: avast! (VPS 130308-0, 08/03/2013), Outbound message X-Antivirus-Status: Clean X-Spam-Score: 1.5 (+) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: LF WSJT-X ver.0.5, r3038 fine on JT9-2 but JT9-5 problems found. My test of ver 0.5, r3038 of WSJT-X on JT9-2 was fully successful, several hours of continuous operation gave virtually faultless decodes on Local Test. Activity on the mode on 630m is virtually non existent but DG3LV was good enough to dedicate a little time to produce report of LA5VNA and G3ZJO signals, no signals were received at LA5VNA or G3ZJO. [...] Content analysis details: (1.5 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.5 COMPENSATION "Compensation" X-Scan-Signature: 5f132ffce194fb93f2267a462d849f2b Subject: LF: WSJT-X ver.0.5, r3038 Test Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 x-aol-global-disposition: G x-aol-sid: 3039ac1d40d55139f1302592 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none LF WSJT-X ver.0.5, r3038 fine on JT9-2 but JT9-5 problems found. My test of ver 0.5, r3038 of WSJT-X on JT9-2 was fully successful, several hours of continuous operation gave virtually faultless decodes on Local Test. Activity on the mode on 630m is virtually non existent but DG3LV was good enough to dedicate a little time to produce report of LA5VNA and G3ZJO signals, no signals were received at LA5VNA or G3ZJO. Some Reports this evening from DG3LV JO53GV: Mode JT9-2 (WSJT-X r3038) 1850 3 -26 0.2 1358.3 0 CQ LA5VNA JO59 1906 1 -27 0.6 1358.4 0 CQ LA5VNA JO59 2052 1 -27 0.2 1364.3 -1 G3ZJO IO92 2104 2 -26 -0.2 1363.7 0 G3ZJO IO92 2156 2 -27 0.2 1365.3 0 G3ZJO IO92 2200 3 -24 0.0 1365.2 0 G3ZJO IO92 Compensation for slight drift has obviously been improved. Test of Mode JT9-5 (WSJT-X r3038) Five sessions of JT9-5 produced no Local decodes. Slight drift is visible on the waterfall using my Kenwood TS870 clearly this cannot be coped with in the decoder. After three transmissions the PTT locked up in TX mode with no tones output, the only way to release the PTT was to close WSJT-X. Using the Transmit First selection to trigger the PTT, this locked up condition could be re produced regularly with Mode JT-5 set, extensive tests with Mode JT-2 set has never shown a problem. The Kenwood TS870 stability is better than many transceivers, particularly the small portable multi band rigs popular for driving Transverters. I use the same pure Com1 Comport PTT interface for all digi mode software. I see some use for JT9-1 and JT9-2 but most likely will abandon this Software again. Eddie G3ZJO