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 vB9DjcfU011176 for ; Sat, 9 Dec 2017 14:45:40 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eNfNr-0000eT-2k for rs_out_1@blacksheep.org; Sat, 09 Dec 2017 13:41:39 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eNfNq-0000eK-Kr for rsgb_lf_group@blacksheep.org; Sat, 09 Dec 2017 13:41:38 +0000 Received: from mout01.posteo.de ([185.67.36.65]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eNfNn-0003M7-Km for rsgb_lf_group@blacksheep.org; Sat, 09 Dec 2017 13:41:37 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id E8B4020FFA for ; Sat, 9 Dec 2017 14:41:34 +0100 (CET) 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=1512826894; bh=5UYcLWELmk1fwFsd2/0cwCZDZlt1+C00aOPuLSkyeto=; h=Date:From:To:Subject:From; b=apkDBdNOoQvPLGOyF4kZGtEtOF3zPvVBESjjxtXA+vvlTg7ZmTSdyw3XxTnNuBEkb 0Mx8GHbMhDoCK/7R2SRVjWVohpEJz4gg2zW4E3au9S9TzxtbDfChFTo29YmLyUilgS Vq0NNq+JwTA0sD2Zj10L8W1rXVbeEQs5MVFNuwTdsuYiyQz3pZCQ85/gwg54IZVamm 96MkBy/XHJhGWlPwb3nx363O3NPQQmBPHUWnT0noRHx9zyk4vTrFjWclsZn83IDJ7w Zmwbp9Jl8SAEkTlHh48lP+xvDZnz5V/Hl/cdwKV7sbotWaxb7tgVIK/fl9A0HmFQCI DTsGPAzXeFWHA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3yv9Nt3wZ1z9rxN for ; Sat, 9 Dec 2017 14:41:34 +0100 (CET) Message-ID: <5A2BE80E.4020307@posteo.de> Date: Sat, 09 Dec 2017 14:41:34 +0100 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: <4d96a9d4-5f22-7650-872b-6344e9aea8e3@abelian.org> <5A19FF75.7080801@posteo.de> <5A1FFE7C.9050703@posteo.de> <5A226B0C.3080701@posteo.de> <579355A36AEE9D4FA555C45D556003AB9AAB0EB9@servigilant.vigilant.local> <5A25C304.3050607@posteo.de> <5A271218.9040803@posteo.de> <5A282BF9.4050409@posteo.de> <5A29193A.2090600@posteo.de> <5A29A373.6060406@posteo.de> <5A29AF93.9030908@posteo.de> In-Reply-To: <5A29AF93.9030908@posteo.de> X-Spam-Score: 0.0 (/) 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 the administrator of that system for details. Content preview: Hi Paul, VLF, Now there was the carrier during the whole night with 1.2 A . Do you have some recommendations for me regarding the best time window for that path? I would like to pass one character over there without stacking. It doesn't matter to run the same message again. Maybe it will decode in that night on its own. But then it would certainly work when stacking is used. So if there is no great imrpovement to be expected from different parameter settings, especially a longer transmission time, then i would simply run the same message again as stated below. I will do so, except you give me some convincing recommendations to start a new run. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -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: 9bd342c7d74bc0c7d15d59c1164ca995 Subject: Re: VLF: TA east to west? Content-Type: multipart/alternative; boundary="------------060805000807020107050605" 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. --------------060805000807020107050605 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Paul, VLF, Now there was the carrier during the whole night with 1.2 A . Do you have some recommendations for me regarding the best time window for that path? I would like to pass one character over there without stacking. It doesn't matter to run the same message again. Maybe it will decode in that night on its own. But then it would certainly work when stacking is used. So if there is no great imrpovement to be expected from different parameter settings, especially a longer transmission time, then i would simply run the same message again as stated below. I will do so, except you give me some convincing recommendations to start a new run. Ah and it would be interesting to see a spectrum peak from the last night, from Mikes RX and from yours! I know it is your world you are operating in, so it is just a marginal effort to produce the peak i would assume :-) And it is a clear contribution for the overall activity on the band. The 1.2 A carrier will then continue until 21:30 UTC and will go over into the BPSK then... 73, Stefan Am 07.12.2017 22:16, schrieb DK7FC: > 45 minutes left before the message starts. I can change to CRC 12 but > 08:08 UTC means that about the last 90 minutes are running in daylight > here. > Let me go to CRC 10, that's 9 hours and 36 minutes. And i'm starting > 30 minutes earlier. > If it decodes it won't be the last message anyway. It is then just the > beginning! I would then want to pass my call over there for example, > i.e. 5+ nights of stacking... > So: > *f = 17470.1000 Hz > Start time: 07.Dec.2017 21:30:00 UTC > Symbol period: 60 s > Characters: 1 > CRC bits: 10 > Coding 16K21A > Duration: 09:36 [hh:mm] > Antenna current: 1 A* > > 73, Stefan > > > Am 07.12.2017 22:01, schrieb Paul Nicholson: >> >> Stefan wrote: >> >> > Today i'd like to try that first east to west VLF TA >> > transmission. Let's try: >> >> > f = 17470.1000 Hz >> > Start time: 07.Dec.2017 22:00:00 UTC >> > Symbol period: 60 s >> > Characters: 1 >> > CRC bits: 6 >> > Coding 16K21A >> >> That may decode in one attempt if lucky, but likely two >> transmissions will be needed. If it does decode, then >> the chance of it being the correct decode from random >> noise is 0.02 %. >> >> Can you run until 08:08 UT with CRC 12 and the other >> settings the same? A gain of 0.74 dB which will make >> a good difference. And if it decodes, the chance of >> a random correct decode is only 0.0004 %. >> >> I hope the weather doesn't spoil the transmission, but >> if you keep trying, you are sure to succeed. >> >> -- >> Paul Nicholson >> -- >> --------------060805000807020107050605 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Paul, VLF,

