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 w7TCHiwF018961 for ; Wed, 29 Aug 2018 14:17:45 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1fuzKx-00024T-8b for rs_out_1@blacksheep.org; Wed, 29 Aug 2018 13:12:39 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1fuzKw-00024K-QG for rsgb_lf_group@blacksheep.org; Wed, 29 Aug 2018 13:12:38 +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 1fuzKv-00088R-24 for rsgb_lf_group@blacksheep.org; Wed, 29 Aug 2018 13:12:37 +0100 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 5E3AE21089 for ; Wed, 29 Aug 2018 14:12:35 +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=1535544755; bh=c+Dy8m1G2UE5vj7dpMUExJCMYli9ft03Ip98S2hQX7U=; h=Date:From:To:Subject:From; b=P9i+Fj3VN3Gi8Mr3HsV8w2429MJHVGagoBE2Q706BG1FCK/791zQLMU27uB63jxiz KfBUtY0YmaI4SR/JhivE3cXwqvijbHzi1GqX4v4bU+jYXbPJ82zYOHDQrOnwCsPd7D XUmINMqlR0AgCfWg/qhWn0MItantS/1Sa3PEgj1OxWTuQyWiwAX1hGoZwlEBtO/yzN 4aAl73TUJyQafJKirNW/FtrVORyA2NN8m7gCymlOnqkYnkACJmyNDeN3NhFqphqw+d tWmVUuTJZRSXVwPqPhN4tFkJ90rpIYBWZpSX9fwUrP2CELyLHPfZNnVNpFhbLrfa2b WMnO/rNQPYF9w== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 420kyp4ztCz9rxH for ; Wed, 29 Aug 2018 14:12:32 +0200 (CEST) Message-ID: <5B868DB0.4080209@posteo.de> Date: Wed, 29 Aug 2018 14:12:32 +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: <1658523aabb-1ec0-b2@webjasstg-vab44.srv.aolmail.net> In-Reply-To: <1658523aabb-1ec0-b2@webjasstg-vab44.srv.aolmail.net> 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: PS: Ah, you decoded the message. That's fine because i didn't know yet if all worked well. What was the carrier S/N? 73, Stefan Am 29.08.2018 12:03, schrieb Markus Vester: > Hi Stefan and Edgar, > > I am still deeply impressed by your groundbreaking work. With close to > 12 dB SNR after three nights, it looks like you could chat at a rate > of one character per day. > > The Excel plots are a nice way to observe the carrier with different > integration times and optimize time and bandwidth. It looks like there > is another weaker maximum after 21 UT, shortly after sunrise in Hobart > (now 20:41 UT). > For a more intuitive interpretation, I would suggest to plot the > middle of the integration time rather than the start time on the x > axis, i.e. offset each curve to the right by half the duration. Then > all curves should more or less peak at the time of a propagation > maximum. There may also be a minor offset in the SNR scale because the > noise power is slightly underestimated due to rolloff of SpecLab's > decimation filter, I think the carrier SNR is really about 0.8 dB > lower than indicated on the y axis. > > The NWC phase plot at DL0AO shows a negative phase slope around -45° > per hour, so it may be worth to also plot SNR with a small negative > frequency offset (~ -35 uHz), possibly gaining a bit more at long > integration times. > > After decoding your message, I have set up the DL0AO 17.47 kHz > instance to unspread the PSK, so it may be used as a local control of > transmit phase and sequence timing. > > Good luck! > Markus > > > -----Ursprüngliche Mitteilung----- > Von: DK7FC > An: rsgb_lf_group > Verschickt: Mo, 27. Aug 2018 15:12 > Betreff: Re: VLF: New experiments on 17.47 kHz planned... > > Hi VLF, > > After transmitting carriers for the last 5 days, there are 3 good days > to stack, the others were noisy. > The resulting SNR via start time plot for different carrier length is > attached. With some uncertainty we can say that these days the ideal > start time for the path from DL to VK7 is 17:50 UTC and the message > duration should be between 2.5...3 hours. > > [...] 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: 3ecbf20a510e9846bb1bdaf7e0334c65 Subject: Re: VLF: New experiments on 17.47 kHz planned... Content-Type: multipart/alternative; boundary="------------080705040804020308060905" 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. --------------080705040804020308060905 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit PS: Ah, you decoded the message. That's fine because i didn't know yet if all worked well. What was the carrier S/N? 73, Stefan Am 29.08.2018 12:03, schrieb Markus Vester: > Hi Stefan and Edgar, > > I am still deeply impressed by your groundbreaking work. With close to > 12 dB SNR after three nights, it looks like you could chat at a rate > of one character per day. > > The Excel plots are a nice way to observe the carrier with different > integration times and optimize time and bandwidth. It looks like there > is another weaker maximum after 21 UT, shortly after sunrise in Hobart > (now 20:41 UT). > For a more intuitive interpretation, I would suggest to plot the > middle of the integration time rather than the start time on the x > axis, i.e. offset each curve to the right by half the duration. Then > all curves should more or less peak at the time of a propagation > maximum. There may also be a minor offset in the SNR scale because the > noise power is slightly underestimated due to rolloff of SpecLab's > decimation filter, I think the carrier SNR is really about 0.8 dB > lower than indicated on the y axis. > > The NWC phase plot at DL0AO shows a negative phase slope around -45° > per hour, so it may be worth to also plot SNR with a small negative > frequency offset (~ -35 uHz), possibly gaining a bit more at long > integration times. > > After decoding your message, I have set up the DL0AO 17.47 kHz > instance to unspread the PSK, so it may be used as a local control of > transmit phase and sequence timing. > > Good luck! > Markus > > > -----Ursprüngliche Mitteilung----- > Von: DK7FC > An: rsgb_lf_group > Verschickt: Mo, 27. Aug 2018 15:12 > Betreff: Re: VLF: New experiments on 17.47 kHz planned... > > Hi VLF, > > After transmitting carriers for the last 5 days, there are 3 good days > to stack, the others were noisy. > The resulting SNR via start time plot for different carrier length is > attached. With some uncertainty we can say that these days the ideal > start time for the path from DL to VK7 is 17:50 UTC and the message > duration should be between 2.5...3 hours. > > This evening i'm going to start an attempt for a 2 character EbNaut > message. With some luck, just 2 days, i.e. 2 stacks will be enough to > get a clear decode. > > *f = 17470.1000 Hz > Start time: 27.Aug.2018 17:50:00 UTC (daily) > Symbol period: 12 s > Characters: 2 > CRC bits: 23 > Coding 16K21A > Duration: 02:56 [hh:mm] > Antenna current: 1.2 A* > > > 73, Stefan > > > > > Am 24.08.2018 14:02, schrieb DK7FC: > > Hi Edgar, > > Thanks for the spectrogram showing JXN nicely! Here i'm watching > NWC but the SNR is much lower, probably due to the strong QRN we > still have in late August... > I'm going to calculate the weighting factors for the stacking > based on the noise amplitude from 18...21 UTC. And obviously it is > not necessary to transmit until 0 UTC, so i will stop an hour > earlier from now on. > > Your SpecLab settings are fine as they are. There is no advantage > from a shorter and wider FFT. The observed spectrum width > currently allows to display more than 2000 FFT bins centered on > the TX frequency, allowing to display enough noise arround the > peak to demonstrate that the peak is most unlikely a by-chance peak... > > Thanks for last nights txt file. We can produce a first stack from > the two days. Last night is weighted by -1.3 dB. The result is > attached. We can already see a peak of 11.3 dB SNR, not > unrealistic but still not significant enough. The spectrum peak > produced from the suggestion of the Excel plot (Start 17:50 UTC, > duration 2 hours) is attached as well. It shows a higher SNR, > which depends on the noise floor calculation (0 dB line). I need > to work on this but anyway the peak looks good relative to the > noise already. > > Another carrier will follow tonite. > > 73, Stefan > > > > Am 23.08.2018 23:40, schrieb Edgar: > > Hi Stefan, > > Based on the past two days signal from JXN, would it improve > the chance of detecting the carrier if the "FFT window time > (length)" matched the time when the signal is at maximum? > > The FFT length is now 8.847 hours. The period when JXN signal > is white is about 1.5 hours. > > The FFT bin width would be wider, and a larger percentage of > bins would have a stronger signal. > > > --------------080705040804020308060905 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit PS: Ah, you decoded the message. That's fine because i didn't know yet if all worked well. What was the carrier S/N?

