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 w2QK6emk021408 for ; Mon, 26 Mar 2018 22:06:41 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1f0YDo-0008NA-Ta for rs_out_1@blacksheep.org; Mon, 26 Mar 2018 20:56:00 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1f0YDb-0008N1-VH for rsgb_lf_group@blacksheep.org; Mon, 26 Mar 2018 20:55:47 +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 1f0YDY-0000lm-DV for rsgb_lf_group@blacksheep.org; Mon, 26 Mar 2018 20:55:46 +0100 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 3324B21190 for ; Mon, 26 Mar 2018 21:55:39 +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=1522094140; bh=67E61YAZoe/0jaondthBIF613ksLE1bjyp2aYwh1DI0=; h=Date:From:To:Subject:From; b=cJIieokwy0BJoleQqPUpalpI01337GRawML8BdVYMA0x0IUR2aIoaeYExaAGe+pQX wmZEYzJ7rhFwmeFWG40qlJ4E+n3NzQT6U+Pf/R25mjo/j75hXeMpmBkQuA3C/cA6QY llLpMCwJiOKrkecTzhEt9G0zDa7j626a/YFasbapeemraRvsYVjgckgq1/YI/uzJFs XNg+LI+Fc1c6yV7a1MEe7HMzrKYCW07OSCQX8kNZ1b+PfexVfKxLx33GNa7lwgUcOF D9HaMs8Awy0fM3jAPd2onaMv71gyLXUPJHZJgaZtoda6eB3eByTAA6mgYcXRHOp8J7 fSRJCpsMniQoQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4094d73XF9z9rxT for ; Mon, 26 Mar 2018 21:55:37 +0200 (CEST) Message-ID: <5AB95038.4080600@posteo.de> Date: Mon, 26 Mar 2018 21:55:36 +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> 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: 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! [...] 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: 20fb97b64762a0bd80c12a4b2f6724b0 Subject: Re: LF: K3RWR LF EbNaut Trial #2 Content-Type: multipart/alternative; boundary="------------030403040807090705010907" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=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. --------------030403040807090705010907 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 --------------030403040807090705010907 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 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
--------------030403040807090705010907--