Re: LF: More EbNaut 137.777 - long wav file

[Markus Vester <markusvester@aol.com>]

Andy,

 

as far as I know you can record a single long wav file, and then run ebnaut-rx several times with a new time offset for each decode attempt. E.g. if your files started 19:59:51, you'd enter 9, 1809, 3609, etc. seconds. After each run you should manually save or rename the xxx-log.txt file as it would otherwise be overwritten during the next attempt. As time offsets into the file will become large, the file samplerate needs to be accurate to avoid buildup of time errors.

 

All the best,
Markus

 

-----Ursprüngliche Mitteilung----- 
Von: Andy Talbot <andy.g4jnt@gmail.com>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: So, 29 Nov 2015 5:38 pm
Betreff: Re: LF: More EbNaut 137.777

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
--