MIME-Version: 1.0
In-Reply-To: <565B01D2.8020409@abelian.org>
References: <8D2F8A79EEF4432-1FFC-66476@webmail-vd018.sysops.aol.com>
	<CAA8k23Rrxfi8PRg4hy7XPh0X2wA39oqsy91=YR-MepHqCzAV7w@mail.gmail.com>
	<565B01D2.8020409@abelian.org>
Date: Sun, 29 Nov 2015 16:35:07 +0000
Message-ID: <CAA8k23QgCR3wK2+yzA-qaca8VBbHekKM_xDrdostDGkTbFe0SA@mail.gmail.com>
From: Andy Talbot <andy.g4jnt@gmail.com>
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: More EbNaut 137.777
Content-Type: multipart/alternative; boundary=047d7bea40b6ea452b0525b0817e
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

--047d7bea40b6ea452b0525b0817e
Content-Type: text/plain; charset=UTF-8

A query ...

So far I've been saving files every 30 minutes, to coincide with Joe's
transmissions.   And have even modified my prog to do that.

BUT   If I instead save one big file of several hours' worth of capture,
will the EbNaut Rx software be able to go though that and work with the
different transmissions?

... and will the results for each be stored in the .txt file.
It would make life easier

Andy  G4JNT


On 29 November 2015 at 13:46, Paul Nicholson <vlf0403@abelian.org> wrote:

>  VO1NA 2015-11-28/29 EbNaut 8K19A 2S 8C.
>  No T sweep, assuming good clock.
>
>  21:30  2.1 dB
>  22:00  no decode
>  22:30  no decode
>  23:00  no decode
>  23:30  no decode
>  00:00  8.6 dB
>  00:30  2.1 dB
>  01:00  3.2 dB
>  01:30 -0.2 dB
>  02:00  no decode
>  02:30  no decode
>  03:00  5.6 dB
>  03:30  no decode
>  04:00  no decode
>  04:30  no decode
>  05:00  8.6 dB
>  05:30  no decode
>  06:00  rx off for battery charge
>
> I took the 00:00 message and ran a cross-correlation with
> a locally generated copy of the message
>
>  http://abelian.org/vlf/tmp/151129a.gif
>
> The correlation peaks at a delay of 27.5 mS.
>
> Later I'll do the same with the messages that didn't
> decode, perhaps to determine if there was a fault, or
> the signal was just too weak.
>
> --
> Paul Nicholson
> --
>
>

--047d7bea40b6ea452b0525b0817e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">A query ...<div><br><div>So far I&#39;ve been saving files=
 every 30 minutes, to coincide with Joe&#39;s transmissions. =C2=A0 And hav=
e even modified my prog to do that. =C2=A0</div><div><br></div><div>BUT =C2=
=A0 If I instead save one big file of several hours&#39; worth of capture, =
will the EbNaut Rx software be able to go though that and work with the dif=
ferent transmissions?</div><div><br></div><div>... and will the results for=
 each be stored in the .txt file.</div><div>It would make life easier</div>=
<div><br></div><div>Andy =C2=A0G4JNT</div><div><br></div><div><br></div></d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 29 No=
vember 2015 at 13:46, Paul Nicholson <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:vlf0403@abelian.org" target=3D"_blank">vlf0403@abelian.org</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">=C2=A0VO1NA 2015-11-28/29 EbNaut =
8K19A 2S 8C.<br>
=C2=A0No T sweep, assuming good clock.<br>
<br>
=C2=A021:30=C2=A0 2.1 dB<br>
=C2=A022:00=C2=A0 no decode<br>
=C2=A022:30=C2=A0 no decode<br>
=C2=A023:00=C2=A0 no decode<br>
=C2=A023:30=C2=A0 no decode<br>
=C2=A000:00=C2=A0 8.6 dB<br>
=C2=A000:30=C2=A0 2.1 dB<br>
=C2=A001:00=C2=A0 3.2 dB<br>
=C2=A001:30 -0.2 dB<br>
=C2=A002:00=C2=A0 no decode<br>
=C2=A002:30=C2=A0 no decode<br>
=C2=A003:00=C2=A0 5.6 dB<br>
=C2=A003:30=C2=A0 no decode<br>
=C2=A004:00=C2=A0 no decode<br>
=C2=A004:30=C2=A0 no decode<br>
=C2=A005:00=C2=A0 8.6 dB<br>
=C2=A005:30=C2=A0 no decode<br>
=C2=A006:00=C2=A0 rx off for battery charge<br>
<br>
I took the 00:00 message and ran a cross-correlation with<br>
a locally generated copy of the message<br>
<br>
=C2=A0<a href=3D"http://abelian.org/vlf/tmp/151129a.gif" rel=3D"noreferrer"=
 target=3D"_blank">http://abelian.org/vlf/tmp/151129a.gif</a><br>
<br>
The correlation peaks at a delay of 27.5 mS.<br>
<br>
Later I&#39;ll do the same with the messages that didn&#39;t<br>
decode, perhaps to determine if there was a fault, or<br>
the signal was just too weak.<br>
<br>
--<br>
Paul Nicholson<br>
--<br>
<br>
</blockquote></div><br></div>

--047d7bea40b6ea452b0525b0817e--