Delivered-To: daveyxm@virginmedia.com Received: by 10.50.208.67 with SMTP id mc3csp3347igc; Sun, 11 May 2014 05:42:33 -0700 (PDT) X-Received: by 10.180.14.72 with SMTP id n8mr11292068wic.53.1399812152979; Sun, 11 May 2014 05:42:32 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id k14si1643881wiv.61.2014.05.11.05.42.32 for ; Sun, 11 May 2014 05:42:32 -0700 (PDT) Received-SPF: none (google.com: owner-rsgb_lf_group@blacksheep.org does not designate permitted sender hosts) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: owner-rsgb_lf_group@blacksheep.org does not designate permitted sender hosts) smtp.mail=owner-rsgb_lf_group@blacksheep.org; dkim=pass header.i=@mx.aol.com; dmarc=pass (p=REJECT dis=NONE) header.from=aol.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WjSi3-0002CZ-8x for rs_out_1@blacksheep.org; Sun, 11 May 2014 13:18:27 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WjSi2-0002CN-Nc for rsgb_lf_group@blacksheep.org; Sun, 11 May 2014 13:18:26 +0100 Received: from omr-d01.mx.aol.com ([205.188.252.208]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1WjSi0-00038a-Ck for rsgb_lf_group@blacksheep.org; Sun, 11 May 2014 13:18:25 +0100 Received: from mtaout-maa02.mx.aol.com (mtaout-maa02.mx.aol.com [172.26.222.142]) by omr-d01.mx.aol.com (Outbound Mail Relay) with ESMTP id 5FD21700567CF for ; Sun, 11 May 2014 08:18:22 -0400 (EDT) Received: from White (95-91-237-52-dynip.superkabel.de [95.91.237.52]) by mtaout-maa02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 72CB8380000A0 for ; Sun, 11 May 2014 08:18:19 -0400 (EDT) Message-ID: From: "Markus Vester" To: References: <536F1A51.3060806@abelian.org> <536F4BBF.7050506@gmail.com> <536F52FC.504@gmail.com> Date: Sun, 11 May 2014 14:18:17 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 x-mimeole: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1399810702; bh=Ei9npKeuHiTNRef1rYaArtj4UkdcCxgmUqVBQQdYFY4=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=d+tOCVG/ZAWJoWZWHLsI/Z/sqwNPFXOJYGU8F7qz1ZBJrO40gA1qT5pLtQNPLhEuH vDAE3dPlr6z7L4x8RhAXYQ8/VpIB7E55LVFLDnWu6OHuUepN2GLAL7Uf332WtI4whR Vw7tgQJFulf/r/uDljuDxhL0nNwLbRtOEQSfOYnU= x-aol-sid: 3039ac1ade8e536f6a8b4535 X-AOL-IP: 95.91.237.52 X-Spam-Score: 0.4 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Surely the concept is not limited to five-letter words. The current encoder implementation on Paul's website takes up to 50 characters, so you can announce a whole litter of kittens including their names, colours etc ;-) The coding for longer message actually becomes more efficient, due to a bit of fixed overhead (constraint length K, CRC check). [...] Content analysis details: (0.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [205.188.252.208 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 1.0 FREEMAIL_REPLY From and body contain different freemails X-Scan-Signature: ed9dcf4545ec97a65e50af1597e81212 Subject: Re: VLF: Coherent BPSK at 8270 from DF6NM Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CF6D23.DAA17110" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME autolearn=no version=2.63 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 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_000A_01CF6D23.DAA17110 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Surely the concept is not limited to five-letter words. The current = encoder implementation on Paul's website takes up to 50 characters, so = you can announce a whole litter of kittens including their names, = colours etc ;-) The coding for longer message actually becomes more = efficient, due to a bit of fixed overhead (constraint length K, CRC = check). Although the transmit part is comparatively simple, the decoder is = certainly not trivial. This is currently in an early state of = experimentation, and I have no idea weather Paul would really intend to = take it all the way to an easy-to-use software package for everyday use. Best 73, Markus From: DK7FC=20 Sent: Sunday, May 11, 2014 12:37 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: VLF: Coherent BPSK at 8270 from DF6NM Hi Markus,=20 Uuuh, chatting with max. 5 characters will become difficult i think :-) = As in JT-9, there should be 13 characters, so one can at least write "i = have a cat"... :-) Well, what does one need to arrange such a decoder? How is the message = displayed? Is it possible to run a detection window, as a text file, = like in OPDS? 73, Stefan Am 11.05.2014 12:30, schrieb Markus Vester:=20 Stefan, yes, you guessed right, the message content was indeed "DF6NM" ;-) Let = me cite from a recent direct mail to Paul: >> I was using a somewhat guessable message, foreseeing a possible = "official first" demonstration. Maybe a truely random message would have = looked even more impressive ;-) Anyhow as this is formally not "amateur = radio" but rather using an unallocated frequency range, so there's no = need for an allocated callsign. Maybe if you'd set up a transmitter = (relatively easy) and I'd learn how to decode (the hard part), we could = start chatting away on VLF ;-) 73, Markus From: DK7FC=20 Sent: Sunday, May 11, 2014 12:06 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: VLF: Coherent BPSK at 8270 from DF6NM Hello Paul, Markus, Well done! Interesting stuff. I see you never stop to find some new=20 things to try :-) Well well, i should think about... What was the contest of the message? A complete callsign, DF6NM? 73, Stefan Am 11.05.2014 08:36, schrieb Paul Nicholson: ... ------=_NextPart_000_000A_01CF6D23.DAA17110 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Surely the concept is not limited to = five-letter=20 words. The current encoder implementation on Paul's website takes up to = 50=20 characters, so you can announce a whole litter of kittens including = their names,=20 colours etc ;-) The coding for longer message actually becomes = more=20 efficient, due to a bit of fixed overhead (constraint length K, CRC=20 check).
 
