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=HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS 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 v5CED8CN000584 for ; Mon, 12 Jun 2017 16:13:10 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1dKQ1f-0002Ej-5O for rs_out_1@blacksheep.org; Mon, 12 Jun 2017 15:09:03 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1dKQ1d-0002EZ-NV for rsgb_lf_group@blacksheep.org; Mon, 12 Jun 2017 15:09:01 +0100 Received: from mout02.posteo.de ([185.67.36.66]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dKQ1a-00061D-0e for rsgb_lf_group@blacksheep.org; Mon, 12 Jun 2017 15:09:00 +0100 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 50AE120C5E for ; Mon, 12 Jun 2017 16:08:57 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3wmZWW6MQCzytg for ; Mon, 12 Jun 2017 16:08:55 +0200 (CEST) Message-ID: <593EA077.1060401@posteo.de> Date: Mon, 12 Jun 2017 16:08:55 +0200 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <15c9c532583-6648-76b2@webprd-a61.mail.aol.com> In-Reply-To: <15c9c532583-6648-76b2@webprd-a61.mail.aol.com> X-Scan-Signature: 86b6d14137f1f41166b7b27a17921f7a Subject: Re: VLF: This weekend... Content-Type: multipart/alternative; boundary="------------060603090905050201020800" 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: 11958 This is a multi-part message in MIME format. --------------060603090905050201020800 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Markus, When Paul will tell the message i will remember and confirm of course :-) BTW i have discovered a better PC in my lab, running at Win7, 64 bit, a 4 core CPU. I ordered 16 GB RAM and will try to decode your file then. It is a good test. Unfortunately the PC where i installed Linux/Ubuntu is rather old, just 2 GB RAM. But never mind, it is a very good start and i will have a better machine soon. I will also try again to decode your yesterday afternoon transmission with the Linux decoder, tomorrow. 73, Stefan Am 12.06.2017 14:41, schrieb Markus Vester: > Well done Stefan and Paul! > > >> i forgot the message > > Huh what a pity, so you won't be able to confirm Paul's decode... > unless someone with a >10 GB machine manages to pull it out from the > DL0AO wav ;-) > > 73, Markus > > > -----Ursprüngliche Mitteilung----- > Von: DK7FC > An: rsgb_lf_group > Verschickt: Mo, 12. Jun 2017 14:23 > Betreff: Re: VLF: This weekend... > > Hello Paul, VLF, > > That's nice, a new record for that week, 100 characters on 6.47 kHz in > a single (non-stacked) transmission, even in June!! :-) > Many thanks for the decode. It looks like you are further improving your > software, so it become a even more powerful tool! I run some very basic > exercises in the last days and i can say i'm impressed and i will become > a friend of the tool(s). > > Reporting the decoded message indirectly by using the md5 hash is a > cleaver idea, but i find it somehow spoils the fun a bit. In principal > the message content is not relevant because it could be any message. But > it looks like a bit far from amateur radio when the message is not told > directly. > Always think about potential newcomers: If someone reads > "9f7707ee7424c3c07c3524616fe45b9b" then he could think "What the hell > are they doing there??? but if he reads "CQ CQ on the 46 km band de > DK7FC in JN49IK, pse KK" then he may rather think "Wow they are really > transferring messages on such low frequencies, much longer messages than > in JT9, i want to try that too"... > > Another thing is that i forgot the message, so i'm curious of what you > have decoded :-) Can you tell the message please? > > 94% channel capacity and just 31.1 % bit error rate, how can this be? > > 73, Stefan > > Am 12.06.2017 11:25, schrieb Paul Nicholson: > > > > Stefan schrieb: > > > > > f = 6470.100000 Hz > > > Start time: 10.Jun.2017 04:00:00 UTC > > > Symbol period: 20 s > > > Characters: 100 > > > CRC bits: 8 > > > Coding 8K21A > > > > Copied a message with md5 hash (*): 9f7707ee7424c3c07c3524616fe45b9b > > Constant reference phase. > > > > BER 31.1% > > > > Eb/N0 = -1.1 dB, 94% of channel capacity. > > > > Carrier S/N: 26.42 dB in 10.0 uHz, > > -23.60 dB in 1Hz, > > -57.58 dB in 2.5kHz > > > > List rank 1159. > > Decoder RAM: 10Gbyte with list length 10k. > > > > I used ebnaut option -a 100 to normalise the amplitudes in the > > decoder. It didn't decode at all without that. > I will try that here too, thanks. It didn't see the -a 100 option in the > documentation. > > > > 100 chars is a record message length at 6470 Hz. > > > > Error map http://abelian.org/vlf/tmp/170612a.png > > > > I used a night blanker setting -a 12 (in version 8 onwards), > > or about -a1.2 before version 8. > > > > (*) echo -n 'XXX...XXX' | md5sum > > > > -- > > Paul Nicholson > > -- > > > --------------060603090905050201020800 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Markus,

