Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w2RCEMJr024780 for ; Tue, 27 Mar 2018 14:14:24 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1f0nOv-0001iS-B6 for rs_out_1@blacksheep.org; Tue, 27 Mar 2018 13:08:29 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1f0nOu-0001iJ-O0 for rsgb_lf_group@blacksheep.org; Tue, 27 Mar 2018 13:08:28 +0100 Received: from mout01.posteo.de ([185.67.36.65]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1f0nOq-0003mg-W4 for rsgb_lf_group@blacksheep.org; Tue, 27 Mar 2018 13:08:27 +0100 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 9AA0920888 for ; Tue, 27 Mar 2018 14:08:22 +0200 (CEST) X-DKIM-Result: Domain=posteo.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1522152503; bh=RsWBQnQ106ltZYt6VzeZXxc9QIhCRBuvmsIa+ry7PK8=; h=Date:From:To:Subject:From; b=NAlAG1F4ISHrlmIyx4IM1XCNIUKJuE8efRjfvt205w9BbsDR325akMXj2EOY66GUm P1/9vUvFyLFqmLK+ZWlPN8vf3nHDbCESP1V/ID3qi5//3r6jt/7sTBb8A367U2OQVy t4G1CC7DwMFf3QP89AunfgoI8wo4WDxLgVDtKC4F1LrjoJy/j2RjbCCalbTi45uk2l QsE5cx4l6pjqLOSnqqc6nag8JFMAwOa24FsaweX6m52BJ4AWRoA3DkkAE+EEB3OlIN psQphE0Ig8E/dVt81ZcyPK4dZ+oRW4bwQ92vKJGyLc43G2Qqk/DRBILuWeDcXA3/SZ 7hqsLk+0OsatA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 409VCT2PD0z9rxN for ; Tue, 27 Mar 2018 14:08:20 +0200 (CEST) Message-ID: <5ABA3433.8040508@posteo.de> Date: Tue, 27 Mar 2018 14:08:19 +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: <79F8DC34-CFC8-4478-BDC1-2AFF165571C5@md.metrocast.net> <5AB9054D.9060200@posteo.de> <5AB95038.4080600@posteo.de> <2FDC899B-3992-4B92-913B-A53B25990420@md.metrocast.net> In-Reply-To: X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hello Riccardo, Very interesting, and congrats to the new EbNaut LF distance record :-) Most amazing! We need someone in ZL to participate! :-) It looks like you took the SpecLab predefined EbNaut feature, instead of using the FFT export and tools by DF6NM, do you confirm? [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 T_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 X-Scan-Signature: 783e848a630124d13ae6ef06c152f951 Subject: Re: LF: K3RWR LF EbNaut Trial #2 Content-Type: multipart/alternative; boundary="------------060601050704040304060107" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE 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 This is a multi-part message in MIME format. --------------060601050704040304060107 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello Riccardo, Very interesting, and congrats to the new EbNaut LF distance record :-) Most amazing! We need someone in ZL to participate! :-) It looks like you took the SpecLab predefined EbNaut feature, instead of using the FFT export and tools by DF6NM, do you confirm? 73, Stefan Am 27.03.2018 11:00, schrieb Riccardo Zoli: > > Hi Rob, Markus, Stefan, LF > > Congrats for recent LF EbNaut success! > > Last night, I have decoded your message here in *JN64bw* (Ariano). > This is a new LF EbNaut W->E QRB record: *7048 km*. > UTC 0200, *Eb/N0 = 2.2 dB* (see attachments). > * > * > My rig is a homebrew SDR, clocked by a GPSDO. The antenna is an > inverted L 12m height, 36m long. > > > All the best > > > 73 de Riccardo IW4DXW > > > > > > 2018-03-27 1:29 GMT+02:00 Rob Renoud >: > > Stephan, > > Thank you for your most insightful, and correct comments. > > I will continue to explore EbNaut as a communications and QSO mode > on 2200m. Your suggestion to focus on messages taking up to 25 > minutes and containing 15 characters fits well with using EbNaut > as a QSO mode. > > I have both Windows and Linux computers - plan on starting with > Windows and transition to Linux as I gain confidence with EbNaut RX. > > Tnx & 73, > Rob - K3RWR > > On Mar 26, 2018, at 15:55, DK7FC > wrote: > >> Hi Rob, >> >> Am 26.03.2018 19:28, schrieb Rob Renoud: >>> Very nice - thanks for you detailed reception reports for the >>> hours between 00:00 and 06:00 and, of course, the decode at 03:00. >> No problem. >> That's the path: http://k7fry.com/grid/?qth=FM18QI&from=jn49ik >> >> Not bad for the first attempt and such a message in rather poor >> conds! >> >>> I believe the tests have shown that EbNaut may well be a viable >>> QSO mode for LF and that my TX station is working well. >>> Implementing RX capability for EbNaut is my next goal. >> Good. Winodws or Linux? :-) >> >>> In the mean time, do you see a need to continue with further >>> EbNaut Trial transmissions from my station? >> For me it is fine. And you know that it's working. In the end it >> is your decision, if you like, then continue. >> >> EbNaut needs a stable phase and it could be interesting to see >> how regular a reasonably phase stability can be expected. >> I would focus on messages taking up to 25 minutes and contain 15 >> characters because this could be a useful choice for later QSO >> modes using 30 minute sequences. >> >> Also you never know who's trying to decode you. People are >> different. Some say "I'm now preparing my RX to receive you" and >> then "Now i am ready to receive you this night" an then "Here is >> my report, i have no copy because the local noise was too strong, >> but tomorrow the QRM should be lower because...." and so on. >> Other people may do the same work and have the same issues but >> tell nothing until they can report a successful decode! :-) >> If you are on the air and offer a possibility to other to detect >> you, you can only rise activity, and that's most important! >> >> 73, Stefan > > --------------060601050704040304060107 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hello Riccardo,

Very interesting, and congrats to the new EbNaut LF distance record :-) Most amazing! We need someone in ZL to participate! :-)