Although the = transmit=20 part is comparatively simple, the decoder is certainly not = trivial.=20 This is currently in an early state of experimentation, and I = have no=20 idea weather Paul  would really intend to take it all the = way to=20 an easy-to-use software package for everyday use.
 
Best = 73,
Markus
 

From: DK7FC
Sent: Sunday, May 11, 2014 12:37 PM
Subject: Re: VLF: Coherent BPSK at 8270 from = DF6NM

Hi = Markus,=20

Uuuh, chatting with max. 5 characters will become difficult i = think :-)=20 As in JT-9, there should be 13 characters, so one can at least write "i = have a=20 cat"... :-)

Well, what does one need to arrange such a decoder? = How is=20 the message displayed? Is it possible to run a detection window, as a = text file,=20 like in OPDS?

73, Stefan

Am 11.05.2014 12:30, schrieb = Markus=20 Vester:=20
Stefan,
 
yes, you guessed right, the message = content was=20 indeed "DF6NM" ;-) Let me cite from a recent direct mail to=20 Paul:
 
>> I was using a somewhat = guessable=20 message, foreseeing a possible "official first" = demonstration. Maybe=20 a truely random message would have looked even more = impressive ;-)=20 Anyhow as this is formally not "amateur radio" but rather using = an=20 unallocated frequency range, so there's no need for an=20 allocated callsign. Maybe if you'd set up a transmitter = (relatively=20 easy) and I'd learn how to decode (the hard part), we could start = chatting=20 away on VLF ;-)
 
73, Markus
 

From: DK7FC
Sent: Sunday, May 11, 2014 12:06 PM
Subject: Re: VLF: Coherent BPSK at 8270 from=20 DF6NM

Hello Paul, Markus,

Well done! Interesting = stuff. I see=20 you never stop to find some new
things to try :-) Well well, i = should=20 think about...

What was the contest of the message? A complete=20 callsign, DF6NM?

73, Stefan

Am 11.05.2014 08:36, schrieb = Paul=20 Nicholson:
...
------=_NextPart_000_000A_01CF6D23.DAA17110--