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: EATSERVER: mailn 1166; 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 v0LNE6jE001828 for ; Sun, 22 Jan 2017 00:14:07 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1cV4lY-0006Yi-GT for rs_out_1@blacksheep.org; Sat, 21 Jan 2017 23:08:12 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1cV4lY-0006YZ-6o for rsgb_lf_group@blacksheep.org; Sat, 21 Jan 2017 23:08:12 +0000 Received: from omr-m017e.mx.aol.com ([204.29.186.19]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1cV4lU-0007cB-6w for rsgb_lf_group@blacksheep.org; Sat, 21 Jan 2017 23:08:11 +0000 Received: from mtaomg-aak02.mx.aol.com (mtaomg-aak02.mx.aol.com [172.27.2.228]) by omr-m017e.mx.aol.com (Outbound Mail Relay) with ESMTP id D8E5D380008E for ; Sat, 21 Jan 2017 18:08:05 -0500 (EST) Received: from core-acx01c.mail.aol.com (core-acx01.mail.aol.com [10.76.14.37]) by mtaomg-aak02.mx.aol.com (OMAG/Core Interface) with ESMTP id 972C138000082 for ; Sat, 21 Jan 2017 18:08:03 -0500 (EST) Received: from 188.192.95.60 by webprd-m81.mail.aol.com (10.74.55.16) with HTTP (WebMailUI); Sat, 21 Jan 2017 18:08:03 -0500 Date: Sat, 21 Jan 2017 18:08:03 -0500 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <159c3496198-4603-10618@webprd-m81.mail.aol.com> In-Reply-To: <5883DED3.4040004@abelian.org> 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=1485040085; bh=bQrvB1I5uF87H4LP3wRLeOlYYPsW70eH+mU84kHY0Zk=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=OMp3Sx/x4Zza/uyhdtHOemxxLrfWN67ALUTohMT6qcImOxbSd39Qf8S2LwDsXowUm tVc/DlOFWu1Zs4b8An1Su2BjUkPa2HLxD+GqNAaOnfiREH8paxpscViBUfaO8Tw11n 1Ku/hKjpNbHDHbWKA6SqzBVjQYXzl/ct8oPmx5mQ= x-aol-sid: 3039ac1b02e45883e9d36883 X-Scan-Signature: 4d97240a623a26620214cd27feaa9f71 Subject: Re: LF: VLF/ULF activity weekend 21th/22th Content-Type: multipart/alternative; boundary="----=_Part_82811_84270619.1485040083350" 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: 10280 ------=_Part_82811_84270619.1485040083350 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Paul, yes, Stefan's carrier was on 2970.000 again today (Jan 21st, 8-17 UT): http= ://www.iup.uni-heidelberg.de/schaefer_vlf/DK7FC_VLF_Grabber2.html Catching the ULF signal in Bielefeld is a fantastic result for the three of= you, Stefan, Wolf and yourself! Wonder how that will compare to the Strass= bourg data. Compliments on the spherics blanking optimisation work! Best 73, Markus (DF6NM) PS: At this moment the beep stopped as my carrier went off for the night. I= 've set it up to come back tomorrow (Sunday) at 7 UT, and a repeat of today= 's 8270.1 Hz EbNaut sequence should start at 10 UT. -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Paul Nicholson An: rsgb_lf_group Verschickt: Sa, 21. Jan 2017 23:23 Betreff: Re: LF: VLF/ULF activity weekend 21th/22th Stefan wrote: > my frequency is 2970.000 Hz, not 2970.005 Hz as announced... Your signal on the 20th detectable at Bielefeld via the online receiver of Wolf Buescher DL4YHF, distance 303.75 km! Just about exactly three wavelengths! So, you are transmitting Stefan! S/N is about 10.5dB in but I haven't optimised the blanker and filter settings for use on vlf6 at that band, so, it probably can be improved. Is today's (21st) transmission on 2970.0 or 2970.005? The signal at Bielefeld is still present today but remains on 2970.000. It was not present on Friday or Thursday. -- Paul Nicholson -- ------=_Part_82811_84270619.1485040083350 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Paul,

yes, Stefan's carrier was on 2970.0= 00 again today (Jan 21st, 8-17 UT): http://www.iup.uni-heidelberg.de/schaef= er_vlf/DK7FC_VLF_Grabber2.html

Catching the ULF signal in Biele= feld is a fantastic result for the three of you, Stefan, Wolf and yourself!=  Wonder how that will compare to the Strassbourg data. Compliments on = the spherics blanking optimisation work!

Best 73,
Markus (DF6NM)<= br>
PS: At this moment the beep stopped as my carrier went off for = the night. I've set it up to come back tomorrow (Sunday) at 7 UT, and = a repeat of today's 8270.1 Hz EbNaut sequence should start at 10 UT.

-----Urspr=C3=BCngliche Mitteilung-----
Von: Paul Nicholson &= lt;vlf0403@abelian.org>
An: rsgb_lf_group <rsgb_lf_group@blackshee= p.org>
Verschickt: Sa, 21. Jan 2017 23:23
Betreff: Re: LF: VLF/ULF= activity weekend 21th/22th


Stefan wrote:

> my = frequency is 2970.000 Hz, not 2970.005 Hz as announced...

Your signa= l on the 20th detectable at Bielefeld via the
online receiver of Wolf Bu= escher DL4YHF, distance 303.75 km!

Just about exactly three waveleng= ths!

So, you are transmitting Stefan!

S/N is about 10.5dB in = but I haven't optimised the blanker and
filter settings for use on vlf6 = at that band, so, it probably
can be improved.

Is today's (21st) = transmission on 2970.0 or 2970.005?

The signal at Bielefeld is still= present today but remains on
2970.000. It was not present on Friday = or Thursday.

--
Paul Nicholson
--

------=_Part_82811_84270619.1485040083350--