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 vBUDSNWp014442 for ; Sat, 30 Dec 2017 14:28:24 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eVH68-0003Pz-RL for rs_out_1@blacksheep.org; Sat, 30 Dec 2017 13:22:48 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eVH5l-0003Pq-4m for rsgb_lf_group@blacksheep.org; Sat, 30 Dec 2017 13:22:25 +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 1eVH5f-0007jC-LM for rsgb_lf_group@blacksheep.org; Sat, 30 Dec 2017 13:22:22 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id C9CD420E7D for ; Sat, 30 Dec 2017 14:22:15 +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=1514640137; bh=ktTGcIyUP5Cf4vCAAJlpG6f3ZK5HLM25czHXmVxdWXU=; h=Date:From:To:Subject:From; b=ktMGAZo0elHrh+oHkyBU1wu30n7V5B5Wmy/FPzkxyg9d8lV9UPEt7foWkQnqJK0gw ysRCnKL3oq2hRYM8CkC2vHFFKJOJOQYvIMl1GfHQdqajiMhXOoLUkkbHxhrZKAnAoN q3dzOiVhOvOu5blqD+r61UxIhSazioeET/6fiTpuyBmOpQu8n4H2i6JbCS0+pBcxz+ bEQDMaNVOTM5n2SAJGSduPiAVZWhfT35CLV7GxttJTf2k2vwIPUnDHA+V8xNDzuHNB oYlctVsYQp4BwkJ7TOYkLQitnLESToROPOoOafNxZefnYYZ9IW+2aLDekHIes2FJWn qruIWF+McI6Fw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3z83yt6XmMz9rxN for ; Sat, 30 Dec 2017 14:22:12 +0100 (CET) Message-ID: <5A479303.5010100@posteo.de> Date: Sat, 30 Dec 2017 14:22:11 +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: <2dbcd2a8-0109-41e4-c0ca-aada17f54de8@abelian.org> <5A31249C.2040307@posteo.de> <5A326AAE.7020808@posteo.de> <6b23a798-f28e-828c-bd8a-43ba8af0fb6a@abelian.org> <346e5dfe-da5f-79e9-c097-e3012a3b74bd@abelian.org> <5A344E83.3020308@posteo.de> <5A37BB18.4090806@posteo.de> <79b53aa1-0fa7-d02c-34bf-5b2e3b7bdddb@abelian.org> <5A381F2B.7000304@posteo.de> <3871624a-11dc-12b8-853c-8454840ca9ff@abelian.org> <5A398786.7000001@posteo.de> <5A398906.9000806@posteo.de> <6833b8ea-5cf8-809e-364e-a9f47e04bc44@abelian.org> <2572ce8a-49f7-fedb-98d3-6b3147b0d3eb@abelian.org> <9e41cc0f-dbc3-25e1-5413-38d00890d74c@abelian.org> <72b92016-13ba-d45d-61c3-d54f6c9c530f@abelian.org> <5A44C2CA.6020004@posteo.de> <5d959a0f-c16c-e1f4-f04e-738592c7ad40@abelian.org> <5A46627C.6040901@posteo.de> <03fc01d380e7$0dca0360$295e0a20$@comcast.net> In-Reply-To: <03fc01d380e7$0dca0360$295e0a20$@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: Thanks Jim, I would be helpful to understand what causes these phase variations. And in a next step it would be nice to learn how to predict / estimate the phase variation. This would allow to correct the phase, for getting a (valid) decode. But that is probably not easy at all and it would also rise the question if using 3rd party propagation data is allowed to get a valid decode at all... [...] 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 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 24b65a258fa7a3a87cfdaa03bb2f3176 Subject: Re: LF: VLF NA Ebnaut Content-Type: text/plain; charset=UTF-8; format=flowed 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=none 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by klubnl.pl id vBUDSNWp014442 Thanks Jim, I would be helpful to understand what causes these phase variations. And in a next step it would be nice to learn how to predict / estimate the phase variation. This would allow to correct the phase, for getting a (valid) decode. But that is probably not easy at all and it would also rise the question if using 3rd party propagation data is allowed to get a valid decode at all... 73 es HNY, Stefan Am 29.12.2017 21:53, schrieb hvanesce@comcast.net: > Stefan and Paul, > > I had been guessing issues in or near the receiver, as in your comments below, and the near field reference sounded like a great idea. > > I thought I would mention that on a few occasions I've been surprised by atypical phase variations on minutes or hours timescales for signals along similar paths, down the US east coast over land-water-land-water-land-water-land... paths at distances up to 1500 km or so, when concurrent signal phase in (for example) Florida (mostly water path) and inland (all land) at roughly similar SSW bearings looked stable. On one such occasion I checked phase sensitivity of the high-variability path (many land-water transitions) using LWPC, and compared with sensitivity of the mostly-water and all-land paths using LWPC. The LWPC comparison was qualitatively similar to the empirical comparison: high sensitivity of phase to ionospheric variations along the path with many land-water transitions. Guessing this is not the explanation for VO1NA-Forest night-to-night phase variations, but I thought I'd mention it, perhaps for future reference. I thought briefly about ice variations along the path but guessed that any ice would be far too thin to matter. > > Also thought I would mention that in general, for path lengths shorter than 1000 km or so, lower VLF frequencies generally have larger groundwave-skywave-interference phase variations on minutes/hours/diurnal timescales than do higher VLF frequencies, but this should not generally be a factor at 8270 Hz for distances much greater than 1000 km, i.e. not a likely factor on the VO1NA-Forest path. > > 73, > > Jim AA5BW > > > -----Original Message----- > From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of DK7FC > Sent: Friday, December 29, 2017 10:43 AM > To: rsgb_lf_group@blacksheep.org > Subject: Re: LF: VLF NA Ebnaut > > Am 29.12.2017 08:51, schrieb Paul Nicholson: > >> I've examined the software at Forest and all appears to be working >> fine, at least as well as my own. >> > OK Paul, thanks for working that out. > > A near field reference for testing the phase stability is certainly a good idea. It should be there all the time ideally. Then one could even correct the faulty segments. A safety redundance. > > >> If we see distant >> MSK phase changing (which we probably will), is it caused by >> the rx or the propagation? Alpha signals are a bit tricky >> to use when there are two transmitters interleaved in the signal being >> averaged. >> > In my Alpha RDF spectrogram, the colours (indicating the phase) are reproducing day by day quite nicely. There are 2 glitches. One is when the TX switches the phase at 0 clock Moscow time. The other glitch is at > 0 UTC. Then there is the slow change of the phase between day and night. > I am in another location and it is another path though. > > >> Perhaps just the weakness of the signal at Forest? >> Eb/N0 -0.1 = S/N 7.5 dB in the 30.6 uHz bandwidth in which the phase >> is measured. >> > Could be the reason. But you are comparing just 2 or 3 days. On my 1 character message at 17470.1 Hz there were no unexpected phase changes > > Another idea could be a damage in an electrical component in the high impedance preamp. Maybe a water drop that changes the capacity somewhere, leading to a phase shift. This would not affect the timing but the phase Just a guess. > > I find it most useful to get an overview of the system performance by looking on a 'wideband' spectrogram, covering e.g. 0...24 kHz and half a day or a day. You will immediately see if something changed, like the signal levels, the phase and timing and sample rate correction (when running an Alpha plot for example). Or you will see if a new QRM source appeared or disappeared. All this without a particular search for eventual errors, just the usual daily view on that spectrogram. I would feel blind without that :-) > > So in the end, is it propagation or not? For me it sound unlikely that it is propagation. On 17.4701 kHz, over such a distance, maybe. But not on 8270 Hz on the path between VO1NA and Mike. > Uuh, another strange idea: Maybe a faulty component in the preamp that changes the phase frequency dependently, like a capacitor moving the edge frequency of a LPF or HPF and changing the phase hereby? > > 73, Stefan > > > > >