Return-Path: X-Spam-DCC: paranoid 1002; Body=3 Fuz1=3 Fuz2=3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_40_50,HTML_MESSAGE,SPF_PASS,UNPARSEABLE_RELAY autolearn=no 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 u9FGTcQL010636 for ; Sat, 15 Oct 2016 18:29:38 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1bvRmd-000635-1g for rs_out_1@blacksheep.org; Sat, 15 Oct 2016 17:26:03 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1bvRmc-00062w-2z for rsgb_lf_group@blacksheep.org; Sat, 15 Oct 2016 17:26:02 +0100 Received: from omr-m020e.mx.aol.com ([204.29.186.20]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1bvRmZ-0006B7-Fb for rsgb_lf_group@blacksheep.org; Sat, 15 Oct 2016 17:26:00 +0100 Received: from mtaomg-maa01.mx.aol.com (mtaomg-maa01.mx.aol.com [172.26.222.143]) by omr-m020e.mx.aol.com (Outbound Mail Relay) with ESMTP id 4EBD5380008C for ; Sat, 15 Oct 2016 12:25:56 -0400 (EDT) Received: from core-acb04f.mail.aol.com (core-acb04.mail.aol.com [172.27.24.4]) by mtaomg-maa01.mx.aol.com (OMAG/Core Interface) with ESMTP id C147938000081 for ; Sat, 15 Oct 2016 12:25:54 -0400 (EDT) Received: from 188.192.95.60 by webprd-a93.mail.aol.com (10.72.112.251) with HTTP (WebMailUI); Sat, 15 Oct 2016 12:25:54 -0400 Date: Sat, 15 Oct 2016 12:25:54 -0400 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <157c929fc63-14b4-5f3e@webprd-a93.mail.aol.com> In-Reply-To: <37b7689f023948f5ff06468d25a3ace3@smtp.hushmail.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=1476548756; bh=nOHb7nSKHbgLuhIPqC0m0Pu+0z+3cS2PTi07jmczK90=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=YbGinxM3DIlnqkvZ+NFbjpccnU16a1A4AGkySRCwOKjUyptlTzu3E/VDdaITsmVgD 3G9TT0OdqNhY8ySMk8ToxO/DWv5z/Ase1PBpFnqpNUM1EMLiSPp7Hauh4UVTeQ2KjZ FT8tRYE6dEckThQndJmoZrVgE9BI0bgdRe51koT0= x-aol-sid: 3039ac1ade8f580258923833 X-Scan-Signature: 671be81035fb274514daa81d2095bf05 Subject: Re: LF: Idiot's guide to receiving Ebnaut? - Tutorial part1 Content-Type: multipart/alternative; boundary="----=_Part_31781_1929385629.1476548754528" 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.11 Content-Length: 10398 Status: O X-Status: X-Keywords: X-UID: 9093 ------=_Part_31781_1929385629.1476548754528 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Tony,=20 downloading from the Dropbox link appeared to work fine here. Anyway I've t= emporarily ftp-ed Stefan's file to http://df6nm.bplaced.net/VLF/fec_tests/1= 0111913.wav , hope that might help out.=20 One minor note: Riccardo's transmission was announced and sent 0.6 milliHz = above nominal. Entering a frequency offset of -14.9994 instead of -15 Hz pr= oduced a stronger and quicker decode. All the best, Markus=20 -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Tony Baldwin An: rsgb_lf_group Verschickt: Sa, 15 Okt 2016 5:58 pm Betreff: Re: LF: Idiot's guide to receiving Ebnaut? - Tutorial part1 Stefan I can't seem to download the dropbox files, it just opens to a video playb= ack. Tony On 15/10/2016 11:58, DK7FC wrote: Hi all,=20 There must be some progress. I thought it could be useful to lern how to participate in EbNaut detectio= ns by doing 2 exercises. 1: Generating wav files that contain the message 2: Configure the EbNaut decoder to read the wav file successfully. Step 2 can be done today. First you need to download the decoder software at http://abelian.org/ebna= ut/ Then you need a wav-file containing a message. For this tutorial, you can = have a wav file that was generated on my PC. It contains even 2 messages (r= are!). Download the file from: https://dl.dropboxusercontent.com/u/19882028/LF/10= 111913.wav To decode a EbNaut message you have to know the start time, the symbol len= gth, the number of characters and the Coding. These informations are given = by the TX stn. Info for message 1: Am 11.10.2016 19:04, schrieb IZ7SLZ:=20 Hello LF, Riccardo IW4DXW informs that he also will be QRV EbNaut tonight on 137485.= 0006 Hz Message contains 31 characters transmitted at 0.5 s/sym, coding 8K19A, dur= ation 14'40'' each hour starting 19.00Z till 23.00Z . GL. 73, Domenico iz7slz My file contains the 19:00 UTC transmission. Info for message 2: Hello Group, considering the Stefan's request, i'm pleased to test again EbNaut today o= n LF with a 51 characters message, 8K19A code, 0.5 s/symbol, duration 22' 4= 0''. QRG =3D 137495.000 Hz Scheduled UT: at hour, starting from 19.00 'till 01.00 of 12-10-2016 (incl= uded). Carrier will be "on" 5 minutes before the transmissions. Now use the EbNaut decoder and select the wav file. For the first message = you can choose 31 characters, and 0.5 for the symbol period. Then press sta= rt, just for a few seconds, then stop again. You will now see some more inf= ormations: The RX freqency and the file start time. Now you can select the = frequency offset, which is -15 Hz. Type that into the field. The next thing is the timing offset. The start time is 18:54:22.340 and th= e message started 19:00:00. You need to know the timing offset precisely! I= f you don't get a decode, it is worth to vary the time offset a bit. A timi= ng offset could of course also come from the TX stn, sometimes unknown. Spe= cLab causes a time offset of 4 samples. You can also see the samplerate 117= .19/sec. So the timing offset is: (4S)/(117.19S/sec)+0.66sec+37sec+300sec = =3D 337.69 seconds. Type that into the start offset field. Now you can start the decoder and should get a decode quite quickly, depen= ding on your PC power. By changing just the number of characters and the frequency offset, you sh= ould receive the other message. Fine, that was part 1 :-) I need to get a feedback now if YOU got a successful decode or if there ar= e problems. Depending on that feedback i would then continue with part 2. Can someone of the 'newcomers' decode both messages? 73, Stefan ------=_Part_31781_1929385629.1476548754528 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Tony, 

downloading from the Dropbox link= appeared to work fine here. Anyway I've temporarily ftp-ed Stefan's file t= o http://df6nm.bplaced.net/VLF/fec_tests/10111913.wav , hope that might hel= p out. 

One minor note: Riccardo's transmission was announced a= nd sent 0.6 milliHz above nominal. Entering a frequency offset of -14.9994&= nbsp;instead of -15 Hz produced a stronger and quicker decode.
All the best,
Markus 



-----Urspr=C3=BCngliche M= itteilung-----
Von: Tony Baldwin <ei8jk@topmail.ie>
An: rsgb_l= f_group <rsgb_lf_group@blacksheep.org>
Verschickt: Sa, 15 Okt 2016= 5:58 pm
Betreff: Re: LF: Idiot's guide to receiving Ebnaut? - Tutorial = part1

Stefan
I can't seem to download the dropbox files, it just opens to a video playback.
Tony


On 15/10/2016 11:58, DK7FC wrote= :
=20 Hi all,

There must be some progress.
I thought it could be useful to lern how to participate in EbNaut detections by doing 2 exercises.
1: Generating wav files that contain the message
2: Configure the EbNaut decoder to read the wav file successfully.
Step 2 can be done today.
First you need to download the decoder software at http://abelian.org/ebnaut/
Then you need a wav-file containing a message. For this tutorial, you can have a wav file that was generated on my PC. It contains even 2 messages (rare!).
Download the file from: https://dl.dr= opboxusercontent.com/u/19882028/LF/10111913.wav
To decode a EbNaut message you have to know the start time, the symbol length, the number of characters and the Coding. These informations are given by the TX stn.
Info for message 1:
Am 11.10.2016 19:04, schrieb IZ7SLZ:
=20
Hello LF,
Riccardo IW4DXW informs that he also will be QRV EbNaut tonight on 137485.0006 Hz
Message contains 31 characters transmitted at 0.5 s/sym, coding 8K19A, duration 14'40'' each hour starting 19.00Z  till 23.00Z .

GL.
73, Domenico iz7slz

My file contains the 19:00 UTC transmission.
Info for message 2:

Hello Gr= oup,

considering the Stefan's request, i'm pleased to test again EbNaut today on LF with a 51 characters message, 8K19A code, 0.5 s/symbol, duration 22' 40''.
QRG =3D 137495.000 Hz

Scheduled UT: at hour, starting from 19.00<= /b> 'till 01.00 of 12-10-2016 (included). Carrier will be "on"  = 5 minutes before the transmissions.

Now use the EbNaut decoder and select the wav file. For the first message you can choose 31 characters, and 0.5 for the symbol period. Then press start, just for a few seconds, then stop again. You will now see some more informations: The RX freqency and the file start time. Now you can select the frequency offset, which is -15 Hz. Type that into the field.
The next thing is the timing offset. The start time is 18:54:22.34= 0 and the message started 19:00:00. You need to know the timing offset precisely! If you don't get a decode, it is worth to vary the time offset a bit. A timing offset could of course also come from the TX stn, sometimes unknown. SpecLab causes a time offset of 4 samples. You can also see the samplerate 117.19/sec. So the timing offset is: (4S)/(117.19S/sec)+0.66sec+37sec+300sec =3D 337.69 seconds. Type that into the start offset field.
Now you can start the decoder and should get a decode quite quickly, depending on your PC power.

By changing just the number of characters and the frequency offset, you should receive the other message.

Fine, that was part 1 :-)
I need to get a feedback now if YOU got a successful decode or if there are problems. Depending on that feedback i would then continue with part 2.
Can someone of the 'newcomers' decode both messages?

73, Stefan



=20
------=_Part_31781_1929385629.1476548754528--