Now there was the carrier during the whole night with 1.2 A . Do you have some recommendations for me regarding the best time window for that path?

I would like to pass one character over there without stacking. It doesn't matter to run the same message again. Maybe it will decode in that night on its own. But then it would certainly work when stacking is used.
So if there is no great imrpovement to be expected from different parameter settings, especially a longer transmission time, then i would simply run the same message again as stated below. I will do so, except you give me some convincing recommendations to start a new run.

Ah and it would be interesting to see a spectrum peak from the last night, from Mikes RX and from yours! I know it is your world you are operating in, so it is just a marginal effort to produce the peak i would assume :-) And it is a clear contribution for the overall activity on the band.

The 1.2 A carrier will then continue until 21:30 UTC and will go over into the BPSK then...

73, Stefan


Am 07.12.2017 22:16, schrieb DK7FC:
45 minutes left before the message starts. I can change to CRC 12 but 08:08 UTC means that about the last 90 minutes are running in daylight here.
Let me go to CRC 10, that's 9 hours and 36 minutes. And i'm starting 30 minutes earlier.
If it decodes it won't be the last message anyway. It is then just the beginning! I would then want to pass my call over there for example, i.e. 5+ nights of stacking...
So:
f = 17470.1000 Hz
Start time: 07.Dec.2017  21:30:00 UTC
Symbol period: 60 s
Characters: 1
CRC bits: 10
Coding 16K21A
Duration: 09:36 [hh:mm]
Antenna current: 1 A

73, Stefan


Am 07.12.2017 22:01, schrieb Paul Nicholson:

Stefan wrote:

> Today i'd like to try that first east to west VLF TA
> transmission. Let's try:

> f = 17470.1000 Hz
> Start time: 07.Dec.2017  22:00:00 UTC
> Symbol period: 60 s
> Characters: 1
> CRC bits: 6
> Coding 16K21A

That may decode in one attempt if lucky, but likely two
transmissions will be needed.  If it does decode, then
the chance of it being the correct decode from random
noise is 0.02 %.

Can you run until 08:08 UT with CRC 12 and the other
settings the same?  A gain of 0.74 dB which will make
a good difference.  And if it decodes, the chance of
a random correct decode is only 0.0004 %.

I hope the weather doesn't spoil the transmission, but
if you keep trying, you are sure to succeed.

--
Paul Nicholson
--

--------------060805000807020107050605--