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 v9L8qP7Y007219 for ; Sat, 21 Oct 2017 10:52:28 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1e5pJA-0006l4-OM for rs_out_1@blacksheep.org; Sat, 21 Oct 2017 09:39:04 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1e5pHM-0006kk-7U for rsgb_lf_group@blacksheep.org; Sat, 21 Oct 2017 09:37:12 +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.89) (envelope-from ) id 1e5pHF-0001KC-LZ for rsgb_lf_group@blacksheep.org; Sat, 21 Oct 2017 09:37:07 +0100 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id CB0BE20A02 for ; Sat, 21 Oct 2017 10:37:02 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3yJwy60SrKz1090 for ; Sat, 21 Oct 2017 10:37:01 +0200 (CEST) Message-ID: <59EB072D.4060007@posteo.de> Date: Sat, 21 Oct 2017 10:37:01 +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: <15f3640d1bf-c10-10621@webjas-vac109.srv.aolmail.net> <59E9451E.80901@posteo.de> <59E945D8.30101@posteo.de> <59E9FF29.5000206@posteo.de> <59EA03F4.2040700@posteo.de> In-Reply-To: <59EA03F4.2040700@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: ...the carrier was unintentionally run on 5170.1 Hz since 4 UTC. It was changed to 5170.005 Hz at 8:26 UTC. The transmission at night was very stable. Next, the same transmission at night and the carrier afterwards, jumping to 5170.005 Hz at 4 UTC... [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: ead411ce91f9601ce3974c7575797436 Subject: Re: VLF: 300 mA on 5170 Hz Content-Type: multipart/alternative; boundary="------------030206060209000900070403" 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. --------------030206060209000900070403 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ...the carrier was unintentionally run on 5170.1 Hz since 4 UTC. It was changed to 5170.005 Hz at 8:26 UTC. The transmission at night was very stable. Next, the same transmission at night and the carrier afterwards, jumping to 5170.005 Hz at 4 UTC... 73, Stefan Am 20.10.2017 16:11, schrieb DK7FC: > Sorry, that was false: > New: > > *f = 5170.1000 Hz > Start time: 20.October.2017 16:00:00 UTC (daily) > Symbol period: 180 s > Characters: 1 > CRC bits: 6 > Coding 8K19A > Duration: 12h > Antenna current: 300 mA* > > Tomorrow there will be a carrier transmission between 4 UTC and 16 UTC. > > 73, Stefan > > Am 20.10.2017 15:50, schrieb DK7FC: >> ...there have been some thunderstorms again last night in a range of >> < 2000 km. Arround 3 UTC the cancellation effects were quite >> expressed. Within 200 Hz or so, the SNR can change by 10 dB. It looks >> like the dSNR/df is most expressed in the range arround 5 kHz. >> A working propagation model would be useful for us. So far we can >> just try to experiment with multi frequency carriers to get an >> impression. >> >> Let's try a short message at night. Maybe it is a bit to optimistic >> to expect that it will be decoded by Alex. But why not. We learned >> that the impossible is possible. I'm not sure about the stability of >> the antenna current during rain, we will see... >> --------------030206060209000900070403 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit ...the carrier was unintentionally run on 5170.1 Hz since 4 UTC. It was changed to 5170.005 Hz at 8:26 UTC.
The transmission at night was very stable. Next, the same transmission at night and the carrier afterwards, jumping to 5170.005 Hz at 4 UTC...

73, Stefan

Am 20.10.2017 16:11, schrieb DK7FC:
Sorry, that was false:
New:

f = 5170.1000 Hz
Start time: 20.October.2017  16:00:00 UTC (daily)
Symbol period: 180 s
Characters: 1
CRC bits: 6
Coding 8K19A
Duration: 12h
Antenna current: 300 mA

Tomorrow there will be a carrier transmission between 4 UTC and 16 UTC.

73, Stefan

Am 20.10.2017 15:50, schrieb DK7FC:
...there have been some thunderstorms again last night in a range of < 2000 km. Arround 3 UTC the cancellation effects were quite expressed. Within 200 Hz or so, the SNR can change by 10 dB. It looks like the dSNR/df is most expressed in the range arround 5 kHz.
A working propagation model would be useful for us. So far we can just try to experiment with multi frequency carriers to get an impression.

Let's try a short message at night. Maybe it is a bit to optimistic to expect that it will be decoded by Alex. But why not. We learned that the impossible is possible. I'm not sure about the stability of the antenna current during rain, we will see...

--------------030206060209000900070403--