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 w2SHkr6S029945 for ; Wed, 28 Mar 2018 19:46:55 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1f1F5h-0004qa-6U for rs_out_1@blacksheep.org; Wed, 28 Mar 2018 18:42:29 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1f1F5g-0004qR-Ir for rsgb_lf_group@blacksheep.org; Wed, 28 Mar 2018 18:42:28 +0100 Received: from proofpoint-cluster.metrocast.net ([65.175.128.136]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1f1F5Z-0008VC-9U for rsgb_lf_group@blacksheep.org; Wed, 28 Mar 2018 18:42:27 +0100 Received: from [192.168.2.10] (d-208-90-143-11.cpe.metrocast.net [208.90.143.11]) (authenticated bits=0) by huckleberry.metrocast.net (8.14.7/8.14.4) with ESMTP id w2SHgEQ4026108 for ; Wed, 28 Mar 2018 17:42:14 GMT From: Rob Renoud Mime-Version: 1.0 (1.0) Date: Wed, 28 Mar 2018 13:42:14 -0400 Message-Id: References: <1626c16e5e5-c89-51da@webjasstg-vab50.srv.aolmail.net> In-Reply-To: <1626c16e5e5-c89-51da@webjasstg-vab50.srv.aolmail.net> To: rsgb_lf_group@blacksheep.org X-Mailer: iPad Mail (15D100) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.19.17,1.0.8,0.0.0000 definitions=2018-03-28_06:2018-03-27,2018-03-28,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1603290000 definitions=main-1803280183 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: Marcus, TU for the reports. Very nice signal levels at 0200 and 0400. Yes, 12 char, CRC 15, 2 s symbols is a viable QSO candidate. [...] 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 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars X-Scan-Signature: 16ae5a6b0cd8af8ba18c7df6d1df8b5a Content-Type: multipart/alternative; boundary=Apple-Mail-446F483B-F760-4F98-97D2-EE43F9ED129D Content-Transfer-Encoding: 7bit Subject: Re: LF: K3RWR LF EbNaut Trial #2 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR 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 --Apple-Mail-446F483B-F760-4F98-97D2-EE43F9ED129D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Marcus, TU for the reports. Very nice signal levels at 0200 and 0400. Yes, 12 char, CRC 15, 2 s symbols is a viable QSO candidate. I will begin transmitting overnight a 12 character message for the next thre= e days as follows: Coding: 8K19 CRC: 15 Symbol Period: 2 sec Length: 12 characters Duration: 28 minutes Message repeated on the Hour & Half-Hour Frequency: 137.395 KHz Start Time: 2200 UTC daily Stop Time: 1000 UTC daily Days: 28/29 Mar, 29/30 Mar, 30/31 Mar Reports and comments welcome :-) 73, Rob - K3RWR FM18qi > On Mar 28, 2018, at 06:11, Markus Vester wrote: >=20 > Hi Rob, >=20 > three decodes again last night: >=20 > UT dB > 0100 1.0 > 0200 8.2 > 0400 5.4 >=20 > Although the signal is sometimes quite strong, it is undecodable due to fa= ding or phase variation at other times. For a two-way QSO I would probably p= refer shorter messages (e.g. 12 char, CRC 15, 2 s symbols, 28 minutes total)= which may come through more reliably. They will also decode more quickly, i= deally allowing an answer in the next time slot. >=20 > Best 73, > Markus (DF6NM) >=20 >=20 >=20 > -----Urspr=C3=BCngliche Mitteilung-----=20 > Von: Markus Vester > An: rsgb_lf_group > Verschickt: Di, 27. Mrz 2018 17:06 > Betreff: Re: LF: K3RWR LF EbNaut Trial #2 >=20 > Congratulations Ric and Rob! >=20 > On their way to Italy, two of last night's transmissions also stopped by i= n Nuremberg, 3 UT (3.0 dB) and 4 UT (2.0 dB). >=20 > Best 73,=20 > Markus (DF6NM) >=20 >=20 >=20 > -----Urspr=C3=BCngliche Mitteilung-----=20 > Von: Rob Renoud > An: rsgb_lf_group > Verschickt: Di, 27. Mrz 2018 14:01 > Betreff: Re: LF: K3RWR LF EbNaut Trial #2 >=20 > Riccardo, >=20 > Wow - well done at your QTH! >=20 > Transmitting at 1W EIRP here. Antenna is a 12.4m vertical wire with 140m o= f top loading. >=20 > I will transmit overnight 27/28 March again with the 30 character message r= epeating every hour. Will then switch to a 20 character message with 1 seco= nd symbol period repeating every half hour. Will post the details of the ne= w message on this web site. >=20 > Thanks & 73, > Rob - K3RWR >=20 >=20 >=20 >=20 >=20 > On Mar 27, 2018, at 05:00, Riccardo Zoli wrote:= >=20 >=20 > Hi Rob, Markus, Stefan, LF >=20 > Congrats for recent LF EbNaut success! >=20 > 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 =3D 2.2 dB (see attachments). >=20 > My rig is a homebrew SDR, clocked by a GPSDO. The antenna is an inverted L= 12m height, 36m long. >=20 >=20 > All the best >=20 >=20 > 73 de Riccardo IW4DXW >=20 >=20 >=20 >=20 >=20 > 2018-03-27 1:29 GMT+02:00 Rob Renoud : > Stephan, >=20 > Thank you for your most insightful, and correct comments. >=20 > I will continue to explore EbNaut as a communications and QSO mode on 2200= m. Your suggestion to focus on messages taking up to 25 minutes and contain= ing 15 characters fits well with using EbNaut as a QSO mode. =20 >=20 > I have both Windows and Linux computers - plan on starting with Windows an= d transition to Linux as I gain confidence with EbNaut RX. >=20 > Tnx & 73, > Rob - K3RWR >=20 > On Mar 26, 2018, at 15:55, DK7FC wrote: >=20 > Hi Rob, >=20 > Am 26.03.2018 19:28, schrieb Rob Renoud: > Very nice - thanks for you detailed reception reports for the hours betwee= n 00:00 and 06:00 and, of course, the decode at 03:00. > No problem. > That's the path: http://k7fry.com/grid/?qth=3DFM18QI&from=3Djn49ik > Not bad for the first attempt and such a message in rather poor conds! >=20 > I believe the tests have shown that EbNaut may well be a viable QSO mode f= or LF and that my TX station is working well. > Implementing RX capability for EbNaut is my next goal. > Good. Winodws or Linux? :-) >=20 > In the mean time, do you see a need to continue with further EbNaut Trial t= ransmissions from my station? > For me it is fine. And you know that it's working. In the end it is your d= ecision, if you like, then continue.=20 >=20 > EbNaut needs a stable phase and it could be interesting to see how regular= a reasonably phase stability can be expected.=20 > I would focus on messages taking up to 25 minutes and contain 15 character= s because this could be a useful choice for later QSO modes using 30 minute s= equences. >=20 > 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 re= ceive 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 c= an only rise activity, and that's most important! >=20 > 73, Stefan >=20 > > >=20 > <03280235_sym.png> > --Apple-Mail-446F483B-F760-4F98-97D2-EE43F9ED129D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Marcus,

TU for the reports.  Very nice signal levels at 0200 and 0400.

Yes, 12 char, CRC 15, 2 s symbols is a viable QSO can= didate.

I will begin transmitting overnight a 12 ch= aracter message for the next three days  as follows:

Coding: 8K19
CRC:  15
Symbol Period: 2 sec
Length:  12 characters
Duration:  28 minutes
Message repeated on the Hour & Half-Hour
Frequency: &n= bsp;137.395 KHz
Start Time:  2200 UTC daily
Stop Ti= me:  1000 UTC daily
Days:  28/29 Mar, 29/30 Mar, 30/31 M= ar

Reports and comments welcome :-)

