Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dk06.r1000.mx.aol.com (Internet Inbound) with ESMTP id 791D83800009A; Sun, 28 Oct 2012 09:52:45 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TSTHe-0002AK-2l for rs_out_1@blacksheep.org; Sun, 28 Oct 2012 13:52:10 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TSTHd-0002AB-Kr for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 13:52:09 +0000 Received: from out1.ip05ir2.opaltelecom.net ([62.24.128.241]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TSTHb-0000ZD-AA for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 13:52:08 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhITAII3jVBOk8jd/2dsb2JhbABEika3DwOBBoEJghkFAQEEAQgBAQMlASMCJgYBAQMFAgEDEQQBAQolFAEEGgYWCAYTCgECAgEBh28KB7sVi3WBLoILgyQDiCSFSokgjyiCbw X-IronPort-AV: E=Sophos;i="4.80,665,1344207600"; d="scan'208";a="397955341" Received: from host-78-147-200-221.as13285.net (HELO xphd97xgq27nyf) ([78.147.200.221]) by out1.ip05ir2.opaltelecom.net with SMTP; 28 Oct 2012 13:52:06 +0000 Message-ID: <005901cdb513$6a2750e0$0501a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <508D2FFF.40700@princeton.edu> <508D3344.9050200@iup.uni-heidelberg.de> Date: Sun, 28 Oct 2012 13:52:04 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 3.8 (+++) 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: Stefan Why is a mapping feature necessary when you can have a real time QSO and get a direct report like most operators do on HF What you are suggesting is a BEACON mode again and QSL via INTERNET. The intention is a QSO mode and get away from Beacon mentality. [...] Content analysis details: (3.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 3.8 AXB_XMAILER_MIMEOLE_OL_024C2 AXB_XMAILER_MIMEOLE_OL_024C2 X-Scan-Signature: 8556389a5ea14fbbf9b9d801ab70c592 Subject: Re: LF: Answers to some JT9 questions Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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: 3039ac1db40a508d38ad6859 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Stefan Why is a mapping feature necessary when you can have a real time QSO and get a direct report like most operators do on HF What you are suggesting is a BEACON mode again and QSL via INTERNET. The intention is a QSO mode and get away from Beacon mentality. de g3kev ----- Original Message ----- From: "Stefan Schäfer" To: Sent: Sunday, October 28, 2012 1:29 PM Subject: Re: LF: Answers to some JT9 questions > Hello Joe, > > Here you are, that's nice :-) > > Thanks for your work and development and quick updates of JT9 for LF/MF > use! Certainly there will be impressive distances covered in JT9 during > this winter season. > > The mapping feature as in WSPR is an important motivation i think, both > for RX and the TX stations! > > I will now prepare for a JT9-30 transmission on 137.43 kHz, running this > until tomorrow 6 UTC. > > 73! Stefan/DK7FC > > Am 28.10.2012 14:15, schrieb Joe Taylor: > > GM/GA all, > > > > 1. Alberto/I2PHD and others have asked whether details of the JT9 > > protocol are described somewhere. At present the only full description > > is the one implicitly contained in the source code, which is openly > > available at http://developer.berlios.de/projects/wsjt/ . In due > > course I will provide a summary document describing the source > > encoding, error-control coding, interleaving and bit-ordering scheme, > > and modulation details. (At this point it's possible that a few of > > these things could still change, depending on user feedback.) > > > > 2. Roger/G3XBM and others asked whether a WSPRnet-like database might > > be made available. Yes, this could be useful, and in principle WSPRnet > > itself could accept reception reports from WSJT-X. I will give some > > thought to adding such a feature, and I'll consider having WSJT-X > > support standard WSPR-format messages such as "WA1ABC FN42 37". I > > should mention, however, that the principal intent of JT9 and WSJT-X > > is to enable 2-way QSOs at MF and LF, with very narrow bandwidths and > > very weak signals. In the longer term, I do not wish that our MF/LF > > frequencies will be used mostly for beacon-like transmissions. > > > > 3. WSJT-X will continue to evolve in coming weeks. The JT9 decoder is > > not yet fully optimized, and other enhancements are in the works, as > > well. Surely there will be bugs in the early program releases: bug > > reports and requests for new features will be most welcome! > > > > -- 73, Joe, K1JT >