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 w8KK7BDM006759 for ; Thu, 20 Sep 2018 22:07:12 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1g358g-0005aU-Fh for rs_out_1@blacksheep.org; Thu, 20 Sep 2018 21:01:26 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1g357t-0005aB-Fu for rsgb_lf_group@blacksheep.org; Thu, 20 Sep 2018 21:00:37 +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 ) id 1g357q-0006Df-8b for rsgb_lf_group@blacksheep.org; Thu, 20 Sep 2018 21:00:34 +0100 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 8E9C021060 for ; Thu, 20 Sep 2018 22:00:29 +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=1537473629; bh=hvF6xNMW05BZ3A4VF4EaVW4CW/VvsPItJGAF6+Yju/c=; h=Date:From:To:Subject:From; b=McTBT2V0JpRRVELAr95PJ2chStGUmjydk7S+9kXSNNweIlbZ2KpcQOcpdZNs0xZe4 uoT4GQCinUJe9cEKf6EsyL+cRZkDv9NxO/XcC4Nfcoev3qz881nMmmIDji06D+oDxC 6slM1zxo1Epdz606bZU3FExqQiTFqJ000KPV9ygXJR0xiHiw577QqaQ99VRGpfHfXd EDEYtX1u+pzSnwx1DnMRQSbd9XSaaUI8VswWoij58ghpB0PYcuiioN4vMHhjmV7BB2 gXVbPFEmDTf8iAX25dH8WIDa47e0j/G4dAz4/p6i9nUO0YnwwmU+jk6WNMXHsjdEKl v51TMtlm9Ez0g== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 42GSJX4QZHz9rxK for ; Thu, 20 Sep 2018 22:00:28 +0200 (CEST) Message-ID: <5BA3FC5C.7070209@posteo.de> Date: Thu, 20 Sep 2018 22:00:28 +0200 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: <7aad9ea4-dfbc-dfd4-3494-4643cdeb10d9@bigpond.com> <5B9C0ECF.6060402@posteo.de> <5B9FB6C7.8080607@posteo.de> <5BA3EEC3.1010509@posteo.de> <5BA3F126.2050803@posteo.de> In-Reply-To: <5BA3F126.2050803@posteo.de> 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: ...something went wrong. Sorry for the confusion. The late message will start tomorrow for the first time. Pity. 73, Stefan Am 20.09.2018 21:12, schrieb DK7FC: > Correction: Same parameters as used for the first message, i.e. both > messages use > > *f = 17470.1000 Hz > Start time: 20.SEP.2018 19:30:00 UTC & 16:30:00 UTC (daily) > Symbol period: 10 s > Characters: 3 > CRC bits: 19 > Coding 16K21A > Antenna current: 1.2 A* > > 73, Stefan > > > Am 20.09.2018 21:02, schrieb DK7FC: >> VLF, >> >> In addition to the message below, which has been transmitted 3 times >> already, i will start to transmit the same message into a later time >> slot, also using different parameters: >> >> *f = 17470.1000 Hz >> Start time: 20.SEP.2018 19:30:00 UTC (daily) >> Symbol period: 10 s >> Characters: 3 >> CRC bits: 16 >> Coding 16K21A >> Duration: 02:24 [hh:mm] >> Antenna current: 1.2 A >> >> *73, Stefan >> >> Am 17.09.2018 16:14, schrieb DK7FC: >>> Edgar, VLF, >>> >>> After evaluating the latest 4 days of carrier transmissions it shows >>> that the path from DL to VK7 is quite unstable, i.e. the phase is >>> very dynamic. When applying different frequency offsets, it seems >>> that the best start time for a message attempt is 16:30 UTC these >>> days. The SNR then peaks when applying a -40 uHz offset, attached. >>> Something between 2...3 hours seems to be best. Currently 2 hours >>> seem to give better results but 3 hours would be less dynamic. >>> Based on this data i'm trying: >>> >>> *f = 17470.1000 Hz >>> Start time: 17.SEP.2018 16:30:00 UTC (daily) >>> Symbol period: 10 s >>> Characters: 3 >>> CRC bits: 19 >>> Coding 16K21A >>> Duration: 02:32 [hh:mm] >>> Antenna current: 1.2 A* >>> >>> 73, Stefan [...] 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.66 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 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: 18c242620d7d7b91a1caf5740aa3e326 Subject: Re: VLF: EbNaut 3 character attempt to VK7 Content-Type: multipart/alternative; boundary="------------020106050506030000080208" 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=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. --------------020106050506030000080208 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ...something went wrong. Sorry for the confusion. The late message will start tomorrow for the first time. Pity. 73, Stefan Am 20.09.2018 21:12, schrieb DK7FC: > Correction: Same parameters as used for the first message, i.e. both > messages use > > *f = 17470.1000 Hz > Start time: 20.SEP.2018 19:30:00 UTC & 16:30:00 UTC (daily) > Symbol period: 10 s > Characters: 3 > CRC bits: 19 > Coding 16K21A > Antenna current: 1.2 A* > > 73, Stefan > > > Am 20.09.2018 21:02, schrieb DK7FC: >> VLF, >> >> In addition to the message below, which has been transmitted 3 times >> already, i will start to transmit the same message into a later time >> slot, also using different parameters: >> >> *f = 17470.1000 Hz >> Start time: 20.SEP.2018 19:30:00 UTC (daily) >> Symbol period: 10 s >> Characters: 3 >> CRC bits: 16 >> Coding 16K21A >> Duration: 02:24 [hh:mm] >> Antenna current: 1.2 A >> >> *73, Stefan >> >> Am 17.09.2018 16:14, schrieb DK7FC: >>> Edgar, VLF, >>> >>> After evaluating the latest 4 days of carrier transmissions it shows >>> that the path from DL to VK7 is quite unstable, i.e. the phase is >>> very dynamic. When applying different frequency offsets, it seems >>> that the best start time for a message attempt is 16:30 UTC these >>> days. The SNR then peaks when applying a -40 uHz offset, attached. >>> Something between 2...3 hours seems to be best. Currently 2 hours >>> seem to give better results but 3 hours would be less dynamic. >>> Based on this data i'm trying: >>> >>> *f = 17470.1000 Hz >>> Start time: 17.SEP.2018 16:30:00 UTC (daily) >>> Symbol period: 10 s >>> Characters: 3 >>> CRC bits: 19 >>> Coding 16K21A >>> Duration: 02:32 [hh:mm] >>> Antenna current: 1.2 A* >>> >>> 73, Stefan --------------020106050506030000080208 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit ...something went wrong. Sorry for the confusion. The late message will start tomorrow for the first time. Pity.

