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 x0JL0GB8026324 for ; Sat, 19 Jan 2019 22:00:17 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gkxcF-0007AS-Bs for rs_out_1@blacksheep.org; Sat, 19 Jan 2019 20:53:19 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gkxa9-0007A3-OG for rsgb_lf_group@blacksheep.org; Sat, 19 Jan 2019 20:51:10 +0000 Received: from mail-ed1-x52e.google.com ([2a00:1450:4864:20::52e]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gkxa4-0003hi-FL for rsgb_lf_group@blacksheep.org; Sat, 19 Jan 2019 20:51:06 +0000 Received: by mail-ed1-x52e.google.com with SMTP id x30so13807020edx.2 for ; Sat, 19 Jan 2019 12:51:03 -0800 (PST) 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:references:in-reply-to:from:date:message-id:subject:to; bh=ohvPZ2As4CY301gY92XUiUqZkKyWLLR7XdXFLakJo08=; b=b1pNy7PCV1ynXUE/cUp3pnFSdyl8IQM77c+BibTr8Hwiehm/UrM4w+iD1w5NFzIVWa TwOinDtgdcZi773pRKBGPa4Z3xNYVCj4Z1ouLnGsRpDsLi7B1/GjJWRlSJhX9uTXV8ez BtUGPZw2IW/rpASa0qFmg8NYD5l07s3hXWRYq8usZ1XJa3NVIUToucjpelkjINnmxsM6 pPXwKRI6vCHBckO5HCX7/i1AUEDP8ayctYyswrIHs9bho054E3obg1bTfYqVjWuCuZQ1 T1d/giHMO9r5tO9NZl9DXHacEr22JJT9EF1xzEfTwgtciJb/cYA8iSOoZMK/8AKn9W9N O2bA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ohvPZ2As4CY301gY92XUiUqZkKyWLLR7XdXFLakJo08=; b=emoDtT6rE5tl5zAkFRv6OIj8sMY2u6ohXtnpPHUoskIbPQJjZ43+j/GFHJ+u9okY7C VGqYrTRag0vTuD6255oKWuarXwPtQ0lMWkh5Yto3R6aRC06GLvB4ttI3ODq+ZU6g7hSA UaYMjWktHUXejEscLWRQIXozNouxwieyVm9DHHsxQkw4hrX2IUwKFvBetAiySH24VNvu WhwVM4ksYF0D7d98/IH0Y+F6DW5oNFwT4UTv+t2F8Ev/H6kud278rx9XOSQrBFW1HyWX uxWNJIMJPzwx5vxq+8fNuAC3dtDhhGMYuxlTLQqbZLn6UoIxOxd4rDpENdjd9JDQ1nhh dX6w== X-Gm-Message-State: AJcUukc6rqMxTjw6ShS3hPaF2vOINq5kaaaKxejaBL8n9P6exRZQ0gIg +9LpaTGjuOUv7dk1FK0RLWJnCmCbNZfrjghQCF0DaQ== X-Google-Smtp-Source: ALg8bN6T3iFXreBBeU38ptRgpEruz/jE575+wOlpYvJKgUqvdI/0D3JcCkX8Zg8BKZVxOdCszkrYdgI9HNKoo9bom1c= X-Received: by 2002:a17:906:b297:: with SMTP id q23-v6mr18703938ejz.147.1547931062658; Sat, 19 Jan 2019 12:51:02 -0800 (PST) MIME-Version: 1.0 References: <1UTCMpy6DA.3Qa4W73pIAl@optiplex980-pc> In-Reply-To: <1UTCMpy6DA.3Qa4W73pIAl@optiplex980-pc> From: Riccardo Zoli Date: Sat, 19 Jan 2019 21:50:50 +0100 Message-ID: To: LF Group X-Spam-Score: 1.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: Hi Jay and all LF EbNauters, Many thanks for your reports and suggestions. And many thanks Jay for your efforts. Yes, indeed: so I'll try tonite with a half of symbol duration, pratically the same parameters used in my transmissi [...] Content analysis details: (1.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [2a00:1450:4864:20:0:0:0:52e listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (riccardozoli80[at]gmail.com) 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (riccardozoli80[at]gmail.com) 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 1.0 FREEMAIL_REPLY From and body contain different freemails X-Scan-Signature: 5934134de2d93cab1d5fc440b67de82f Subject: Re: LF: EbNaut Content-Type: multipart/alternative; boundary="000000000000206ead057fd5c9c4" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.7 required=5.0 tests=FROM_ENDS_IN_NUMS,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 --000000000000206ead057fd5c9c4 Content-Type: text/plain; charset="UTF-8" Hi Jay and all LF EbNauters, Many thanks for your reports and suggestions. And many thanks Jay for your efforts. Yes, indeed: so I'll try tonite with a half of symbol duration, pratically the same parameters used in my transmissions on 14/15 Nov. 2018: *QRG: 137545 Hz* *Coding 8K19A* *CRC 16* *3 sec./sym.* *6 characters* Duration: 28 min. every 30 minutes, 1st transmission on 2100 UTC, last on 0700 UTC. Reports are welcome as usual... All the best 73 de Riccardo IW4DXW Il giorno Sab 19 Gen 2019, 12:36 jrusgrove@comcast.net < jrusgrove@comcast.net> ha scritto: > Alex, Riccardo & EbNaut-eers > > Unfortunately no copy of either station last night. Alex ... > understand your TX frequency may have been moving around. > > I wonder if a 1 hour transmission is too long for 137 kHz? Recalling > spectrograms of QRSS going back many years seems to indicate a QSB pattern > of approximately 15 - 30 minutes. Both receptions of IZ7SLZ and IW4DXW (a > while back) were 'one and done' with no hint of the signal in adjacent time > slots ... using 30 minute transmission times. Even DK7FC's normally big > signal shows big QSB swings from one half hour period to the next. Can't > help but wonder if 20 or 30 minute transmission periods make better use of > the QSB characteristics on 136 kHz. > > Comments? > > Jay W1VD > --000000000000206ead057fd5c9c4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi Jay and = all LF EbNauters,

Many t= hanks for your reports and suggestions.
And many tha= nks Jay for your efforts. Yes, indeed: so I'll try tonite with a half o= f symbol duration, pratically the same parameters used in my transmissions = on 14/15 Nov. 2018:

Q= RG: 137545 Hz
Coding 8K19A
CRC 16
3 sec./sym.
6 characters
Duration: 28 min.<= /div>
every 30 minutes, 1st transmission on 2100 UTC, last= on 0700 UTC.

Report= s are welcome as usual...


All the best

73 de Riccardo IW4DXW

<= div dir=3D"auto">









<= div dir=3D"ltr">Il giorno Sab 19 Gen 2019, 12:36 jrusgrove@co= mcast.net <jrusgrove@comcast.net> ha scritto:
Alex, Riccardo & EbNaut-eers
=C2=A0
Unfortunately no copy of either=C2=A0station last night. Alex ... unde= rstand=C2=A0your TX frequency may have been moving around.
=C2=A0
I wonder if a 1 hour transmission=C2=A0is too long for 137 kHz?=C2=A0R= ecalling spectrograms of QRSS going back many years seems to indicate a QSB= pattern of approximately 15 - 30 minutes. Both receptions of IZ7SLZ and IW= 4DXW (a while back) were 'one=C2=A0and done' with no hint of the si= gnal in adjacent time slots ... using 30 minute transmission times.=C2=A0Ev= en=C2=A0DK7FC's=C2=A0normally big signal shows big QSB swings from one = half hour period to the next. Can't help but wonder if 20 or 30 minute = transmission periods make better use of the QSB characteristics on 136 kHz.=
=C2=A0
Comments?
=C2=A0
Jay W1VD=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
--000000000000206ead057fd5c9c4--