Message-ID: <5AB10ABA.9030504@posteo.de>
Date: Tue, 20 Mar 2018 14:20:58 +0100
From: DK7FC <selberdenken@posteo.de>
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: <8a85a7a8-7a1b-f38c-3581-88701aeaf955@n1bug.com> <5AAFE3B3.8050603@posteo.de> <BF78757DDB53418FBDBB44BDDF21C052@PCDaheim> <CAC+C6w41=_5R_po9Kn0Szd7dTtv6DQ4Cgn7uWAPjRwwyoXUpfQ@mail.gmail.com> <579355A36AEE9D4FA555C45D556003ABA3C3A19A@servigilant.vigilant.local> <8E11D917-1416-4D11-A173-E71E2C74FCC1@md.metrocast.net>
In-Reply-To: <8E11D917-1416-4D11-A173-E71E2C74FCC1@md.metrocast.net>
Subject: Re: [english 100%] Re: LF: 2200m Trans-Atlantic QSO dream...
Content-Type: multipart/alternative;
 boundary="------------080306050507040503070205"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

This is a multi-part message in MIME format.
--------------080306050507040503070205
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Rob,

Am 20.03.2018 12:17, schrieb Rob Renoud:
> I do agree that EbNaut is most excellent for experimentation and 
> possibly QSOs on LF.  I believe the LF community should formulate an 
> initial signal configuration for development and testing and one that 
> will possibly support minimum QSO requirements as well.  I am not 
> smart enough about EbNaut at this point to offer any suggestions or 
> make any recommendations about signal configurations.
>
> I am also available to put a EbNaut signal at 1W EIRP on LF from my 
> QTH at FM18qi while I continue implementing full EbNaut RX and decode 
> capability.
>
> All ideas, suggestions and recommendations welcome!

Meanwhile Jay/W1VD should be well equipped and routined for EbNaut 
reception. His LF RX has always been one of the best in the US. Before 
attempting QSOs i would suggest to run simple beacons, with a short 
message like 'K3RWR' :-)

Always use this page to determine the symbol length and CRC to get a 
specific transmission duration: 
http://abelian.org/ebnaut/calc.php?sndb=3&snbws=0.022&snmps=&code=8K19&sp=3&crc=24&nc=5&submit=Calculate

The settings are just an example. Assume your beacon repeats each 30 
minutes and sends your callsign, then these settings may be a good 
choice to start.

Once someone has a decode of your transmission, he can report 'you are 3 
dB in 22 mHz' (a typical BW for a QRSS-60 spectrogram) and then you can 
type these values in the tp fields of that page and calculate how many 
characters could be possible at that SNR in that bandwidth.
And for a RX station it is some advice which optimum list length is 
recommended.

It would be interesting to see some progress in the use of EbNaut on LF. 
Then, the step to VLF is an order of magnitude smaller :-)

73, Stefan

--------------080306050507040503070205
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Rob,<br>
<br>
Am 20.03.2018 12:17, schrieb Rob Renoud:
<blockquote
 cite="mid:8E11D917-1416-4D11-A173-E71E2C74FCC1@md.metrocast.net"
 type="cite">
  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  <div>I do agree that EbNaut is most excellent for experimentation and
possibly QSOs on LF.  I believe the LF community should formulate an
initial signal configuration for development and testing and one that
will possibly support minimum QSO requirements as well.  I am not smart
enough about EbNaut at this point to offer any suggestions or make any
recommendations about signal configurations.</div>
  <div><br>
  </div>
  <div>I am also available to put a EbNaut signal at 1W EIRP on LF from
my QTH at FM18qi while I continue implementing full EbNaut RX and
decode capability.</div>
  <div><br>
  </div>
  <div>All ideas, suggestions and recommendations welcome!</div>
</blockquote>
<br>
Meanwhile Jay/W1VD should be well equipped and routined for EbNaut
reception. His LF RX has always been one of the best in the US. Before
attempting QSOs i would suggest to run simple beacons, with a short
message like 'K3RWR' :-) <br>
<br>
Always use this page to determine the symbol length and CRC to get a
specific transmission duration:
<a class="moz-txt-link-freetext" href="http://abelian.org/ebnaut/calc.php?sndb=3&amp;snbws=0.022&amp;snmps=&amp;code=8K19&amp;sp=3&amp;crc=24&amp;nc=5&amp;submit=Calculate">http://abelian.org/ebnaut/calc.php?sndb=3&amp;snbws=0.022&amp;snmps=&amp;code=8K19&amp;sp=3&amp;crc=24&amp;nc=5&amp;submit=Calculate</a><br>
<br>
The settings are just an example. Assume your beacon repeats each 30
minutes and sends your callsign, then these settings may be a good
choice to start.<br>
<br>
Once someone has a decode of your transmission, he can report 'you are
3 dB in 22 mHz' (a typical BW for a QRSS-60 spectrogram) and then you
can type these values in the tp fields of that page and calculate how
many characters could be possible at that SNR in that bandwidth.<br>
And for a RX station it is some advice which optimum list length is
recommended.<br>
<br>
It would be interesting to see some progress in the use of EbNaut on
LF. Then, the step to VLF is an order of magnitude smaller :-)<br>
<br>
73, Stefan<br>
</body>
</html>

--------------080306050507040503070205--