Envelope-to: dave@picks.force9.co.uk Delivery-date: Sun, 24 Apr 2005 20:26:50 +0100 Received: from ptb-spamcore02.plus.net ([192.168.71.3]) by ptb-mxcore04.plus.net with esmtp (PlusNet MXCore v1.0) id 1DPmkk-00032W-48 for dave@picks.force9.co.uk; Sun, 24 Apr 2005 20:26:50 +0100 Received: from mailnull by ptb-spamcore02.plus.net with spamcore-l-b (Exim 4.32; FreeBSD) id 1DPmmv-0008NZ-U6 for dave@picks.force9.co.uk; Sun, 24 Apr 2005 20:29:05 +0100 Received: from [192.168.101.71] (helo=pih-mxcore05.plus.net) by ptb-spamcore02.plus.net with esmtp (Exim 4.32; FreeBSD) id 1DPmmv-0008NW-R2 for dave@picks.force9.co.uk; Sun, 24 Apr 2005 20:29:05 +0100 Received: from post.thorcom.com ([193.82.116.20]) by pih-mxcore05.plus.net with esmtp (PlusNet MXCore v1.0) id 1DPmim-0002pT-H9 for dave@picks.force9.co.uk; Sun, 24 Apr 2005 20:24:48 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1DPmiN-0005eE-KD for rs_out_1@blacksheep.org; Sun, 24 Apr 2005 20:24:23 +0100 Received: from [193.82.116.30] (helo=relay.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1DPmiN-0005e5-2K for rsgb_lf_group@blacksheep.org; Sun, 24 Apr 2005 20:24:23 +0100 Received: from mout2.freenet.de ([194.97.50.155] ident=exim) by relay.thorcom.net with esmtp (Exim 4.43) id 1DPmiL-00083G-KD for rsgb_lf_group@blacksheep.org; Sun, 24 Apr 2005 20:24:23 +0100 Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout2.freenet.de with esmtpa (Exim 4.51) id 1DPmi8-0000hj-AH for rsgb_lf_group@blacksheep.org; Sun, 24 Apr 2005 21:24:08 +0200 Received: from pd902e786.dip.t-dialin.net ([217.2.231.134] helo=[192.168.0.200]) by mx3.freenet.de with esmtpsa (ID dl4yhf@freenet.de) (TLSv1:AES256-SHA:256) (Exim 4.51 #8) id 1DPmi7-0000HE-H1 for rsgb_lf_group@blacksheep.org; Sun, 24 Apr 2005 21:24:08 +0200 Message-ID: <426BF29E.7080301@freenet.de> Date: Sun, 24 Apr 2005 21:25:18 +0200 From: Wolf DL4YHF User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: In-Reply-To: X-SPF-Result: relay.thorcom.net: 194.97.50.155 is neither permitted nor denied by domain of freenet.de X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=failed,none Subject: Re: LF: Wolf qso 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 (v3.00) Hello Dave, Sorry for the setup problems - indeed, the calibration of sample rate and frequency tuning is essential, and I am still looking for an easier way to tune. The waterfall (and spectrum graph) will be pretty useless when it comes to the really weak signals, since WOLF's decoding potential exceeds the waterfall's weak-signal displaying capability by far (especially when looking at a BPSK signal). There is a tuning mode in the program which can produce a thin line on the receiver's sreen. It must be exactly on the place which is marked with the larger tick in the middle of the frequency scale (phew, I should mention that in a manual... but no time yet). About the crash: What compilation date (and time ! ) does the "About"-box show ? I recently uploaded a new version in which a bug has been fixed, which caused a crashed after quickly switching from RX to TX and back to RX (the latest version was compiled today, April 24, which was used by DF6NM and DF0WD). But before downloading that version, wait for a few days until the next one is out. I will add the option for a waterfall with selectable frequency solution, which would simplify tuning if another station (with precise TX) transmits the "Tune Tone" for a couple of minutes. About the same message being decoded more than once, even if there is no signal: Strong signals "accumulate" (or integrate) in a memory, causing the same message to be displayed more than once. Since the message text is spread all over the 960 bit message frame (which takes 96 seconds to send at 10 bit/sec), the coding scheme makes it possible to decode a strong signal which was only 24 seconds long. To try this "off-line" with a reasonably fast PC (say >= 300 MHz), you can let up to three instances of the WOLF GUI on the same machine, each of them using its own configuration. With an AC97 audio system (which most PCs use these days), let one instance transmit, and the other receive. If your soundcard plays an ugly game with you, it uses *different* sampling rates for in- and output (this can happen, but fortunately not too often). If it happens, enter different sample rates in the "Transmit" and "Receive" fields on the config tab. A digital frequency counter connected to the soundcard output, and the "Tune Tone" mode will quickly reveal such problems. After calibrating the sampling rate (until 800.00 Hz get out as 800.00 Hz), you have a stable generator to test the input ("Receive") sampling rate. Note: Some digital frequency counters can be switched into "Period measurement" mode, which gives a much higher resolution than the "frequency measurement" mode, even at 10 second gate time. About the WOLF-test today: Before calling Markus in WOLF BPSK after the Formula 1 race today, I noticed a signal on the waterfall which I couldn't decode - was that you Dave ? Now back to the workbench... 73, Wolf DL4YHF ( Wolf = Wolfgang, that's me; WOLF = BPSK by KK7KA, that's not me - all the flowers to Stewart please ! :-) Dave Pick schrieb: >Marcus and group (especially Wolf) > >Thanks for your patience whilst I struggled to get Wolf GUI set up! >I had literally just unzipped it and ran it into the TX and I saw your >signal come back on the waterfall but couldn't make it decode for ages... >When I got the calibration sorted I could then decode fine (but the signal >was audible so it SHOULD have worked!). I had two copies running one on >Win98 and one on Win 2K and they both kept crashing after about 10mins, then >I couldn't make the TX start on the right frequency unless I re-started the >program several times. >Also I had the RX constantly repeating the last message it had received, >which was my TX message from the other computer, even though I was receiving >Marcus on the waterfall... Most odd. >Perhaps I need more practice?! >Thanks Wolf for making Stewart's mode accessible to the dim operators like >myself. It shows a lot of potential but maybe it's not quite ready as a QSO >mode yet? (Or maybe I'm not...?) > >73 and thanks both again > >Dave G3YXM. > > > > > > >