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 x1PL4G65026228 for ; Mon, 25 Feb 2019 22:04:18 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gyNAy-0004i1-NO for rs_out_1@blacksheep.org; Mon, 25 Feb 2019 20:48:37 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gyN7R-0004gv-F9 for rsgb_lf_group@blacksheep.org; Mon, 25 Feb 2019 20:44:57 +0000 Received: from resqmta-ch2-09v.sys.comcast.net ([2001:558:fe21:29:69:252:207:41]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gyN7F-0006t4-CW for rsgb_lf_group@blacksheep.org; Mon, 25 Feb 2019 20:44:46 +0000 Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id yIC8g0uAFQNsNyN7AgJVwG; Mon, 25 Feb 2019 20:44:40 +0000 X-DKIM-Result: Domain=comcast.net Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1551127480; bh=/bJdA6ak2GteWld31zz1o+VKtJgGliby2r2iod5PrmI=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=ddl/4ZSjkbQds5jPm6w4LZRpIbT52jX3BfR8kh6kRYLE2pqO5ZIL8zZ7iQ3y/aBBk QOzHHfiE2WVD3S3ttS4ImQ2ugH5OajTqeplVXCgiM9wqiLyVQP7cqBMKJj7jGG0YEq 9tMYsQ2bz7OxlWbQmwxYwN71fpr6TGUPUrCMAyi4ptB810eVvWct64/wxQzyN97lZN 5mlc5Do2V70jsEusbbeRSKp7ti4tAvL/99VwRT+bO0ExwIJCNDUuZGs3jUkWa5UZ3K pF2ceaJqs3M8tsoTtDYASY5D7kNCAc2XZAaRa8ov+j9bfc9ZL7c6aeUpRwz6jQooay jNetPc1aUpDmg== Received: from Owner ([IPv6:2601:140:8500:7f9f:d064:ad1a:5aee:318]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id yN78gVVu5FPHiyN79gx9Jv; Mon, 25 Feb 2019 20:44:40 +0000 X-Xfinity-VMeta: sc=0;st=legit From: To: References: <1341300776.3468000.1550834824126.ref@mail.yahoo.com> <1341300776.3468000.1550834824126@mail.yahoo.com> <5C7415E4.7090603@posteo.de> In-Reply-To: <5C7415E4.7090603@posteo.de> Date: Mon, 25 Feb 2019 15:44:31 -0500 Message-ID: <009101d4cd4a$ed8530f0$c88f92d0$@comcast.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGobIVDJBpFCMgFIgT2U/vkQCRSfQJ2rAPxAlojuM0CU/BCawFWV+ikpgXbfqA= Content-Language: en-us X-Spam-Score: -0.7 (/) 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: Stefan, Congratulations on this latest milestone. 57.6 km at 470 Hz at an SNR that would have supported 6 bits of information with 90% of battery energy unused is impressive; nice work. Using r^2.5 extinction it seems like another 13 dB would reach the far field. Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [2001:558:fe21:29:69:252:207:41 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (hvanesce[at]comcast.net) 0.0 T_KAM_HTML_FONT_INVALID BODY: Test for Invalidly Named or Formatted Colors in HTML 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 6ae4eec5875a1b41a36d2a35c03bf59e Subject: LF: RE: 470.1 Hz detected in 57.6 km distance Content-Type: multipart/alternative; boundary="----=_NextPart_000_0092_01D4CD21.04B199F0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.1 required=5.0 tests=HTML_30_40,HTML_MESSAGE, NO_REAL_NAME 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 multipart message in MIME format. ------=_NextPart_000_0092_01D4CD21.04B199F0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Stefan, =20 Congratulations on this latest milestone. 57.6 km at 470 Hz at an SNR = that would have supported 6 bits of information with 90% of battery = energy unused is impressive; nice work. =20 Using r^2.5 extinction it seems like another 13 dB would reach the far = field. =20 I wonder if some fine-tuning of distance could be helpful in that case. = I=E2=80=99m not sure how to easily calculate modal null separation = distances at wavelengths greater than ionospheric height, but by = extrapolation from 3 kHz it would seem that at 470 Hz, ten nulls (from = modes 1 through 5) might be fairly closely spaced near a 110 km target = location, such that a small increase or decrease in receiver distance = from transmitter could move the receiver toward a peak in the = interference pattern. =20 I=E2=80=99m not sure how you changed receiver locations in the past so = perhaps in this case you can=E2=80=99t easily move the receiver. =20 Your 2-hour spectral plot is a welcome sight. =20 73, =20 Jim AA5BW =20 =20 =20 From: owner-rsgb_lf_group@blacksheep.org = [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of DK7FC Sent: Monday, February 25, 2019 11:21 AM To: rsgb_lf_group@blacksheep.org Subject: ULF: 470.1 Hz detected in 57.6 km distance =20 Hi ULF friends,=20 Last Friday i run another carrier transmission on my 900m long ground = loop antenna. It was the second experiment at 470.1 Hz. The last = experiment failed because just a few 1/10 dB were missed to reach the 14 = dB SNR level which is the criterium for a valid detection. During the last week i managed to reduce the background QRM on the E = field significantly (at least 10 dB) in that frequency range by changing = the ground connection on the RX system, so it was an EMC issue. In the recent experiment the DC measurement showed 1 A at 58 V, so the = loop loss was just 58 Ohm, which is one of the best values so far. Conecting the PA to the LiFePo4 accu produced 620 W RF power and 3 A = antenna current (!) in the first moment. But the DC/DC converter became = a bit to warm and i (thought) had enough time so i reduced the input = voltage. The power dropped to 460 W and so the antenna current during = the experiment was 2.75 A. The carrier started at 14:50 UTC and was on = the air for 2.5 hours! It was a quiet day and so i decided spontaneously to do the experiment. = But i've been at work in the morning and so i was late, a bit to late = actually, since the band already opened and the QRN increased during the = experiment. Who knows what happened to the phase over that path. The = only RX station detecting the signal was my own tree in 57.6 km = distance. Due to the rising QRN the last 30 minutes did not help to = rise the SNR of the postprocessed spectrum peak. But 2 hours were fine = to get a clear copy! Usually i have to ways to determine the final SNR: One is to read the = output of the EbNaut decoder decoding a '*' message. The ouput, if using = the -f15 -f16 -M'*****' options, then shows the carrier S/N directly. The other method is a script that calculates the SNR dB value based on = the spectrum peak and 0 dB noise level. This 0 dB noise level = calculation is done according to the description in SpectumLab's help = sites. Here is the quote: "The definition of noise levels is not easy. Here is the basic algorithm = of the 'noise' function:=20 1. An array of amplitudes (usually dB values) from the last FFT = calculation is sorted into order of increasing amplitude.=20 2. The amplitude of the lower quartile value (for example bin number 256 = in a sorted set of 1024 points) PLUS 3dB is then returned as an estimate = of the mean noise level.=20 This technique automatically throws away very high values (strong = signals) that would otherwise affect the result." This technique is used in my script. I find the result adequate, the 0 = dB level is visually in the center of the noise. But sometimes the SNR = statements are a bit different between my script and the result of the = EbNaut program. Maybe it is due to the fact that i am calculating the = mean level based on just 1000 bins arround the spectrum peak, and EbNaut = watches a higher bandwidth, which may contain more QRM peaks that rise = the mean noise baseline? That may explain why my script whows an SNR of 18.2 dB whereas the = EbNaut decoder says it is an SNR of 16.17 dB. Anyway, well above 14 dB. The signal was strong enough, it could have carried a 6 character EbNaut = message. Attached is a 424 uHz spectrogram showing a short carrier trace just = before the high QRN sets in. Also attached, a single spectrum peak = detection and the result for an EbNaut message (showing the carrier = S/N). So, it is the first amateur radio signal on the 638 km band detected = over such a distance i think. 73, Stefan ------=_NextPart_000_0092_01D4CD21.04B199F0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Stefan,

 

Congratulations on this latest milestone. 57.6 km at 470 Hz at an SNR = that would have supported 6 bits of information with 90% of battery = energy unused is impressive; nice work.

 

Using r^2.5 extinction it seems like another 13 dB would reach the = far field.

 

I wonder if some fine-tuning of distance could be helpful in that = case. I=E2=80=99m not sure how to easily calculate modal null separation = distances at wavelengths greater than ionospheric height, but by = extrapolation from 3 kHz it would seem that at 470 Hz, ten nulls (from = modes 1 through 5) might be fairly closely spaced near a 110 km target = location, such that a small increase or decrease in receiver distance = from transmitter could move the receiver toward a peak in the = interference pattern.

 

I=E2=80=99m not sure how you changed receiver locations in the past = so perhaps in this case you can=E2=80=99t easily move the = receiver.

 

Your 2-hour spectral plot is a welcome sight.

 

73,

 

Jim AA5BW

 

=C2=A0

 

From: owner-rsgb_lf_group@blacksheep.org = [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of = DK7FC
Sent: Monday, February 25, 2019 11:21 = AM
To: rsgb_lf_group@blacksheep.org
Subject: ULF: = 470.1 Hz detected in 57.6 km = distance

 

Hi ULF = friends,

Last Friday i run another carrier transmission on my = 900m long ground loop antenna. It was the second experiment at 470.1 = Hz. The last experiment failed because just a few 1/10 dB were = missed to reach the 14 dB SNR level which is the criterium for a valid = detection.
During the last week i managed to reduce the background = QRM on the E field significantly (at least 10 dB) in that frequency = range by changing the ground connection on the RX system, so it was an = EMC issue.

In the recent experiment the DC measurement showed 1 A = at 58 V, so the loop loss was just 58 Ohm, which is one of the best = values so far.

Conecting the PA to the LiFePo4 accu produced 620 = W RF power and 3 A antenna current (!) in the first moment. But the = DC/DC converter became a bit to warm and i (thought) had enough time so = i reduced the input voltage. The power dropped to 460 W and so = the antenna current during the experiment was 2.75 A. The carrier = started at 14:50 UTC and was on the air for 2.5 hours!

It was a = quiet day and so i decided spontaneously to do the experiment. But i've = been at work in the morning and so i was late, a bit to late actually, = since the band already opened and the QRN increased during the = experiment. Who knows what happened to the phase over that path. The = only RX station detecting the signal was my own tree in 57.6 km = distance.  Due to the rising QRN the last 30 minutes did not = help to rise the SNR of the postprocessed spectrum peak. But 2 hours = were fine to get a clear copy!

Usually i have to ways to = determine the final SNR: One is to read the output of the EbNaut decoder = decoding a '*' message. The ouput, if using the -f15 -f16 -M'*****' = options, then shows the carrier S/N directly.
The other method is a = script that calculates the SNR dB value based on the spectrum peak and 0 = dB noise level. This 0 dB noise level calculation is done according to = the description in SpectumLab's help sites. Here is the = quote:
"The definition of noise levels is not easy. Here is = the basic algorithm of the 'noise' function:

  1. An array of amplitudes (usually dB values) from the last = FFT calculation is sorted into order of increasing amplitude. =
  2. The amplitude of the lower quartile value (for example = bin number 256 in a sorted set of 1024 points) PLUS 3dB is then returned = as an estimate of the mean noise level. =

This technique automatically throws away = very high values (strong signals) that would otherwise affect the = result."

This technique is = used in my script. I find the result adequate, the 0 dB level is = visually in the center of the noise. But sometimes the SNR statements = are a bit different between my script and the result of the EbNaut = program. Maybe it is due to the fact that i am calculating the mean = level based on just 1000 bins arround the spectrum peak, and EbNaut = watches a higher bandwidth, which may contain more QRM peaks that rise = the mean noise baseline?
That may explain why my script whows an = SNR of 18.2 dB whereas the EbNaut decoder says it is an SNR of = 16.17 dB. Anyway, well above 14 dB.

The signal was strong = enough, it could have carried a 6 character EbNaut = message.

Attached is a 424 uHz spectrogram showing a short = carrier trace just before the high QRN sets in. Also attached, a single = spectrum peak detection and the result for an EbNaut message (showing = the carrier S/N).


So, it is the first amateur radio signal on = the 638 km band detected over such a distance i = think.


73, Stefan

------=_NextPart_000_0092_01D4CD21.04B199F0--