Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_MED, 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 uBSKh3ri029700 for ; Wed, 28 Dec 2016 21:43:04 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1cML0C-0000ah-Sn for rs_out_1@blacksheep.org; Wed, 28 Dec 2016 20:39:12 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1cML0C-0000aY-8c for rsgb_lf_group@blacksheep.org; Wed, 28 Dec 2016 20:39:12 +0000 Received: from omr-a019e.mx.aol.com ([204.29.186.67]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1cML09-0005C2-7b for rsgb_lf_group@blacksheep.org; Wed, 28 Dec 2016 20:39:11 +0000 Received: from mtaomg-mad01.mx.aol.com (mtaomg-mad01.mx.aol.com [172.26.221.207]) by omr-a019e.mx.aol.com (Outbound Mail Relay) with ESMTP id 01A6238000A6 for ; Wed, 28 Dec 2016 15:39:07 -0500 (EST) Received: from core-acx02h.mail.aol.com (core-acx02.mail.aol.com [10.76.5.147]) by mtaomg-mad01.mx.aol.com (OMAG/Core Interface) with ESMTP id 4DEFB38000085 for ; Wed, 28 Dec 2016 15:39:06 -0500 (EST) Received: from 188.192.95.60 by webprd-a15.mail.aol.com (10.72.12.229) with HTTP (WebMailUI); Wed, 28 Dec 2016 15:39:06 -0500 Date: Wed, 28 Dec 2016 15:39:06 -0500 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <15947286237-3edb-2331b@webprd-a15.mail.aol.com> In-Reply-To: <15946ff1a8d-6491-23af8@webprd-a52.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=1482957546; bh=e2rclfPjqiIrd3mGBfpB5a+uzhbIguJC2tw0KJcjrcU=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=RQGChF3qJrVLw0y6W1TNuqNHmTZeBwKPkP4nFe5NVuoRvpG7UlTzFQm37+KrvM4hB Hu1Fpl0ylGatN/M551lIc2RS0AdnGHqFQzRsjv7L0DotDL59aSI7QiOmPoK21sOnTJ GHso5Ikr06fOzhCVxU3yZABLgW6I6zsPQR/+OnzY= x-aol-sid: 3039ac1addcf586422ea3b0b X-Scan-Signature: 6bb858db23df2b82c4f5a8cb512b45b1 Subject: Re: LF: EbNaut beaconing from JN64 Content-Type: multipart/alternative; boundary="----=_Part_184494_2111093398.1482957546034" 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: O X-Status: X-Keywords: X-UID: 9981 ------=_Part_184494_2111093398.1482957546034 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable PS I have scheduled 5 minute carriers before and after each sequence, so th= at might also help finding the signal. PS Corrected a couple of typos below, regarding soundcard glitches. 73, Markus -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Markus Vester An: rsgb_lf_group Verschickt: Mi, 28 Dez 2016 8:54 pm Betreff: Re: LF: EbNaut beaconing from JN64 Hi Joe, sorry to read the mishap regarding the poor RasPi memory card. Don't worry = too much about hitting the "correct" Pilot frequency - it doesn't matter as= long as we know where it is, or the frequency word actually sent to the DD= S. If you like you might just use the magic number 59055800 ( =3D 03851eb8= hex) to come back to the old 137499.99925 Hz. Glitches seem rare enough not to be a big problem - I reviewed your files f= rom the other night (Dec 10/11) and found only a single one shortly after 2= 3 UT. Sometimes leaving the PC alone seems to help, avoiding unnecessary us= er interface activity. Anyway LF conditions seem to be improving, and my favourite northern propag= ation indicaters (Loran-C Korea and Ussurisk) are picking up a bit of stren= gth. Thought I might send a bit more EbNaut tonight, using same parameters = as before:=20 137490 Hz, 2 sec, 8 char, 8K19A, starting on the hour plus about 0.3 s sou= ndcard delay. =20 Still need to think up a message ;-). Best 73, Markus (DF6NM) -----Urspr=C3=BCngliche Mitteilung-----=20 Von: jcraig An: rsgb_lf_group Verschickt: Mi, 28 Dez 2016 7:01 pm Betreff: Re: LF: EbNaut beaconing from JN64 Hi Markus, Thank-you for your efforts. The pilot was generated using a raspi/ad9851 but there have been troubles with instability. Bypassing, shielding, etc over the past few days yeielded no satisfaction and, sadly, a fried pi/SD card! The arduino still works but the high precision math has to be done on another machine as work continues on getting a replacement=20 pilot. 73 Joe VO1NA PS Stefan's coil is very compact. 0,4 mm wire? Hope it can take the kV! PPS Paul's article greatly apprectiated. Thanks!=20 PPPS All the best to all in 2017 On Sun, 25 Dec 2016, Markus Vester wrote: > Hi Joe, > > > today I found the time to look into your files from Dec 19/20 (1220xx08.t= xt etc.). The pilot level is just right now. Assuming an accurate 10 MHz DD= S-clock, the theoretical pilot frequency would be 137499.999255 Hz, consist= ent with the -0.8 mHz offset that I had found last time. This allows us to = determine the course of your RX center frequency, which apparently drifted = about 10 mHz upwards during that night (137499.8988 to 137499.9088 Hz). > > > Some of the files (e.g. 0708 and 0608, see png) showed phase jumps, which= are presumably due to occasional short audio dropouts in the soundcard pro= cessing. In principle it should be possible to correct these glitches a-pos= teriori but I have not attempted to do so. The 0308, 0408 and 0508 files lo= oked good so I calculated the expected offsets for Ric's transmit frequency= and attempted decodes. Unfortunately no useful result appeared yet. > > > LF DX conditions haven't been too good lately. But I'm sure that once the= y improve, you will be able to pick up more than one European EbNaut statio= n. > > > Best 73, > Markus > ------=_Part_184494_2111093398.1482957546034 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