73, Stefan

Am 20.09.2018 21:12, schrieb DK7FC:
Correction: Same parameters as used for the first message, i.e. both messages use

f = 17470.1000 Hz
Start time: 20.SEP.2018  19:30:00 UTC & 16:30:00 UTC (daily)
Symbol period: 10 s
Characters: 3
CRC bits: 19
Coding 16K21A
Antenna current: 1.2 A


73, Stefan


Am 20.09.2018 21:02, schrieb DK7FC:
VLF,

In addition to the message below, which has been transmitted 3 times already, i will start to transmit the same message into a later time slot, also using different parameters:

f = 17470.1000 Hz
Start time: 20.SEP.2018  19:30:00 UTC (daily)
Symbol period: 10 s
Characters: 3
CRC bits: 16
Coding 16K21A
Duration: 02:24 [hh:mm]
Antenna current: 1.2 A

73, Stefan

Am 17.09.2018 16:14, schrieb DK7FC:
Edgar, VLF,

After evaluating the latest 4 days of carrier transmissions it shows that the path from DL to VK7 is quite unstable, i.e. the phase is very dynamic.  When applying different frequency offsets, it seems that the best start time for a message attempt is 16:30 UTC these days. The SNR then peaks when applying a -40 uHz offset, attached. Something between 2...3 hours seems to be best. Currently 2 hours seem to give better results but 3 hours would be less dynamic.
Based on this data i'm trying:

f = 17470.1000 Hz
Start time: 17.SEP.2018  16:30:00 UTC (daily)
Symbol period: 10 s
Characters: 3
CRC bits: 19
Coding 16K21A
Duration: 02:32 [hh:mm]
Antenna current: 1.2 A


73, Stefan
--------------020106050506030000080208--