73, Stefan

Am 29.08.2018 12:03, schrieb Markus Vester:
Hi Stefan and Edgar,

I am still deeply impressed by your groundbreaking work. With close to 12 dB SNR after three nights, it looks like you could chat at a rate of one character per day.

The Excel plots are a nice way to observe the carrier with different integration times and optimize time and bandwidth. It looks like there is another weaker maximum after 21 UT, shortly after sunrise in Hobart (now 20:41 UT).
For a more intuitive interpretation, I would suggest to plot the middle of the integration time rather than the start time on the x axis, i.e. offset each curve to the right by half the duration. Then all curves should more or less peak at the time of a propagation maximum. There may also be a minor offset in the SNR scale because the noise power is slightly underestimated due to rolloff of SpecLab's decimation filter, I think the carrier SNR is really about 0.8 dB lower than indicated on the y axis.

The NWC phase plot at DL0AO shows a negative phase slope around -45° per hour, so it may be worth to also plot SNR with a small negative frequency offset (~ -35 uHz), possibly gaining a bit more at long integration times.

After decoding your message, I have set up the DL0AO 17.47 kHz instance to unspread the PSK, so it may be used as a local control of transmit phase and sequence timing.
 
Good luck!
Markus


-----Ursprüngliche Mitteilung-----
Von: DK7FC <selberdenken@posteo.de>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Mo, 27. Aug 2018 15:12
Betreff: Re: VLF: New experiments on 17.47 kHz planned...

