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 w1LE94ou013564 for ; Wed, 21 Feb 2018 15:09:05 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eoUzE-0006vf-Oc for rs_out_1@blacksheep.org; Wed, 21 Feb 2018 14:03:08 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eoUzE-0006vW-97 for rsgb_lf_group@blacksheep.org; Wed, 21 Feb 2018 14:03:08 +0000 Received: from mout01.posteo.de ([185.67.36.65]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eoUz6-0002cQ-Bi for rsgb_lf_group@blacksheep.org; Wed, 21 Feb 2018 14:03:07 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id CB30520E0A for ; Wed, 21 Feb 2018 15:02:57 +0100 (CET) X-DKIM-Result: Domain=posteo.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1519221777; bh=beOSswhdeAEjXybCeLA1PVQL7pktQgF5/RuupFcKqIY=; h=Date:From:To:Subject:From; b=LShcEzp48QuooiACVgA/ml0zpGA9OSdKpshVbay/2MmJPcTqhrNgNNC1JqPov7zVi tF31bWQNKylywe9qKz89PJLryLtex+OKRuYY4K+JL8iJktAetYtplg8FG9+nAeAilU PQL1Cqtv11HgauQRDgXUWuTHMnQFk2IBWTLNKQ3Apjk4Onh3gyvsLCtVZ2Iw956M0E 77Ic9NXD58cJ3ZCNeBuPmrwJKpKkjb4r/qDZH9Bd3fGac7QZh0Z9qyWk64hXYV0Sri PqxQos9k5dCgioXYa/PdBrjX5GNw+MM+Y0C2lfoglkyb6hog5tWkF+nokLKD0d4IyU vu8pUu8e1NIKA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3zmfMN2klTz9rxX for ; Wed, 21 Feb 2018 15:02:56 +0100 (CET) Message-ID: <5A8D7C10.5030705@posteo.de> Date: Wed, 21 Feb 2018 15:02:56 +0100 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <5A8C51C3.4030503@posteo.de> In-Reply-To: X-Spam-Score: 0.0 (/) 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: ...i just checked the old emails. It was in 2012. Here is a link to Markus' website which contains the slowWSPR tools, http://df6nm.bplaced.net/wspr/ . It works for TXing and RXing. For TXing you can use the normal software of course. For RXing you can use the latest WSJT-X software set to WSPR-2. You need something like VAC to lead the audio to the input of WSJT-X. It is some years ago that is used the software but there is a readme file. So maybe someone likes to try to use it. Jay/W1VD may add instructions on how to set it up for RXing. I hope the file comes through... [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 61577e2058c0d3bf1737d7de6ed6eb16 Subject: Re: LF: WSPR-15 on 136 KHz Content-Type: text/plain; charset=UTF-8; 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 ...i just checked the old emails. It was in 2012. Here is a link to Markus' website which contains the slowWSPR tools, http://df6nm.bplaced.net/wspr/ . It works for TXing and RXing. For TXing you can use the normal software of course. For RXing you can use the latest WSJT-X software set to WSPR-2. You need something like VAC to lead the audio to the input of WSJT-X. It is some years ago that is used the software but there is a readme file. So maybe someone likes to try to use it. Jay/W1VD may add instructions on how to set it up for RXing. I hope the file comes through... 73, Stefan Am 21.02.2018 09:52, schrieb N1BUG: > Interesting. I didn't know about that. I suppose we need to develop > our own tools from within the LF community as we are too small to > attract attention from without. > > I'm trying Windows 7 compatibility mode with WSPR-X. It has been > running about 10 hours so far and decoding K3RWR every time. > > The rain has stopped so today I can look at my antenna coil and maybe > start transmitting again if the coil is OK. I will start on WSPR-2 > again but might switch to WSPR-15. > > 73, > Paul N1BUG > > > > On 02/20/2018 11:50 AM, DK7FC wrote: >> LF, >> >> Before WSPR-15 came up in 2011, Markus/DF6NM developed a tool which >> can generate and decode WSPR-15 and other WSPR modes. We used WSPR-8 >> (4 times slower, +6 dB) and even WSPR-30 (16x slower, +12 dB). The >> program collects the data from SpectrumLab and replays it faster >> afterwards, and leads the output to a normal WSPR decoder. So this >> fast replayed data can be fed into the new WSJT-X program running in >> WSPR-2 mode. >> I remember positive tests with Jay/W1VD >> >> If someone is interested, i could look into the details again. I >> guess the program is still available. Maybe Markus want's to comment. >> >> 73, Stefan >> >> Am 20.02.2018 17:33, schrieb Alex R7NT: >>> Rob, >>> I believe that WSPR15 is more viable on 136 at low powers (up to 1W >>> ERP) on long QRB (compared with WSPR2) :) >>> It's like comparing OP8 (~WSPR2) and OP32 (~WSPR32). >>> But OP8 died a few years ago on 136 >>> >>> 73! Alex R7NT 136.73.ru >>> >>> 2018-02-20 15:32 GMT+03:00 Rob Renoud >> >: >>> >>> >>> Two T/A spots from Geoff, G0LUJ, last evening on 2200M at >>> -35dB and -37dB show WSPR-15 to be a viable mode on 136 KHz. >>> I will continue nightly WSPR-15 transmissions for the next >>> week or so. >>> >>> Does anyone have an early release of WSJT-X with the slow JT9 >>> modes included? I believe that WSJT-X V. 0.95, r3243 released >>> about 04/2013 may be one release that includes the slow JT9 modes. >>> >>> 73, >>> Rob - K3RWR >