Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_MED, RCVD_IN_SORBS_SPAM,SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 X-Spam-DCC: : mailn 1480; Body=2 Fuz1=2 Fuz2=2 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by lipkowski.org (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id v5AKT3MS024374 for ; Sat, 10 Jun 2017 22:29:04 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1dJmw2-0005Zs-D5 for rs_out_1@blacksheep.org; Sat, 10 Jun 2017 21:24:38 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1dJmvu-0005Zj-SN for rsgb_lf_group@blacksheep.org; Sat, 10 Jun 2017 21:24:30 +0100 Received: from omr-m001e.mx.aol.com ([204.29.186.1]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1dJmvq-0008Sv-TK for rsgb_lf_group@blacksheep.org; Sat, 10 Jun 2017 21:24:29 +0100 Received: from mtaomg-mbb02.mx.aol.com (mtaomg-mbb02.mx.aol.com [172.26.254.112]) by omr-m001e.mx.aol.com (Outbound Mail Relay) with ESMTP id A4F6738000B3 for ; Sat, 10 Jun 2017 16:24:24 -0400 (EDT) Received: from core-acb10h.mail.aol.com (core-acb10.mail.aol.com [172.27.24.10]) by mtaomg-mbb02.mx.aol.com (OMAG/Core Interface) with ESMTP id 735ED38000082 for ; Sat, 10 Jun 2017 16:24:23 -0400 (EDT) Received: from 188.192.95.60 by webprd-m70.mail.aol.com (10.74.71.88) with HTTP (WebMailUI); Sat, 10 Jun 2017 16:24:22 -0400 Date: Sat, 10 Jun 2017 16:24:23 -0400 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <15c93add89b-61e9-44cc@webprd-m70.mail.aol.com> MIME-Version: 1.0 X-MB-Message-Source: WebUI X-MB-Message-Type: User X-Mailer: JAS STD X-Originating-IP: [188.192.95.60] x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1497126264; bh=rzPWdrwyXeuv1S/qpcrsmrw7Uz/uWyxNx80G40GVqcI=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=wl8+ZzdPZM1MzZWGT02TT1B/o2nC9S421zXytRzkUMCju41/HrG2v+X1x3xQBKqci IcVbAMDVStH4MxBGaX6m8TsjBQvknd5nExHQQHjkN2PARZ/LfUDUdLdmaNegNyY0dC mX9f8mMtixPSyoUtqgnpFaam+3RmYkxjl3723Le4= x-aol-sid: 3039ac1afe70593c55775848 X-Scan-Signature: d7fcd9b75df8d1b09ddef9df028bd9ae Subject: ELF: ZEVS phase and frequency accuracy? Content-Type: multipart/alternative; boundary="----=_Part_20833_2000461598.1497126262937" 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 X-Scanned-By: MIMEDefang 2.75 Status: RO X-Status: X-Keywords: X-UID: 11942 ------=_Part_20833_2000461598.1497126262937 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I've been wondering whether the 82 Hz carrier from the ZEVS transmitter is = accurate and synchroneous to UTC. So I set up a colour spectrogram on the D= L0AO grabber http://df6nm.bplaced.net/dl0ao/VLFgrabber/vlfgrabber_dl0ao_test.htm (scroll down to near the bottom), which shows the phase with reference to a= 1pps harmonic on the other channel. The colour sequence is red-yellow-gree= n-blue for retarding ZEVS phase (unfortunately opposite to the way it's don= e on LoranView). During the last six hours, the colour has changed from red to green, indica= ting a 120=C2=B0 delay. This Looks like the carrier is ~ 20 uHz below 82 Hz= (-0.25 ppm, quite a large difference on a relative scale). I am asking mys= elf how it the transmit frequency is physically being steered, possibly "Al= exanderson-style" by setting the velocity of a rotating machine? If the fre= quency offset turns out to be real and stable, it could be a means for DX'e= rs to differentiate the real ZEVS signal from possible local receiver artif= acts. I wonder whether anyone else could verify the offset? On the other hand, I wouldn't yet rule out a diurnal propagation effect, ev= en though at a distance of less than a wavelength this should not produce s= uch a large phase change. There could also be local effects on the receive = site from variable humidity in the vegetation near the E-field probe.=20 So the big question is whether or not the phase trend will continue tonight= and tomorrow. Best 73, Markus (DF6NM) ------=_Part_20833_2000461598.1497126262937 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I've been wondering whether the 82 Hz carrier from the ZEVS transmit= ter is accurate and synchroneous to UTC. So I set up a colour spe= ctrogram on the DL0AO grabber
 http://df6nm.bplaced.net/d= l0ao/VLFgrabber/vlfgrabber_dl0ao_test.htm
(scroll down to near the botto= m), which shows the phase with reference to a 1pps harmonic on the oth= er channel. The colour sequence is red-yellow-green-blue for retarding ZEVS= phase (unfortunately opposite to the way it's done on LoranView).
=
During the last six hours, the colour has changed from red to green, in= dicating a 120=C2=B0 delay. This Looks like the carrier is ~ 20 uHz be= low 82 Hz (-0.25 ppm, quite a large difference on a relative scale). I= am asking myself how it the transmit frequency is physically being steered= , possibly "Alexanderson-style" by setting the velocity of a rotating = machine? If the frequency offset turns out to be real and stable,= it could be a means for DX'ers to differentiate the real ZEVS signal = from possible local receiver artifacts. I wonder whether anyone else c= ould verify the offset?

On the other hand, I wouldn't yet = rule out a diurnal propagation effect, even though at a distance of&nb= sp;less than a wavelength this should not produce such a large ph= ase change. There could also be local effects on the receive site from= variable humidity in the vegetation near the E-field probe. 

S= o the big question is whether or not the phase trend will continue ton= ight and tomorrow.

Best 73,
Markus (DF6NM)
------=_Part_20833_2000461598.1497126262937--