Return-Path: X-Spam-DCC: paranoid 1290; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,HTML_50_60, HTML_MESSAGE autolearn=unavailable version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id sBCGIIdS010128 for ; Fri, 12 Dec 2014 17:18:18 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1XzSpD-00021b-7k for rs_out_1@blacksheep.org; Fri, 12 Dec 2014 16:12:15 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1XzSpC-00021S-Sy for rsgb_lf_group@blacksheep.org; Fri, 12 Dec 2014 16:12:14 +0000 Received: from omr-m2.mx.aol.com ([64.12.133.13]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84) (envelope-from ) id 1XzSpA-0000Uz-Da for rsgb_lf_group@blacksheep.org; Fri, 12 Dec 2014 16:12:13 +0000 Received: from mtaout-maa01.mx.aol.com (mtaout-maa01.mx.aol.com [172.26.222.141]) by omr-m2.mx.aol.com (Outbound Mail Relay) with ESMTP id 580463800017B for ; Fri, 12 Dec 2014 11:12:10 -0500 (EST) Received: from White (ipb21bee4a.dynamic.kabel-deutschland.de [178.27.238.74]) by mtaout-maa01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 86A423800009F for ; Fri, 12 Dec 2014 11:12:07 -0500 (EST) Message-ID: <948E5F99C2B7422D880EDAB26B718131@White> From: "Markus Vester" To: References: <5489EFBC.3050401@abelian.org> <5489F474.4030904@abelian.org> <5489FA44.3010709@abelian.org> <548AA644.4030707@abelian.org> <01b701d0161e$c6a4bf60$53ee3e20$@comcast.net> Date: Fri, 12 Dec 2014 17:12:04 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20140625; t=1418400730; bh=wB5MuyvraGEiTIXy6CO5795CfAJiQun1fDWlrAnJhHE=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=wL7o+ygxwVaskRQkKn0o1RvViFksS3GacsJ6E8/zjW+X9IFiK9IhVXWilCwXxry6m nd7lNmQ9EbP49WVh1DAVnzXvFv9P+7/v8o+evYv75XAf7ZJ0D73PrnE3SwMO26PmEZ grXQiSOUmDfRYxRgPjVXcueSbW0tN6A+hRKqFR/A= x-aol-sid: 3039ac1ade8d548b13d74c9a X-AOL-IP: 178.27.238.74 X-Scan-Signature: 58ba09640deeac370be75328ed1b0fef Subject: Re: VLF: 8819.9 Hz in Virginia? Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01D0162E.C0B1D150" 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.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 1469 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_000B_01D0162E.C0B1D150 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Jim, >my spectrogram data was captured at ~ 1mHz resolution (715 uHz bin = width),=20 Your resolution is actually similar enough to Paul's 833 uHz bins, and = the excursion on the unid signal (around 0.010 Hz, not uHz) would be = clearly visible. Could you post your spectrogram around 16 UT yesterday? = Best 73, Markus From: hvanesce@comcast.net=20 Sent: Friday, December 12, 2014 4:17 PM To: rsgb_lf_group@blacksheep.org=20 Subject: RE: VLF: 8819.9 Hz in Virginia? Paul, I've been monitoring near 8820 since Dex's prior transmission (assessing = and mitigating noise in case Dex switches on again). I don't have good absolute-frequency calibration at this northern Virginia location, and = I'm interested in whether the signal captured at Forest (near 8819.9) is the same signal that I have seen almost continuously for the past 6 days (I = have seen occasional small frequency shifts that do not seem like utility = power line frequency shifts). I tried to correlate the ~0.01Hz delta-f feature shown in your spectrogram link (below), between 1400 UTC and 1700 UTC, = with my local spectrogram. This raised a Spectrum Lab question: my = spectrogram data was captured at ~ 1mHz resolution (715 uHz bin width), and = accordingly I can't quite discern 0.01uHz features (like the one shown in your = Forest link) in my waterfall display. Can I inspect previously captured = Spectrum Lab data at higher resolution by accessing a data file, or perhaps by opening a new waterfall-display window? Apologies for bothering you with this detail-level question; I wanted to try to correlate my data with = the data in your link below while the data is still in my Spectrum Lab = buffer, and without corrupting or erasing the data in the attempt to inspect it = at higher resolution.=20 73, Jim AA5BW =20 -----Original Message----- From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Paul Nicholson Sent: Friday, December 12, 2014 3:25 AM To: rsgb_lf_group@blacksheep.org Subject: Re: VLF: 8819.9 Hz in Virginia? Spectrogram covering 24 hours yesterday http://abelian.org/vlf/tmp/141211c.gif A wandering signal from a crystal source of average stability. These are fairly common when you dig deep enough into the noise. Fortunately easy to distinguish from a GPS locked amateur signal. Demonstrates how useless an undisciplined xtal osc is for VLF (tx and = rx). -- Paul Nicholson -- ------=_NextPart_000_000B_01D0162E.C0B1D150 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Jim,
 
