Return-Path: X-Spam-DCC: paranoid 1002; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, RATWARE_GECKO_BUILD autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id t4QI722T017139 for ; Tue, 26 May 2015 20:07:02 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1YxJCv-0004YN-94 for rs_out_1@blacksheep.org; Tue, 26 May 2015 19:04:05 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1YxJCu-0004YE-V2 for rsgb_lf_group@blacksheep.org; Tue, 26 May 2015 19:04:04 +0100 Received: from mout.gmx.net ([212.227.17.22]) by relay1.thorcom.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85) (envelope-from ) id 1YxJCt-0002CP-49 for rsgb_lf_group@blacksheep.org; Tue, 26 May 2015 19:04:03 +0100 Received: from [127.0.0.1] ([185.78.62.85]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Ltqmn-1Z5AtI3BO1-011DQF for ; Tue, 26 May 2015 20:04:01 +0200 Message-ID: <5564B58B.8010802@gmx.net> Date: Tue, 26 May 2015 20:03:55 +0200 From: Tobias DG3LV User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <55649E42.3070906@freenet.de> <8D265EC08008761-1BC8-16D9E@webmail-vm124.sysops.aol.com> In-Reply-To: <8D265EC08008761-1BC8-16D9E@webmail-vm124.sysops.aol.com> X-Provags-ID: V03:K0:3kthIzq54P6aGgL3+CpwLO+D9PoGVCB+PLFSeyUFuUJcL02fD+0 iwHug2qSarzpGNrJ3i7R15mIg2h9fQkRdv0XeEekJ/XwGQ7OXfOf60PI5/uFXpXhvTWFFd8 uWWtZ+AaFpvKdDt+2G5y76MY/UZRhDaVBPnYEqZfKL6HEWVOydW3neQrlnnDHg3O7+ObVYq XKHqm1PKtciePJVVjkdDg== X-UI-Out-Filterresults: notjunk:1; X-Scan-Signature: 39d0aa3a8a50eef73e9de70bcfcadb32 Subject: Re: LF: 630M WSPR T/A - WSPR-15? Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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-Scanned-By: MIMEDefang 2.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 3295 Hi Wolf, Markus ! For testing purposes you could run WSPR-2-mode twice as well instead of -15 and -2. Better use two installations of WSPR-X into two separate directories from Root C:\, as WSPR writes temporary *.wav and *.C2-files to its "save"-subdirectory (even at save=none). They are deleted immediately after decode. Maybe one instance deletes the file of the concurrent instance. At WSPR-15 and WSPR-2 both beginn their cycle at 00:00 and 00:30, so the filenames may be identical, leaving to confusion. There will be NO errormessages warning you! At the beginning of WSPR-X we learned that whitespace characters in directory-names as well as local characters (German "Umlaute") are a bad idea. This has not changed. Best use old-fashioned DOS names like C:\wspr_2 and C:\wspr_15 or similar. There are no errormessages or crash, it just will not decode anything. (experience of Stefan DK7FC at that time) 73 de dg3lv Tobias Am 26.05.2015 um 18:56 schrieb Markus Vester: > Hi Wolf, > that's exactly what I did too, with same results: wspr-2 running and > uploading fine, no chance to test -15 due to lack of signals. But if > signals had been present on both bands, wouldn't both instances try to > access the same files in the same directory, eg. ALL_WSPR.TXT or > settings? Well, with Andy on -15 we may find out tonight. > All the best, > Markus (DF6NM) > BTW I decoded DF1VB for a while with 6.5 seconds latency, and then no > more - might have been a too large clock offset. > > > -----Ursprüngliche Mitteilung----- > Von: wolf_dl4yhf > An: rsgb_lf_group > Verschickt: Di, 26 Mai 2015 6:27 pm > Betreff: Re: LF: 630M WSPR T/A - WSPR-15? > > rrr Stefan and Markus - thanks for the info. > > I have two instances of WSPR-X running, launched from the same > directory, one configured (manually) for WSPR-2 and the other for -15. > Not a single decode from the latter yet. > > I guess as long as they run, the two instances don't interfear (:o) > > 73, > Wolf DL4YHF . > > > Am 26.05.2015 02:19, schrieb Markus Vester: >> Wolf, as far as I know the only way to separate them in the database >> seems to be sorting by frequency (which is not very useful otherwise). >> There is a peculiarity in that the hh:15 and hh:45 timestamps in the >> database seem to be "rectified" to even minutes (hh:16 and hh:46) at >> midnight UT (just happened to G4JNT entries). >> Stefan, I'm not sure about not using -15 on MF. Even though fading is >> faster and deeper, the WSPR decoder seems to cope well with it. After >> all WSPR-2 is useful on HF where fading happens in seconds. The >> spectrogram of Andy's transmission last night sometimes showed two >> deep fades in one sequence, but it was decoded ok. It has been argued >> that a very short and strong maximum might be utilized by -2 and not >> by -15, and maybe there's not all of the theoretical 9 dB gain, but I >> reckon on average it's not much less. >> Laurence yes your frequencies are correct, dial *474.2 kHz*, RF: 475.6 >> - 475.8 WSPR-2, 475.8 - 475.825 WSPR-15. >> I wonder if it is possible to run two instances of WSPRX side by side >> on the same machine, one for -2 and one for -15? Or would they crash >> one another? >> 73, Markus >> >> *From:* DK7FC >> *Sent:* Tuesday, May 26, 2015 1:16 AM >> *To:* rsgb_lf_group@blacksheep.org >> *Subject:* Re: LF: 630M WSPR T/A >> >> Am 25.05.2015 22:55, schrieb wolf_dl4yhf: >>> p.s. is there a possibility to filter / display only WSPR-15 decodes >>> from the database, and how widespread is the use of that mode ? >> >> ...there have been a few MF TA tests in WSPR-15 in the early 630m >> days, showing that this mode is to slow for the path on that band. >> These tests have not been very extended though. But most likely there >> is not a 'gain' of 9 dB over WSPR-2. I would assume that successful >> detections are even less likely in that mode over the pond. >> >> 73, Stefan >