Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: K3RWR LF EbNaut Trial #2

To: [email protected]
Subject: Re: LF: K3RWR LF EbNaut Trial #2
From: Markus Vester <[email protected]>
Date: Tue, 27 Mar 2018 11:06:23 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1522163185; bh=xmR3RfPKnLZUidMSP5HO8XmpFCuR1YrD59h1EJUwlTk=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=Yint7X7jdlQRVabTwcbTqO9p0ToiQwGgJYwvh7rVKk2a3XBRSclQyb2nHn8G8W2cm ZtcuuYlqZZadQWTSlYKSFi1qCSY0ktljzU1ae6irc/nO3NRqpHAVyWYJ8t/8N83z5N GumSbVXqZhDScZdcN+D/Rr15dsN8IU2pufoNoh3I=
In-reply-to: <[email protected]>
Reply-to: [email protected]
Sender: [email protected]
Congratulations Ric and Rob!

On their way to Italy, two of last night's transmissions also stopped by in Nuremberg, 3 UT (3.0 dB) and 4 UT (2.0 dB).

Best 73,
Markus (DF6NM)



-----Ursprüngliche Mitteilung-----
Von: Rob Renoud <[email protected]>
An: rsgb_lf_group <[email protected]>
Verschickt: Di, 27. Mrz 2018 14:01
Betreff: Re: LF: K3RWR LF EbNaut Trial #2

Riccardo,

Wow - well done at your QTH!

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

I will transmit overnight 27/28 March again with the 30 character message repeating 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 & 73,
Rob - K3RWR





On Mar 27, 2018, at 05:00, Riccardo Zoli <[email protected]> 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 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 <[email protected]>:
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 <[email protected]> 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

<raw02.JPG>
<dec02.JPG>

Attachment: 03270335_result.png
Description: PNG image

Attachment: 03270335_sym.png
Description: PNG image

<Prev in Thread] Current Thread [Next in Thread>