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 v43KOqXP011631 for ; Wed, 3 May 2017 22:24:53 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1d60mG-0004dh-Vf for rs_out_1@blacksheep.org; Wed, 03 May 2017 21:21:36 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1d60mG-0004dY-Ch for rsgb_lf_group@blacksheep.org; Wed, 03 May 2017 21:21:36 +0100 Received: from omr-m011e.mx.aol.com ([204.29.186.11]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1d60mD-0003vf-7I for rsgb_lf_group@blacksheep.org; Wed, 03 May 2017 21:21:35 +0100 Received: from mtaomg-aal02.mx.aol.com (mtaomg-aal02.mx.aol.com [172.27.20.208]) by omr-m011e.mx.aol.com (Outbound Mail Relay) with ESMTP id DD6D8380010E for ; Wed, 3 May 2017 16:21:30 -0400 (EDT) Received: from core-acx11d.mail.aol.com (core-acx11.mail.aol.com [172.27.155.136]) by mtaomg-aal02.mx.aol.com (OMAG/Core Interface) with ESMTP id 6EEC538000081 for ; Wed, 3 May 2017 16:21:30 -0400 (EDT) Received: from 188.192.95.60 by webprd-m100.mail.aol.com (10.74.63.51) with HTTP (WebMailUI); Wed, 03 May 2017 16:21:30 -0400 Date: Wed, 3 May 2017 16:21:30 -0400 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <15bcff98e23-6ee5-1ac54@webprd-m100.mail.aol.com> In-Reply-To: <579355A36AEE9D4FA555C45D556003AB8FDD7085@servigilant.vigilant.local> 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=1493842890; bh=vc583lKbGcqKkwIETPAIzWNe6MNI3wxz84ilSLDlSHQ=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=f+khgj4SfQJTaDKEFsVha5HtrlTNIff4l6ZzKwZM37ZTpxMfYcyo856zhSnS1Up49 +oSpOSqdrZESuJwwDDbwksnarblnheNe8eoZy4BLQvnsrs/S7JLkLV7bbMtsgsTpD8 7s+aik+KMPP8Hst9wqws3Ps25h60fjkRvmp2Wt3c= x-aol-sid: 3039ac1b14d0590a3bca0729 X-Scan-Signature: f7f918e40888a44a70dddae14bd6a529 Subject: Re: LF: SL settings for EbNaut FFT recording ? Content-Type: multipart/alternative; boundary="----=_Part_136630_1825124152.1493842890273" 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: RO X-Status: X-Keywords: X-UID: 11581 ------=_Part_136630_1825124152.1493842890273 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Luis, yes I also found that your file starts 20.76 seconds late. But this is not = a big problem, because the decoder can cope with missing data at the beginn= ing or end. For a late start you should simply enter a negative start offse= t, i.e. -20.76 seconds plus four samples =3D -20.76 + 4 / 0.514 =3D -13 sec= onds. In this case the loss is less than a single sample so perfectly negli= gible. I also attempted to decode your file with no success, so probably ju= st not enough SNR yet. Best 73, Markus =20 -----Urspr=C3=BCngliche Mitteilung-----=20 Von: VIGILANT Luis Fern=C3=A1ndez An: rsgb_lf_group Verschickt: Mi, 3. Mai 2017 22:05 Betreff: Re: LF: SL settings for EbNaut FFT recording ? Hi Markus=20 Not your fault ! I did not use your .USR directly. Tried to reproduce the c= onfiguration manually Then I did not realize about the different time pattern in the files. Now I= understand one more detail ;-) Unfortunately EbNaut reports that the file start is at 18:00:20.760 So it seems it started too late. And the previous file will be one hour ear= lier, so loosing the end of the transmission Would it worth to use a bigger FFT of 10 hours for example ? Anyway show_rawsyms3b produces a very flat graphic. No signs of a signal an= ywere=20 I think that means "keep playing" ;-) 73 de Luis EA5DOM ------=_Part_136630_1825124152.1493842890273 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Luis,

yes I also found that your file sta= rts 20.76 seconds late. But this is not a big problem, = because the decoder can cope with missing data at the beginning or end.&nbs= p;For a late start you should simply enter a negative start offse= t, i.e. -20.76 seconds plus four samples =3D -20.76 + 4 / 0.514 = =3D -13 seconds. In this case the loss is less than a single sample so= perfectly negligible. I also attempted to decode your file with no su= ccess, so probably just not enough SNR yet.

Best 73,
Markus&= nbsp;  


-----Urspr=C3=BCngliche Mitteilung-----
Vo= n: VIGILANT Luis Fern=C3=A1ndez <luis@vigilant.es>
An: rsgb_lf_gro= up <rsgb_lf_group@blacksheep.org>
Verschickt: Mi, 3. Mai 2017 22:0= 5
Betreff: Re: LF: SL settings for EbNaut FFT recording ?

Hi Markus

Not your fault ! I did not use your .USR directly. Tried to reproduce = the configuration manually
Then I did not realize about the different time pattern in the files. = Now I understand one more detail ;-)

Unfortunately EbNaut reports that the file start is at 18:00:20.760
So it seems it started too late. And the previous file will be one hou= r earlier, so loosing the end of the transmission
Would it worth to use a bigger FFT of 10 hours for example ?

Anyway show_rawsyms3b produces a very flat graphic. No signs of a sign= al anywere 
I think that means "keep playing" ;-)

73 de Luis
EA5DOM

------=_Part_136630_1825124152.1493842890273--