<= /div>
73,
Rob - K3RWR FM18qi


On M= ar 28, 2018, at 06:11, Markus Vester <markusvester@aol.com> wrote:

Hi Rob,

three decodes again la= st night:

 UT   dB
0100  1.0
0= 200  8.2
0400  5.4

Although the signal is s= ometimes quite strong, it is undecodable due to fading or phase variation at= other times. For a two-way QSO I would probably prefer shorter messages (e.= g. 12 char, CRC 15, 2 s symbols, 28 minutes total) which may come through mo= re reliably. They will also decode more quickly, ideally allowing an answer i= n the next time slot.

Best 73,
Markus (DF6NM)

=

-----Urspr=C3=BCngliche Mitteilung-----
Von: Markus Vester <<= a href=3D"mailto:markusvester@aol.com">markusvester@aol.com>
An: r= sgb_lf_group <rsgb_lf_gro= up@blacksheep.org>
Verschickt: Di, 27. Mrz 2018 17:06
Betreff: R= e: LF: K3RWR LF EbNaut Trial #2

Congratulations Ric and= Rob!

On their way to Italy, two of last night's transmi= ssions also stopped by in Nuremberg, 3 UT (3.0 dB) and 4 UT (2.0 dB).
<= div style=3D"color: black; font-family: arial,helvetica,sans-serif; font-siz= e: 10pt;">
Best 73,
Markus (DF6NM)



-----Urspr=C3=BCngl= iche Mitteilung-----
Von: Rob Renoud <k3rwr@md.metrocast.net>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>Verschickt: Di, 27. Mrz 2018 14:01
Betreff: Re: LF: K3RWR LF EbNaut Tri= al #2

=
Riccardo,

Wow - well done at y= our QTH!

Transmitting at 1W EIRP here.  Antenn= a is a 12.4m vertical wire with 140m of top loading.

I will transmit overnight 27/28 March again with the 30 character message r= epeating every hour.  Will then switch to a 20 character message with 1= second symbol period repeating every half hour.  Will post the details= of the new message on this web site.

Thanks & 7= 3,
Rob - K3RWR



<= div>

On Mar 27, 2018, at 05:00, Riccardo Zoli <riccardozoli80@gmail.com> wrote:


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 E= bNaut W->E QRB record: 7048 km.
UTC 0200, Eb/N0 =3D= 2.2 dB (see attachments).

My r= ig is a homebrew SDR, clocked by a GPSDO. The antenna is an inverted L 12m h= eight, 36m long.


All the best
<= div>

73 de Riccardo IW4DXW

=




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

Thank you for yo= ur most insightful, and correct comments.

I will co= ntinue to explore EbNaut as a communications and QSO mode on 2200m.  Yo= ur 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 W= indows and transition to Linux as I gain confidence with EbNaut RX.

Tnx & 73,
Rob - K3RWR

On Mar 26, 2018, at 15:55, DK7FC <http://k7fry.com/grid/?qth=3D= FM18QI&from=3Djn49ik
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

<raw02.JPG>
<dec02.JPG>

<03280235_sym= .png>
<k3rwr_df6nm_18= 0328_logs.txt>
= --Apple-Mail-446F483B-F760-4F98-97D2-EE43F9ED129D--