>my spectrogram data was captured at = ~ 1mHz=20 resolution (715 uHz bin width),
 
Your resolution is actually = similar enough to=20 Paul's 833 uHz bins, and the excursion on the unid signal (around = 0.010 Hz,=20 not uHz) would be clearly visible. Could you post your spectrogram = around 16 UT=20 yesterday?
 
Best 73,
Markus

From:=20 hvanesce@comcast.net =
Sent: Friday, December 12, = 2014 4:17=20 PM
To: rsgb_lf_group@blacksheep.org=20
Subject: RE: VLF: 8819.9 = Hz in=20 Virginia?

Paul,

I've been monitoring near = 8820 since=20 Dex's prior transmission (assessing and
mitigating noise in case Dex = switches=20 on again). I don't have good
absolute-frequency calibration at this = northern=20 Virginia location, and I'm
interested in whether the signal captured = at=20 Forest (near 8819.9) is the
same signal that I have seen almost = continuously=20 for the past 6 days (I have
seen occasional small frequency shifts = that do=20 not seem like utility power
line frequency shifts). I tried to = correlate the=20 ~0.01Hz delta-f feature
shown in your spectrogram link (below), = between 1400=20 UTC and 1700 UTC, with
my local spectrogram. This raised a Spectrum = Lab=20 question: my spectrogram
data was captured at ~ 1mHz resolution (715 = uHz bin=20 width), and accordingly
I can't quite discern 0.01uHz features (like = the one=20 shown in your Forest
link) in my waterfall display. Can I inspect = previously=20 captured Spectrum
Lab data at higher resolution by accessing a data = file, or=20 perhaps by
opening a new waterfall-display window? Apologies for = bothering=20 you with
this detail-level question; I wanted to try to correlate my = data=20 with the
data in your link below while the data is still in my = Spectrum Lab=20 buffer,
and without corrupting or erasing the data in the attempt to = inspect=20 it at
higher resolution.

73,

Jim AA5BW  =20

-----Original Message-----
From: owner-rsgb_lf_group@blacksheep.org
[mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of = Paul=20 Nicholson
Sent: Friday, December 12, 2014 3:25 AM
To: rsgb_lf_group@blacksheep.org
Subject: Re: VLF: 8819.9 Hz in Virginia?

Spectrogram = covering=20 24 hours yesterday

  http://abelian.org/vlf/tmp/141211c.gif

A wandering signal from a crystal source of average=20 stability.
These are fairly common when you dig deep enough into the=20 noise.
Fortunately easy to distinguish from a GPS locked amateur=20 signal.

Demonstrates how useless an undisciplined xtal osc is for = VLF (tx=20 and rx).

--
Paul=20 Nicholson
--


------=_NextPart_000_000B_01D0162E.C0B1D150--