Return-Path: <owner-rsgb_lf_group@blacksheep.org>
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 w7KETcta020605
	for <rlg@klubnl.pl>; Mon, 20 Aug 2018 16:29:39 +0200
Received: from majordom by post.thorcom.com with local (Exim 4.14)
	id 1frl7f-0000Sh-0b
	for rs_out_1@blacksheep.org; Mon, 20 Aug 2018 15:25:35 +0100
Received: from [195.171.43.32] (helo=relay1.thorcom.net)
	by post.thorcom.com with esmtp (Exim 4.14)
	id 1frl7e-0000SY-M4
	for rsgb_lf_group@blacksheep.org; Mon, 20 Aug 2018 15:25:34 +0100
Received: from mout02.posteo.de ([185.67.36.66])
	by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
	(Exim 4.91_59-0488984)
	(envelope-from <selberdenken@posteo.de>)
	id 1frl7d-0006zf-4j
	for rsgb_lf_group@blacksheep.org; Mon, 20 Aug 2018 15:25:33 +0100
Received: from submission (posteo.de [89.146.220.130]) 
	by mout02.posteo.de (Postfix) with ESMTPS id E67C520F06
	for <rsgb_lf_group@blacksheep.org>; Mon, 20 Aug 2018 16:25:31 +0200 (CEST)
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=1534775131; bh=5Xh3panyd0JXFaf8g58Sj7+prwIYBCFOiMRYHIr/t5Q=;
	h=Date:From:To:Subject:From;
	b=gR2dglg6mB97lfcz7BS5WcDFLmjp0FwmvX6xqrGuRFCni0jcusbLsvYtTcjmzoqWV
	 JnByiaifomRrMFoAzrPQaP0KujlKkzACx295jZiEaO/7MtvhoLRVVv+9EPe3z1zU4b
	 kTIa93Ghm6Q+3QJGQXquVGUUQgs9sQQhPUTQRGNaQhZbTOtIJfOHvbT2ZfWsTjbc3z
	 W9q9fpdBMJoYxGUfgwDJmzT5CsE4tzUCwcxrHTRw13E7ocy0XqEYnBXD6nEI3p54to
	 S31CEBPsI86zDUNcvsHvUfgGBQxJUNvm01+ffD5qBR1+smYyN6npb0VYc1rowdUcMx
	 1dNq9dcOZb2jQ==
Received: from customer (localhost [127.0.0.1])
	by submission (posteo.de) with ESMTPSA id 41vGLM2Jzvz9rxG
	for <rsgb_lf_group@blacksheep.org>; Mon, 20 Aug 2018 16:25:31 +0200 (CEST)
Message-ID: <5B7ACF5B.1020303@posteo.de>
Date: Mon, 20 Aug 2018 16:25:31 +0200
From: DK7FC <selberdenken@posteo.de>
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: <A722128C879B4EE082F37351D38B066C@mal> <CAD2C4F26F134BD3916E2095ED907F01@mal> <5B7ACEC4.2090304@posteo.de>
In-Reply-To: <5B7ACEC4.2090304@posteo.de>
X-Spam-Score: -2.5 (--)
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:  PS: Is there anyone else interested in VK or even ZL ? Am
   20.08.2018 16:23, schrieb DK7FC: > Hi VLF, > > For this week, i'm planning
    to start with new experiments on 17.47 > kHz, where i have a (renewed) special
    permission to transmit. > > So far the best results were a prooved carrier
    detection as well as a > 1 character EbNaut decode by Edgar from Tasmania
    (VK7). > > The first goal will be to determine the best time (start time
   and > length) on the path for this season. We have a usable path for about
    2 > months centered on our autun/spring time (21st SEP). > > The Signal will
    be exported by SpecLab to simple txt files containing > the FFT data. This
    allows stacking, which will be required to get some > S/N at all. A reasonable
    stable path is essential during the > transmission time. All this will be
    determined by running some carrier > transmissions, a few hours per day,
   starting about 16 UTC. > > When knowing the time to try we will attempt to
    transfer a 2 character > message and then even longer messages. 5 characters
    would be realistic > i think, with some luck and good propagation and low
    QRN on the RX > site... > > More soon. > > 73, Stefan [...] 
 Content analysis details:   (-2.5 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.66 listed in list.dnswl.org]
 -0.2 RCVD_IN_MSPIKE_H2      RBL: Average reputation (+2)
                             [185.67.36.66 listed in wl.mailspike.net]
 -0.0 SPF_PASS               SPF: sender matches SPF record
 -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: f62c7cf8eeb8e5a327b71719e9bffff1
Subject: Re: VLF: New experiments on 17.47 kHz planned...
Content-Type: text/plain; charset=ISO-8859-1; 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

PS: Is there anyone else interested in VK or even ZL ?

Am 20.08.2018 16:23, schrieb DK7FC:
> Hi VLF,
>
> For this week, i'm planning to start with new experiments on 17.47 
> kHz, where i have a (renewed) special permission to transmit.
>
> So far the best results were a prooved carrier detection as well as a 
> 1 character EbNaut decode by Edgar from Tasmania (VK7).
>
> The first goal will be to determine the best time (start time and 
> length) on the path for this season. We have a usable path for about 2 
> months centered on our autun/spring time (21st SEP).
>
> The Signal will be exported by SpecLab to simple txt files containing 
> the FFT data. This allows stacking, which will be required to get some 
> S/N at all. A reasonable stable path is essential during the 
> transmission time. All this will be determined by running some carrier 
> transmissions, a few hours per day, starting about 16 UTC.
>
> When knowing the time to try we will attempt to transfer a 2 character 
> message and then even longer messages. 5 characters would be realistic 
> i think, with some luck and good propagation and low QRN on the RX 
> site...
>
> More soon.
>
> 73, Stefan