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 vB7L56cp002693 for ; Thu, 7 Dec 2017 22:05:07 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eN3G6-00060m-TN for rs_out_1@blacksheep.org; Thu, 07 Dec 2017 20:59:06 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eN3G6-00060d-C6 for rsgb_lf_group@blacksheep.org; Thu, 07 Dec 2017 20:59:06 +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 1eN3G2-0003pH-Rm for rsgb_lf_group@blacksheep.org; Thu, 07 Dec 2017 20:59:05 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id DFDC420DF3 for ; Thu, 7 Dec 2017 21:59:01 +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=1512680341; bh=mB1d2McMWIa3lGiZZCPsHaxFj2X9p9aM2/7OYG04X24=; h=Date:From:To:Subject:From; b=YxMJwYKtjJ0cNhmqD7TN2nW5EVKz52sfTOcZjEleKhpo9vRbXO71gV3Y9Lo44epIA VpIEPc3QlSbQmx+yCdjL3n/q7sI/VZldt+OJOMIpqYnoTFPq728h0Sb9FQGUrTvPxx YB00gsCHyc6Fke8VFfVDob5L5V9MmEktrX2kdG7aGNPa+jyNlC6lxOkjH3PyuwyK3N xej5iw52/VmeoVut/2HIsjGbAarWdnlpYw0JCE8zJEfmBOuwuSriAM37vNcgH2J1Ng VPZh0jTA5ffTIWGhwoOBZaHcTATECZUaYae4yetXdD7m0Cx52nZf3jyvKtQF4ZtAj5 VkNXvZ61Xo1cQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3yt7BY38Zbz9rxG for ; Thu, 7 Dec 2017 21:59:01 +0100 (CET) Message-ID: <5A29AB95.3070400@posteo.de> Date: Thu, 07 Dec 2017 21:59:01 +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> <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> <00f101d36f83$8b02c5d0$a1085170$@comcast.net> <39d3d920-05d8-4172-f58a-4914f8f66bc1@abelian.org> <6e937a83-7603-fa2e-014e-8d52af427aa1@abelian.org > <010c01d36f96$a8117410$f8345c30$@comcast.net> In-Reply-To: <010c01d36f96$a8117410$f8345c30$@comcast.net> 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 Jim, Paul, Am 07.12.2017 21:04, schrieb hvanesce@comcast.net: > Receiver is at 38.915547, -77.124948 > Or FM18KV59AS :-) As Paul suggested, i would agree that recording the audio is the best you can do. Later you can try to create different spectrograms or try to get an EbNaut decode. Record in stereo, with the PPS pulses on the other channel. If you are using NMEA+PPS this would be ideal. Otherwise you can note the start time and set it manually later. [...] 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: b4085bc26841e34d79a2f3beb8f287b1 Subject: Re: VLF: TA east to west? Content-Type: multipart/alternative; boundary="------------030904030604030202030706" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,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. --------------030904030604030202030706 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Jim, Paul, Am 07.12.2017 21:04, schrieb hvanesce@comcast.net: > Receiver is at 38.915547, -77.124948 > Or FM18KV59AS :-) As Paul suggested, i would agree that recording the audio is the best you can do. Later you can try to create different spectrograms or try to get an EbNaut decode. Record in stereo, with the PPS pulses on the other channel. If you are using NMEA+PPS this would be ideal. Otherwise you can note the start time and set it manually later. My signal is to weak to get a trace on a spectrogram in that distance but you could try to get a single spectrum peak by using a rectangular window (FFT register card) and select a FFT window time equal to the common night time of 8.5 hours. Then start that SpecLab instance at 22 UTC. After 8.5 hours you will get the first spectrum. With some luck you can see the strongest peak right on 17470.1000 Hz. > 8 hours raw data ~ 11 GB if I calculated correctly. 8 hours * 3600 sec/hour * 16 bit/sample * 48000 samples/sec * 2 channels = 44236800000 bit = 5529600000 byte = 5.15 GB Maybe you are referring to a sample rate of 96 kS/s, then your ~11 GB is correct. I'm not sure but i think i remember that i learned that 1 kB = 1024 B, not 1000 B. But i am not sure. > OK to use raw data from SpecLab running in Windows? Generating wav files (larger than 4 GB) works very well on SpecLab. > No need for EbNaut? > You can do that later. Paul wrote: > I'm able to log into Mike's VLF computer to extract raw signal. > I already wondered how you watch for a 17470 Hz signal from a 32 kS/s vorbis stream :-) Just for fun i'm watching Alpha F1 (11904.7619 Hz) from that stream in VA. It has 23 dB SNR in 424 uHz! 73, Stefan --------------030904030604030202030706 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi Jim, Paul,

Am 07.12.2017 21:04, schrieb hvanesce@comcast.net:
Receiver is at 38.915547, -77.124948
Or FM18KV59AS :-)

As Paul suggested, i would agree that recording the audio is the best you can do. Later you can try to create different spectrograms or try to get an EbNaut decode. Record in stereo, with the PPS pulses on the other channel. If you are using NMEA+PPS this would be ideal. Otherwise you can note the start time and set it manually later.

My signal is to weak to get a trace on a spectrogram in that distance but you could try to get a single spectrum peak by using a rectangular window (FFT register card) and select a FFT window time equal to the common night time of 8.5 hours. Then start that SpecLab instance at 22 UTC. After 8.5 hours you will get the first spectrum. With some luck you can see the strongest peak right on 17470.1000 Hz.

8 hours raw data ~ 11 GB if I calculated correctly.
8 hours * 3600 sec/hour * 16 bit/sample * 48000 samples/sec * 2 channels = 44236800000 bit = 5529600000 byte = 5.15 GB Maybe you are referring to a sample rate of 96 kS/s, then your ~11 GB is correct.
I'm not sure but i think i remember that i learned that 1 kB = 1024 B, not 1000 B. But i am not sure. 

OK to use raw data from SpecLab running in Windows?
Generating wav files (larger than 4 GB) works very well on SpecLab.
 No need for EbNaut?
You can do that later.

Paul wrote:
I'm able to log into Mike's VLF computer to extract raw signal.
I already wondered how you watch for a 17470 Hz signal from a 32 kS/s vorbis stream :-)
Just for fun i'm watching Alpha F1 (11904.7619 Hz) from that stream in VA. It has 23 dB SNR in 424 uHz!

73, Stefan --------------030904030604030202030706--