Return-Path: Received: (qmail 20313 invoked from network); 9 Apr 2005 02:41:12 -0000 Received: from unknown (HELO ptb-spamcore03.plus.net) (192.168.71.7) by ptb-mailstore02.plus.net with SMTP; 9 Apr 2005 02:41:12 -0000 Received: from Debian-exim by ptb-spamcore03.plus.net with spam-scanned (Exim 4.44) id 1DK5uK-00016P-8s for dave@picks.force9.co.uk; Sat, 09 Apr 2005 03:41:12 +0100 Received: from [192.168.67.2] (helo=ptb-mxcore02.plus.net) by ptb-spamcore03.plus.net with esmtp (Exim 4.44) id 1DK5uK-00016M-7D for dave@picks.force9.co.uk; Sat, 09 Apr 2005 03:41:12 +0100 Received: from post.thorcom.com ([193.82.116.20]) by ptb-mxcore02.plus.net with esmtp (Exim) id 1DK5uK-000Ipd-4s for dave@picks.force9.co.uk; Sat, 09 Apr 2005 02:41:12 +0000 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1DK5tx-0000cS-5b for rs_out_1@blacksheep.org; Sat, 09 Apr 2005 03:40:49 +0100 Received: from [193.82.116.30] (helo=relay.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1DK5tw-0000cJ-LV for rsgb_lf_group@blacksheep.org; Sat, 09 Apr 2005 03:40:48 +0100 Received: from sterling.noc-servers.net ([69.93.216.2]) by relay.thorcom.net with esmtp (Exim 4.43) id 1DK5tu-00023p-TP for rsgb_lf_group@blacksheep.org; Sat, 09 Apr 2005 03:40:48 +0100 Received: from [192.55.122.100] (helo=w2ksn) by sterling.noc-servers.net with esmtpa (Exim 4.50) id 1DK5ts-0007VB-SD for rsgb_lf_group@blacksheep.org; Fri, 08 Apr 2005 22:40:45 -0400 Message-ID: <001301c53cad$a55447e0$1101a8c0@w2ksn> From: "Stewart Nelson" To: rsgb_lf_group@blacksheep.org Date: Fri, 8 Apr 2005 19:41:33 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sterling.noc-servers.net X-AntiAbuse: Original Domain - blacksheep.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - scgroup.com X-SPF-Result: relay.thorcom.net: 69.93.216.2 is neither permitted nor denied by domain of scgroup.com X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=failed,none Subject: LF: WOLF sources Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com 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-Spam-Filtered: by PlusNet SpamCORE (v4.00) Hi Wolf and all, I just posted a copy of the WOLF sources at http://www.scgroup.com/ham/wolf-source.zip This has the complete environment; if you have MS VC++ you should be able to build it right away. Binaries are also included, so you can see if the build gives the same results. The code is simple C, so it should not be hard to build it with Borland or GCC. All the real work is done in wolf.cpp; there are various utility functions in fft.cpp. Although I don't presently have time to write new code, I'd be glad to answer any questions that may come up. In addition to a GUI and real-time operation, here are some features I'd like to (eventually) see: 1. Slow it down! Instead of a raw rate of 10 bps, operation at e.g. 1 or 2 bps would greatly reduce interference to stations operating on nearby frequencies, and permit operation between LORAN lines. A slower format would also be much more tolerant of timing errors, in a future system using synchronized clocks. I believe that reducing the data rate is a simple matter of adjusting some parameters, but there are two problems: a) It's likely that many Tx or Rx would not be phase-stable over the 8 or 16 minutes that a frame would now take. One would need to add a "stability" setting to allow searching for carrier frequency and phase over a selectable fraction of a frame. b) It would be a shame to have to wait 16 minutes for results, even when the incoming signal is strong. One could perform a decode with e.g. 1/4 of a frame, substituting "erasures" for the missing bits. 2. Provide for Tx/Rx bit timing synchronization. This could use GPS or another external source, or simply depend on accurate computer clocks. That should greatly improve sensitivity, by eliminating false reference pattern sync on weak signals. 3. Implement "smart" signal averaging, weighting the incoming message symbols according to the quality of the received reference symbols. That would avoid degradation of data received during good propagation, by noise received during prior poor propagation. Also, when the received reference is "excellent", the decoder could reset, allowing different messages to be sent in each frame. A combination of (2) and (3) should permit operation at "any" SNR, though it would of course take 100 times longer to receive a signal 10 dB weaker. 4. Implement some means of Tx/Rx carrier sync. This probably requires GPS at the Tx end, though it may be possible to use LORAN QRM on receive. First, that would improve LF skywave performance by a few dB. However, on a long-term phase stable path, e.g. VLF or groundwave, it should permit operation at any SNR, taking only 10 times longer to receive a signal 10 dB weaker. If different folks are interested in tackling these topics, perhaps I could act as a coordinator. 73, Stewart KK7KA