Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_MED, SPF_PASS,SUBJ_ALL_CAPS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 X-Spam-DCC: EATSERVER: mailn 1166; Body=2 Fuz1=2 Fuz2=2 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by lipkowski.org (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id v2T7ARDI025392 for ; Wed, 29 Mar 2017 09:10:28 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ct7gs-0001Xl-A5 for rs_out_1@blacksheep.org; Wed, 29 Mar 2017 08:06:46 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ct7gr-0001XW-FJ for rsgb_lf_group@blacksheep.org; Wed, 29 Mar 2017 08:06:45 +0100 Received: from mail-qt0-x233.google.com ([2607:f8b0:400d:c0d::233]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-ECDSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1ct7gm-0000Pj-08 for rsgb_lf_group@blacksheep.org; Wed, 29 Mar 2017 08:06:44 +0100 Received: by mail-qt0-x233.google.com with SMTP id x35so5326080qtc.2 for ; Wed, 29 Mar 2017 00:06:39 -0700 (PDT) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=u/yVcec11V7fJuRutmp9Uj1sc/lOIr/3MPC/zF0Z1Xc=; b=HpUy1lZaJOZ9zA6aoHg5nY+8Ofuz2nIiYPGaJ78RHE6OlWAPGQJjWTtsuZaU80PL88 SsXrqzoMgkX7UpVSGJB9mcfp7q0DyNIcJlCoLmMGs40RG2k+RaFiynnM6Pe7oHHGI6wA QsQX/KHZrW4U7+8YLBAgYqZVmJe279HT5hvedcPg04YImdp+VZvNGMEqFNS2dl8Ibrey 65F7rnFw6YZW56T5TmjptUpmj+JBI6DeKRoH7gLwI99hEITHruGoB/98/1gMmelZu58n sYABwFUkj51L1GZ4a3DgaeaIU8syVp96bN7TMXn+IEk7YyTFJ2lwd06NSPUm6HjZ9a8U MBQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=u/yVcec11V7fJuRutmp9Uj1sc/lOIr/3MPC/zF0Z1Xc=; b=SlorxGu5QbX0NYKhKIJKiLYApyW6pj/8w02vNYEBdMZmkewn8SDjsyaHZHwaUgup+e JzT6cgCabJ3pnYteTKOjans5L8mNrWJZrunT0HA8URHCPZyCcAHoNc499SWcby56h+xX zyaQt6fUgwMmdXv106zn7WJ0eA2QHX6onSNgajIghjdr5zyhyZ0C13moSrwlIjy+7CdX I6Ru4pozzT76G8AaIXW96k3cZUNxWZSDZrjZTuY6j5Oydtq8POvYtIYO/5bfpa5xJn6G Asje56JYjnyaAmFqCrRMOSMgONVBZ8zLOrmUIh97BX2sBC7yjFrs2oA0XKbjpTgQwQxI LCqA== X-Gm-Message-State: AFeK/H2bhY/w03BjPhV1+fw3nk4BuZlTw6moDXdjxu7OhYimk0sLtmuFuukOWpxMdiDfR8n2dOtZjDnzsGPE5g== X-Received: by 10.237.54.162 with SMTP id f31mr29898103qtb.2.1490771197846; Wed, 29 Mar 2017 00:06:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.45.110 with HTTP; Wed, 29 Mar 2017 00:06:37 -0700 (PDT) In-Reply-To: <7f3f518e-ae25-c64b-7963-13d6d1e7b88a@charter.net> References: <15b0c868a2e-7d4f-1e3d7@webprd-a90.mail.aol.com> <5b20b18e-06fc-6965-34dc-dac06702857b@n1bug.com> <58D90EAA.2040800@gmail.com> <7f3f518e-ae25-c64b-7963-13d6d1e7b88a@charter.net> From: Alex R7NT Date: Wed, 29 Mar 2017 10:06:37 +0300 Message-ID: To: rsgb_lf_group@blacksheep.org X-Scan-Signature: 5f3d51ad98dd7d967f54e1b86b99caac Subject: Re: LF: WSPR-15 Content-Type: multipart/alternative; boundary=001a1146f022b06d46054bd93728 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.75 Status: O X-Status: X-Keywords: X-UID: 11048 --001a1146f022b06d46054bd93728 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi John! Thank you very much for information of perspective WSPR15. >From my point of view for example if Ron WH2XDN TX in WSPR15 he will have VK, EU etc and more JA in his list. His great 10W ERP will be able to be received too far :-) So, I have not found any information abt his TX antenna and his output power of TX. Could you be so kind to tell me abt TX setup of Ron=E2=80=99s = WH2XDN. Or share links to site with this information! Thanks! 73! Alex R7NT 136.73.ru 2017-03-27 17:03 GMT+03:00 John Andrews : > Stefan, > > An email exchange with Joe Taylor at the start of this year indicated tha= t > his group thought that WSPR-15 was a "dead end", and they planned no > further development on it. Rather, they were talking about: > > "If a more sensitive WSPR-like mode is truly needed for LF/MF > experimentation, would it be better to create something that for now > I'll call "WSPR-MSK", which (like MSK144) uses OQPSK (Offset Quadrature > Phase-Shift Keying), a constant-envelope waveform, coherent > demodulation, and an LDPC code? Steve (K9AN) and I have discussed such > a possible mode, and we might be more motivated to develop that rather > than going "back" to WSPR-15. I suspect WSPR-MSK could be made as > sensitive (or better) than WSPR-15, even with transmissions shorter than > 15 minutes." > > I haven't followed up on it, other than to give him initial encouragement= . > I notice that Andy Talbot has posted an inquiry today on the WSJT > development group reflector, so that might produce an update. > > John, W1TAG > > > On 3/27/2017 9:07 AM, DK7FC wrote: > >> Hi Paul, >> >> I've never had serious problems with the WSJT-X software running in >> WSPR-15 mode. However they did not continue to develop WSPR-15 since >> some years. For example the multi-pass decode option is not available >> for WSPR-15, a pity. Obviously they lost their interest, because it is >> 'just' LF, and there are not many users. If i remember correctly it was >> 2012 when i've been in contact with K1JT to talk about WSPR-15. That was >> the time he released the mode. He even was a member of this group for >> some time in that year. So i would assume they rather want to drop their >> interest in that mode for the future. Anyway we can use the old version >> which has of course the same performance than in 2013... >> One can assume an improvement of up to 9 dB, in theory and practice... >> >> 73, Stefan >> >> Am 27.03.2017 13:22, schrieb N1BUG: >> >>> On 03/27/2017 03:08 AM, Alex R7NT wrote: >>> >>> I'm more interested in WSPR15 vs WSPR2 vs OP32 :-) >>>> What are the ideas about this? >>>> >>>> I believe WSPR15 is better against WSPR2 on LF for long distances in >>>> the usual propagation >>>> >>> >>> Hi Alex. >>> >>> I am very interested in WSPR15. >>> >>> Unfortunately the only WSPR15 decoder seems to be WSPR-X software >>> which many of us cannot use. It is always crashing, freezing, stopping >>> on many PCs. >>> >>> If someday the developers put WSPR15 in the stable WSJT-X software (or >>> someone writes another decoder software) then I think it has a chance >>> to become more popular. I am waiting! >>> >>> When (if) there is a stable decoder I will listen for WSPR15 in >>> parallel with WSPR2. >>> >>> 73, >>> Paul N1BUG / WI2XTC >>> FN55mf >>> >>> --001a1146f022b06d46054bd93728 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi John!