Hi VLF,

After transmitting carriers for the last 5 days, there are 3 good days to stack, the others were noisy.
The resulting SNR via start time plot for different carrier length is attached. With some uncertainty we can say that these days the ideal start time for the path from DL to VK7 is 17:50 UTC and the message duration should be between 2.5...3 hours.

This evening i'm going to start an attempt for a 2 character EbNaut message. With some luck, just 2 days, i.e. 2 stacks will be enough to get a clear decode.

f = 17470.1000 Hz
Start time: 27.Aug.2018  17:50:00 UTC (daily)
Symbol period: 12 s
Characters: 2
CRC bits: 23
Coding 16K21A
Duration: 02:56 [hh:mm]
Antenna current: 1.2 A



73, Stefan




Am 24.08.2018 14:02, schrieb DK7FC:
Hi Edgar,

Thanks for the spectrogram showing JXN nicely! Here i'm watching NWC but the SNR is much lower, probably due to the strong QRN we still have in late August...
I'm going to calculate the weighting factors for the stacking based on the noise amplitude from 18...21 UTC. And obviously it is not necessary to transmit until 0 UTC, so i will stop an hour earlier from now on.

Your SpecLab settings are fine as they are. There is no advantage from a shorter and wider FFT. The observed spectrum width currently allows to display more than 2000 FFT bins centered on the TX frequency, allowing to display enough noise arround the peak to demonstrate that the peak is most unlikely a by-chance peak...

Thanks for last nights txt file. We can produce a first stack from the two days. Last night is weighted by -1.3 dB. The result is attached. We can already see a peak of 11.3 dB SNR, not unrealistic but still not significant enough. The spectrum peak produced from the suggestion of the Excel plot (Start 17:50 UTC, duration 2 hours) is attached as well. It shows a higher SNR, which depends on the noise floor calculation (0 dB line). I need to work on this but anyway the peak looks good relative to the noise already.

Another carrier will follow tonite.

73, Stefan



Am 23.08.2018 23:40, schrieb Edgar:
Hi Stefan,

Based on the past two days signal from JXN, would it improve the chance of detecting the carrier if the "FFT window time (length)" matched the time when the signal is at maximum?

The FFT length is now 8.847 hours. The period when JXN signal is white is about 1.5 hours.

The FFT bin width would be wider, and a larger percentage of bins would have a stronger signal.



--------------080705040804020308060905--