When Paul will tell the message i will remember and confirm of course :-)

BTW i have discovered a better PC in my lab, running at Win7, 64 bit, a 4 core CPU. I ordered 16 GB RAM and will try to decode your file then. It is a good test. Unfortunately the PC where i installed Linux/Ubuntu is rather old, just 2 GB RAM. But never mind, it is a very good start and i will have a better machine soon.

I will also try again to decode your yesterday afternoon transmission with the Linux decoder, tomorrow.

73, Stefan

Am 12.06.2017 14:41, schrieb Markus Vester:
Well done Stefan and Paul!

>> i forgot the message

Huh what a pity, so you won't be able to confirm Paul's decode... unless someone with a >10 GB machine manages to pull it out from the DL0AO wav ;-)

73, Markus


-----Ursprüngliche Mitteilung-----
Von: DK7FC <selberdenken@posteo.de>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Mo, 12. Jun 2017 14:23
Betreff: Re: VLF: This weekend...

Hello Paul, VLF,

That's nice, a new record for that week, 100 characters on 6.47 kHz in
a single (non-stacked) transmission, even in June!! :-)
Many thanks for the decode. It looks like you are further improving your
software, so it become a even more powerful tool! I run some very basic
exercises in the last days and i can say i'm impressed and i will become
a friend of the tool(s).

Reporting the decoded message indirectly by using the md5 hash is a
cleaver idea, but i find it somehow spoils the fun a bit. In principal
the message content is not relevant because it could be any message. But
it looks like a bit far from amateur radio when the message is not told
directly.
Always think about potential newcomers: If someone reads
"9f7707ee7424c3c07c3524616fe45b9b" then he could think "What the hell
are they doing there??? but if he reads "CQ CQ on the 46 km band de
DK7FC in JN49IK, pse KK" then he may rather think "Wow they are really
transferring messages on such low frequencies, much longer messages than
in JT9, i want to try that too"...

Another thing is that i forgot the message, so i'm curious of what you
have decoded :-) Can you tell the message please?

94% channel capacity and just 31.1 % bit error rate, how can this be?

73, Stefan

Am 12.06.2017 11:25, schrieb Paul Nicholson:
>
> Stefan schrieb:
>
> > f = 6470.100000 Hz
> > Start time: 10.Jun.2017 04:00:00 UTC
> > Symbol period: 20 s
> > Characters: 100
> > CRC bits: 8
> > Coding 8K21A
>
> Copied a message with md5 hash (*): 9f7707ee7424c3c07c3524616fe45b9b
> Constant reference phase.
>
> BER 31.1%
>
> Eb/N0 = -1.1 dB, 94% of channel capacity.
>
> Carrier S/N: 26.42 dB in 10.0 uHz,
> -23.60 dB in 1Hz,
> -57.58 dB in 2.5kHz
>
> List rank 1159.
> Decoder RAM: 10Gbyte with list length 10k.
>
> I used ebnaut option -a 100 to normalise the amplitudes in the
> decoder. It didn't decode at all without that.
I will try that here too, thanks. It didn't see the -a 100 option in the
documentation.
>
> 100 chars is a record message length at 6470 Hz.
>
> Error map http://abelian.org/vlf/tmp/170612a.png
>
> I used a night blanker setting -a 12 (in version 8 onwards),
> or about -a1.2 before version 8.
>
> (*) echo -n 'XXX...XXX' | md5sum
>
> --
> Paul Nicholson
> --
>

--------------060603090905050201020800--