Thank you v= ery much for information of perspective WSPR15.
From my point of view=C2=A0for e= xample=C2=A0if Ron WH2XDN TX in WSP= R15 he will have VK, EU etc and more JA in his list. His great 10W ERP will= be able to be received too far :-)
So, I have not found any information abt his TX antenna and his output= power of TX. Could you be so kind to tell me abt TX setup of Ron=E2=80=99s= WH2XDN. Or share links to site with this information!
Thanks!

73! Alex R7NT =C2=A0136.73.ru

2017-03-27 17:03 GMT+03:00 John Andrews <w1tag@charter.n= et>:
Ste= fan,

An email exchange with Joe Taylor at the start of this year indicated that = his group thought that WSPR-15 was a "dead end", and they planned= no further development on it. Rather, they were talking about:

"If a more sensitive WSPR-like mode is truly needed for LF/MF
experimentation, would it be better to create something that for now
I'll call "WSPR-MSK", which (like MSK144) uses OQPSK (Offset = Quadrature
Phase-Shift Keying), a constant-envelope waveform, coherent
demodulation, and an LDPC code?=C2=A0 Steve (K9AN) and I have discussed suc= h
a possible mode, and we might be more motivated to develop that rather
than going "back" to WSPR-15.=C2=A0 I suspect WSPR-MSK could be m= ade as
sensitive (or better) than WSPR-15, even with transmissions shorter than 15= minutes."

I haven't followed up on it, other than to give him initial encourageme= nt. I notice that Andy Talbot has posted an inquiry today on the WSJT devel= opment group reflector, so that might produce an update.

John, W1TAG


On 3/27/2017 9:07 AM, DK7FC wrote:
Hi Paul,

I've never had serious problems with the WSJT-X software running in
WSPR-15 mode. However they did not continue to develop WSPR-15 since
some years. For example the multi-pass decode option is not available
for WSPR-15, a pity. Obviously they lost their interest, because it is
'just' LF, and there are not many users. If i remember correctly it= was
2012 when i've been in contact with K1JT to talk about WSPR-15. That wa= s
the time he released the mode. He even was a member of this group for
some time in that year. So i would assume they rather want to drop their interest in that mode for the future. Anyway we can use the old version
which has of course the same performance than in 2013...
One can assume an improvement of up to 9 dB, in theory and practice...

73, Stefan

Am 27.03.2017 13:22, schrieb N1BUG:
On 03/27/2017 03:08 AM, Alex R7NT wrote:

I'm more interested in WSPR15 vs WSPR2 vs OP32 :-)
What are the ideas about this?

I believe WSPR15 is better against WSPR2 on LF for long distances in
the usual propagation

Hi Alex.

I am very interested in WSPR15.

Unfortunately the only WSPR15 decoder seems to be WSPR-X software
which many of us cannot use. It is always crashing, freezing, stopping
on many PCs.

If someday the developers put WSPR15 in the stable WSJT-X software (or
someone writes another decoder software) then I think it has a chance
to become more popular. I am waiting!

When (if) there is a stable decoder I will listen for WSPR15 in
parallel with WSPR2.

73,
Paul N1BUG / WI2XTC
FN55mf

--001a1146f022b06d46054bd93728--