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 wAHBR76e000798 for ; Sat, 17 Nov 2018 12:27:18 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gNyZB-0002if-46 for rs_out_1@blacksheep.org; Sat, 17 Nov 2018 11:15:09 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gNyZ9-0002iW-Vk for rsgb_lf_group@blacksheep.org; Sat, 17 Nov 2018 11:15:07 +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.91_59-0488984) (envelope-from ) id 1gNyZ4-0005kO-QA for rsgb_lf_group@blacksheep.org; Sat, 17 Nov 2018 11:15:06 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id BDD73160061 for ; Sat, 17 Nov 2018 12:15:00 +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=1542453300; bh=ni7ZOW9iuC8BIGLIH5jCI7WsiDtJwXwmISDP4WQHoQo=; h=Date:From:To:Subject:From; b=FaCzxT8rlMnK8VUtaYYRjvwH4Y1dBbtSgeq6ux9W8B32TQizVvGtKDkO6fbJCXFeE GfpgK2V1Jq875J2H6A8/y/bjJy6UJV9dlxcLwrwbScZ29an8LT/4GqpnlXu9fmP+W9 SwPXBH5oP5j+ZYOy3/+EO6tPqQZfFlt+aMslAqMQisZkfoQhOMt9FKzHaNT1Hup2pB sTYKI3iCrqXJtS37IjpsgzM4JgIz76lEaqyzeilJ0ME1biWhgGQ+5BWFHryjHda+F0 OGz5ZBg96yX9FDq8iR+qBEsTtkXNv6nenSXmnyFqZLQQ4UlcVDwzxHFcT8NNPpEujg ZQDWxOsLheLuA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 42xsvS1Mrfz6tmG for ; Sat, 17 Nov 2018 12:15:00 +0100 (CET) Message-ID: <5BEFF833.8080100@posteo.de> Date: Sat, 17 Nov 2018 12:14:59 +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: <818091004.1158892.1542301019212.ref@mail.yahoo.com> <818091004.1158892.1542301019212@mail.yahoo.com> In-Reply-To: X-Spam-Score: -2.3 (--) 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 @@CONTACT_ADDRESS@@ for details. Content preview: There were a number of active WSPR-15 stations on LF last night and this morning, up to now, including N1BUG getting TA decodes. Well done. I see most stations are reporting with times stamps xx:15 and xx:45 for messages which began at xx:00 and xx:30. So the 'old' WSPR-X program seems to be used by them. Who of them uses the latest wsprd [...] Content analysis details: (-2.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [185.67.36.65 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: ca106b06b6ccff7e79a253db5c71bd8f Subject: Re: LF: Re: WSPR-15 Content-Type: multipart/alternative; boundary="------------080405000601000104040701" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.8 required=5.0 tests=HTML_30_40,HTML_MESSAGE 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 This is a multi-part message in MIME format. --------------080405000601000104040701 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit There were a number of active WSPR-15 stations on LF last night and this morning, up to now, including N1BUG getting TA decodes. Well done. I see most stations are reporting with times stamps xx:15 and xx:45 for messages which began at xx:00 and xx:30. So the 'old' WSPR-X program seems to be used by them. Who of them uses the latest wsprd.exe and the latest dlls together with the old GUI, as suggested by Domenico? If this method actually works for everyone, then it may be easier to set up for most OMs, so all the necessary files could be packed into a zip file and made available for everyone... 73, Stefan Am 15.11.2018 19:59, schrieb Domenico IZ7SLZ: > Hi LF, > > I want suggest a further way to try WSPR-15 with latest improvement of > the WSJT-X vers. 2.0.0. > > WSJT-X uses the program wsprd.exe to decode wspr-2. This program has > also wspr-15 capability. So i have taken wsprd.exe dated 10/11/2018 > included in WSJT-X bin folder and putted in the WSPR-X v0.9r3058 > directory that i hold in my radio pc since years. > > Some dll's need also to be copied in the same way (i did this in the > past, so i'm not sure which files are necessary, but any error's > message explains which library is necessary !) > > So the program WSPR-X is now running with a new version of wsprd.exe > and seems stable. I can operate WSPR-15. > > By the way, my radio PC is an old PC with WinXp, so i don't know if > this old program (WSPR-X) should work on 64 bit pc. > Also i don't know if this program is longer available in the net. > > Maybe this advice can be useful for operators working with similar > conditions of mine. > 73, Domenico IZ7SLZ > > > > > > > On Thu, 15 Nov 2018 at 18:00, Markus Vester > wrote: > > Hi Stefan, > > here is an attempt for a wspr-15 to wspr-2 receive converter which > should also work under 64-bit Windows versions. Operation is > similar to the old wspr-8 and -32 utilities > http://df6nm.bplaced.net/wspr/slowWSPR.zip > which also contains a description worth reading. The "waitraster" > program has been replaced by a DOS loop based on the %time% variable. > > To run the attached script, you will need to rename it from .txt > to .bat. Then download DL4YHF's sound utilities from > http://www.qsl.net/dl4yhf/soundutl/sndutl_e.zip > and the little sleep utility > http://df6nm.bplaced.net/VLF/fec_tests/sleep.zip > > The speeded-up audio should be routed from sndoutpt to WSJT-X > using a virtual audio cable, e.g. VAC or VB-Cable from Vincent Burel > https://www.vb-audio.com/Cable/ > This needs to be selected as the default audio output device, as > well as the WSJT-X input device. > > Note that > - reported frequencies will be translated from 137600-137625 to > 137400-137600 Hz, > - reported timestamps will be 15 or 16 minutes late, > - reported SNR will be 9 dB too good. > > I have to admit that the script hasn't been tested yet, so there > is no guarantee that it will work at all. If I was to do this > again, I'd probably not go down the speeded-up audio route, but > rather make a script which calls wsprd.exe directly. > > Good luck, > Markus (DF6NM) > > > > -----Ursprüngliche Mitteilung----- > Von: DK7FC > > An: rsgb_lf_group > > Verschickt: Do, 15. Nov. 2018 11:26 > Betreff: Re: LF: Re: WSPR-15 > > Hi Markus, > > Congrats to last nights successes! > > Well, since WSPR-15 is certainly the better mode for LF DX, and > the WSPR team is not interested in LF, will you find the > motivation to release an updated version of your utilities that > enable 64-bit users to receive WSPR-15 using the latest WSPR-2 > decoder? > > 73, Stefan > > > > Am 15.11.2018 00:49, schrieb Markus Vester: >> > maybe they don't work on 64 bit machines? >> >> yes that is the problem. These "tools" are just a simple DOS >> script. All the real work is done by the audio utilities from >> Wolfgang DL4YHF, which are running fine as ever. But my little >> "waitraster.exe" utility, which did nothing but hold the script >> until the beginning of a desired minute, will no longer work >> under Win-64. >> >> Best 73, >> Markus >> >> -----Ursprüngliche Mitteilung----- >> Von: N1BUG >> An: rsgb_lf_group >> >> Verschickt: Mi, 14. Nov. 2018 23:03 >> Betreff: Re: LF: Re: WSPR-15 >> >> I am interested in this too, but if I recall there was a reason I >> didn't install those tools. I can't remember now... maybe they don't >> work on 64 bit machines? If that was it, I am out of luck. >> >> My WSPR2/WSPR15 transmitting tests last season showed that WSPR15 >> was much better than WSPR2... even though most WSPR2 listeners were >> using the new improved decoder and WSPR15 listeners were using the >> old WSPR-X. >> >> 73, >> Paul >> >> >> On 11/14/18 4:09 PM, jrusgrove@comcast.net >> wrote: >> > Stefan >> > >> > Vague memories ... the tools, if they still exist, would be on >> an old computer that's not so easy to >> > resurrect. >> > >> > Yes, it seems the current WSPR2 decoder is much improved. Think >> your time might be better spent on >> > that mode since there are already many listeners. It would be >> interesting to see how far west into >> > the US you could be decoded on a good night. Just my opinion ;~) . >> > >> > Jay W1VD >> > >> > >> > ----- Original Message ----- >> > From: "DK7FC" > > >> > To: > > >> > Sent: Wednesday, November 14, 2018 1:51 PM >> > Subject: LF: WSPR-15 >> > >> > >> >> Jay, LF, >> >> >> >> I already have the next idea, maybe for tomorrow? ;-) >> >> >> >> You remember the early days before K1JT released WSPR-15. >> >> Markus developed the slow-WSPR tools and we (you, as the DX RX >> station ) tried WSPR-8 and even >> >> WSPR-30 successfully. >> >> >> >> Using Markus tools, the slowly transmitted WSPR (with accurate >> FSK spacing) was accelerated >> >> replayed in the next time slot and then fed to the normal >> WSPR-2 decoder, beeing connected to the >> >> database. >> >> >> >> Meanwhile the WSPR-2 decoder performance seems to have much >> improved. So, it may be interesting to >> >> try the 'old' tool of Markus together with the latest WSPR-2 >> decoder. >> >> >> >> What do you think? Do you still have the config files and so on? >> >> >> >> Worth a try? >> >> >> >> 73, Stefan >> >> >> >> PS: 137.620 kHz is right in the WSPR-15 defined slot. I think >> this is why my coil is resonant >> >> there ;-) >> --------------080405000601000104040701 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit There were a number of active WSPR-15 stations on LF last night and this morning, up to now, including N1BUG getting TA decodes. Well done.

I see most stations are reporting with times stamps xx:15 and xx:45 for messages which began at xx:00 and xx:30. So the 'old' WSPR-X program seems to be used by them.
Who of them uses the latest wsprd.exe and the latest dlls together with the old GUI, as suggested by Domenico?
If this method actually works for everyone, then it may be easier to set up for most OMs, so all the necessary files could be packed into a zip file and made available for everyone...

73, Stefan

Am 15.11.2018 19:59, schrieb Domenico IZ7SLZ:
Hi LF,

I want suggest a further way to try WSPR-15 with latest improvement of the WSJT-X vers. 2.0.0.

WSJT-X uses the program wsprd.exe to decode wspr-2. This program has also wspr-15 capability. So i have taken wsprd.exe dated 10/11/2018 included in WSJT-X bin folder and putted in the  WSPR-X v0.9r3058 directory that i hold in my radio pc since years.

Some dll's need also to be copied in the same way (i did this in the past, so i'm not sure which files are necessary, but any error's message explains which library is necessary !)

So the program WSPR-X is now running with a new version of wsprd.exe and seems stable. I can operate WSPR-15.

By the way, my radio PC is an old PC with WinXp,  so i don't know if this old program (WSPR-X) should work on 64 bit pc.
Also i don't know if this program is longer available in the net.

Maybe this advice can be useful for operators working with similar conditions of mine.
73, Domenico IZ7SLZ






On Thu, 15 Nov 2018 at 18:00, Markus Vester <markusvester@aol.com> wrote:
Hi Stefan,

here is an attempt for a wspr-15 to wspr-2 receive converter which should also work under 64-bit Windows versions. Operation is similar to the old wspr-8 and -32 utilities
http://df6nm.bplaced.net/wspr/slowWSPR.zip
which also contains a description worth reading. The "waitraster" program has been replaced by a DOS loop based on the %time% variable.

To run the attached script, you will need to rename it from .txt to .bat. Then download DL4YHF's sound utilities from
http://www.qsl.net/dl4yhf/soundutl/sndutl_e.zip
and the little sleep utility
http://df6nm.bplaced.net/VLF/fec_tests/sleep.zip

The speeded-up audio should be routed from sndoutpt to WSJT-X using a virtual audio cable, e.g. VAC or VB-Cable from Vincent Burel
https://www.vb-audio.com/Cable/
This needs to be selected as the default audio output device, as well as the WSJT-X input device.

Note that
- reported frequencies will be translated from 137600-137625 to 137400-137600 Hz,
- reported timestamps will be 15 or 16 minutes late,
- reported SNR will be 9 dB too good.

I have to admit that the script hasn't been tested yet, so there is no guarantee that it will work at all. If I was to do this again, I'd probably not go down the speeded-up audio route, but rather make a script which calls wsprd.exe directly.

Good luck,
Markus (DF6NM)



-----Ursprüngliche Mitteilung-----
Von: DK7FC <selberdenken@posteo.de>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Do, 15. Nov. 2018 11:26
Betreff: Re: LF: Re: WSPR-15

Hi Markus,

Congrats to last nights successes!

Well, since WSPR-15 is certainly the better mode for LF DX, and the WSPR team is not interested in LF, will you find the motivation to release an updated version of your utilities that enable 64-bit users to receive WSPR-15 using the latest WSPR-2 decoder?

73, Stefan



Am 15.11.2018 00:49, schrieb Markus Vester:
> maybe they don't work on 64 bit machines?

yes that is the problem. These "tools" are just a simple DOS script. All the real work is done by the audio utilities from Wolfgang DL4YHF, which are running fine as ever. But my little "waitraster.exe" utility, which did nothing but hold the script until the beginning of a desired minute, will no longer work under Win-64.

Best 73,
Markus

-----Ursprüngliche Mitteilung-----
Von: N1BUG <paul@n1bug.com>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Mi, 14. Nov. 2018 23:03
Betreff: Re: LF: Re: WSPR-15

I am interested in this too, but if I recall there was a reason I
didn't install those tools. I can't remember now... maybe they don't
work on 64 bit machines? If that was it, I am out of luck.

My WSPR2/WSPR15 transmitting tests last season showed that WSPR15
was much better than WSPR2... even though most WSPR2 listeners were
using the new improved decoder and WSPR15 listeners were using the
old WSPR-X.

73,
Paul


On 11/14/18 4:09 PM, jrusgrove@comcast.net wrote:
> Stefan
>
> Vague memories ... the tools, if they still exist, would be on an old computer that's not so easy to
> resurrect.
>
> Yes, it seems the current WSPR2 decoder is much improved. Think your time might be better spent on
> that mode since there are already many listeners. It would be interesting to see how far west into
> the US you could be decoded on a good night. Just my opinion ;~) .
>
> Jay W1VD
>
>
> ----- Original Message -----
> From: "DK7FC" <selberdenken@posteo.de>
> To: <rsgb_lf_group@blacksheep.org>
> Sent: Wednesday, November 14, 2018 1:51 PM
> Subject: LF: WSPR-15
>
>
>> Jay, LF,
>>
>> I already have the next idea, maybe for tomorrow? ;-)
>>
>> You remember the early days before K1JT released WSPR-15.
>> Markus developed the slow-WSPR tools and we (you, as the DX RX station ) tried WSPR-8 and even
>> WSPR-30 successfully.
>>
>> Using Markus tools, the slowly transmitted WSPR (with accurate FSK spacing) was accelerated
>> replayed in the next time slot and then fed to the normal WSPR-2 decoder, beeing connected to the
>> database.
>>
>> Meanwhile the WSPR-2 decoder performance seems to have much improved. So, it may be interesting to
>> try the 'old' tool of Markus together with the latest WSPR-2 decoder.
>>
>> What do you think? Do you still have the config files and so on?
>>
>> Worth a try?
>>
>> 73, Stefan
>>
>> PS: 137.620 kHz is right in the WSPR-15 defined slot. I think this is why my coil is resonant
>> there ;-)

--------------080405000601000104040701--