PS I have scheduled 5 minute carriers before an= d after each sequence, so that might also help finding the signal.
PS Co= rrected a couple of typos below, regarding soundcard glitches.

= 73, Markus

-----Urspr=C3=BCngliche Mitteilung-----
Von: Markus V= ester <markusvester@aol.com>
An: rsgb_lf_group <rsgb_lf_group@b= lacksheep.org>
Verschickt: Mi, 28 Dez 2016 8:54 pm
Betreff: Re: LF= : EbNaut beaconing from JN64

Hi Joe,

sorry= to read the mishap regarding the poor RasPi memory card. Don't worry = too much about hitting the "correct" Pilot frequency - it doesn't matter as= long as we know where it is, or the frequency word actually sent to t= he DDS. If you like you might just use  the magic number 590= 55800 ( =3D 03851eb8 hex) to come back to the old 137499.99925 Hz.

G= litches seem rare enough not to be a big problem - I reviewed&nbs= p;your files from the other night (Dec 10/11) and found only a single one s= hortly after 23 UT. Sometimes leaving the PC alone seems to help, avoi= ding unnecessary user interface activity.

Anyway LF conditions = seem to be improving, and my favourite northern propagation indicaters (Lor= an-C Korea and Ussurisk) are picking up a bit of strength. Thought I m= ight send a bit more EbNaut tonight, using same parameters as bef= ore: 
 137490 Hz, 2 sec, 8 char, 8K19A, starting on = the hour plus about 0.3 s soundcard delay.  
Still need t= o think up a message ;-).

Best 73,
Markus (DF6NM)

-----Urs= pr=C3=BCngliche Mitteilung-----
Von: jcraig <jcraig@mun.ca>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Versc= hickt: Mi, 28 Dez 2016 7:01 pm
Betreff: Re: LF: EbNaut beaconing from JN= 64

Hi Markus,

Thank-you for your efforts. The pilot wa= s generated using a raspi/ad9851
but there have been troubles with insta= bility. Bypassing, shielding, etc
over the past few days yeielded no sat= isfaction and, sadly, a fried pi/SD
card! The arduino still works but t= he high precision math has to
be done on another machine as work continu= es on getting a replacement
pilot.

73 Joe VO1NA

PS Stefan= 's coil is very compact. 0,4 mm wire? Hope it can take the kV!
PPS Pau= l's article greatly apprectiated. Thanks!
PPPS All the best to all in = 2017




On Sun, 25 Dec 2016, Markus Vester wrote:

&g= t; Hi Joe,
>
>
> today I found the time to look into your= files from Dec 19/20 (1220xx08.txt etc.). The pilot level is just right no= w. Assuming an accurate 10 MHz DDS-clock, the theoretical pilot frequency w= ould be 137499.999255 Hz, consistent with the -0.8 mHz offset that I had fo= und last time. This allows us to determine the course of your RX center fre= quency, which apparently drifted about 10 mHz upwards during that night (13= 7499.8988 to 137499.9088 Hz).
>
>
> Some of the files (e.= g. 0708 and 0608, see png) showed phase jumps, which are presumably due to = occasional short audio dropouts in the soundcard processing. In principle i= t should be possible to correct these glitches a-posteriori but I have not = attempted to do so. The 0308, 0408 and 0508 files looked good so I calculat= ed the expected offsets for Ric's transmit frequency and attempted decodes.= Unfortunately no useful result appeared yet.
>
>
> LF DX= conditions haven't been too good lately. But I'm sure that once they impro= ve, you will be able to pick up more than one European EbNaut station.
&= gt;
>
> Best 73,
> Markus
>
------=_Part_184494_2111093398.1482957546034--