Return-Path: X-Spam-DCC: paranoid 1002; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, HTML_50_60,HTML_MESSAGE,RATWARE_GECKO_BUILD,SPF_PASS 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 u9FEg2nT010450 for ; Sat, 15 Oct 2016 16:42:02 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1bvQ5h-0005mA-81 for rs_out_1@blacksheep.org; Sat, 15 Oct 2016 15:37:37 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1bvQ5g-0005m1-9b for rsgb_lf_group@blacksheep.org; Sat, 15 Oct 2016 15:37:36 +0100 Received: from smtp2.hushmail.com ([65.39.178.134]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1bvQ5d-0005b4-Ts for rsgb_lf_group@blacksheep.org; Sat, 15 Oct 2016 15:37:35 +0100 Received: from smtp2.hushmail.com (localhost [127.0.0.1]) by smtp2.hushmail.com (Postfix) with SMTP id 5762BA045F for ; Sat, 15 Oct 2016 14:37:29 +0000 (UTC) Received: from smtp.hushmail.com (w7.hushmail.com [65.39.178.32]) by smtp2.hushmail.com (Postfix) with ESMTP for ; Sat, 15 Oct 2016 14:37:28 +0000 (UTC) To: rsgb_lf_group@blacksheep.org References: <157b3bf43d2-111e-bfa3@webprd-a11.mail.aol.com> <0f1b59cf-e10d-1daf-125b-ad4aca471a06@gmail.com> <580205DC.80508@posteo.de> <58020BE2.1020107@posteo.de> From: Tony Baldwin Message-ID: Date: Sat, 15 Oct 2016 15:37:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <58020BE2.1020107@posteo.de> X-Scan-Signature: c96efc14f58f84aa05b44c520f48db32 Subject: Re: LF: Idiot's guide to receiving Ebnaut? - Tutorial part1 Content-Type: multipart/alternative; boundary="------------52CE15CA15771AB6CD4FE301" 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: 9789 Status: O X-Status: X-Keywords: X-UID: 9091 This is a multi-part message in MIME format. --------------52CE15CA15771AB6CD4FE301 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Thanks Stefan At the moment I'm reorganising all my shack, especially the computers, so nothing working at the moment. But If I don't get it all working by later this evening, I will certainly give it a go tomorrow. 73, Tony, EI8JK On 15/10/2016 11:58, DK7FC wrote: > 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.dropboxusercontent.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: >>> 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 Group, >>>>> >>>>> 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 = *137495.000* Hz >>>>> >>>>> Scheduled UT: *at hour*, starting from *19.00* '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.340* > 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 = 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 > > --------------52CE15CA15771AB6CD4FE301 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Thanks Stefan

At the moment I'm reorganising all my shack, especially the computers, so nothing working at the moment.
But If I don't get it all working by later this evening, I will certainly give it a go tomorrow.

73, Tony, EI8JK


On 15/10/2016 11:58, DK7FC wrote:
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.dropboxusercontent.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:
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 Group,

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 = 137495.000 Hz

Scheduled UT: at hour, starting from 19.00 '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.340 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 = 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



--------------52CE15CA15771AB6CD4FE301--