It looks like you took the SpecLab predefined EbNaut feature, instead of using the FFT export and tools by DF6NM, do you confirm?

73, Stefan



Am 27.03.2018 11:00, schrieb Riccardo Zoli:

Hi Rob, Markus, Stefan, LF

Congrats for recent LF EbNaut success!

Last night, I have decoded your message here in JN64bw (Ariano). This is a new LF EbNaut W->E QRB record: 7048 km.
UTC 0200, Eb/N0 = 2.2 dB (see attachments).

My rig is a homebrew SDR, clocked by a GPSDO. The antenna is an inverted L 12m height, 36m long.


All the best


73 de Riccardo IW4DXW





2018-03-27 1:29 GMT+02:00 Rob Renoud <k3rwr@md.metrocast.net>:
Stephan,

Thank you for your most insightful, and correct comments.

I will continue to explore EbNaut as a communications and QSO mode on 2200m.  Your suggestion to focus on messages taking up to 25 minutes and containing 15 characters fits well with using EbNaut as a QSO mode.  

I have both Windows and Linux computers - plan on starting with Windows and transition to Linux as I gain confidence with EbNaut RX.

Tnx & 73,
Rob - K3RWR

On Mar 26, 2018, at 15:55, DK7FC <selberdenken@posteo.de> wrote:

Hi Rob,

Am 26.03.2018 19:28, schrieb Rob Renoud:
Very nice - thanks for you detailed reception reports for the hours between 00:00 and 06:00 and, of course, the decode at 03:00.
No problem.
That's the path: http://k7fry.com/grid/?qth=FM18QI&from=jn49ik
Not bad for the first attempt and such a message in rather poor conds!

I believe the tests have shown that EbNaut may well be a viable QSO mode for LF and that my TX station is working well.
Implementing RX capability for EbNaut is my next goal.
Good. Winodws or Linux? :-)

In the mean time, do you see a need to continue with further EbNaut Trial transmissions from my station?
For me it is fine. And you know that it's working. In the end it is your decision, if you like, then continue.

EbNaut needs a stable phase and it could be interesting to see how regular a reasonably phase stability can be expected.
I would focus on messages taking up to 25 minutes and contain 15 characters because this could be a useful choice for later QSO modes using 30 minute sequences.

Also you never know who's trying to decode you. People are different. Some say "I'm now preparing my RX to receive you" and then "Now i am ready to receive you this night" an then "Here is my report, i have no copy because the local noise was too strong, but tomorrow the QRM should be lower because...." and so on. Other people may do the same work and have the same issues but tell nothing until they can report a successful decode! :-)
If you are on the air and offer a possibility to other to detect you, you can only rise activity, and that's most important!

73, Stefan

--------------060601050704040304060107--