Message-ID: <5BA1FB2F.3020201@posteo.de>
Date: Wed, 19 Sep 2018 09:30:55 +0200
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: <282F751D-64A8-4EC5-8EEF-9C5CF2ED6921@md.metrocast.net> <5BA0139E.3030205@posteo.de> <5BA0170F.1090303@posteo.de> <8A3EDA86-338A-4338-B7DA-8B617DA05AC2@md.metrocast.net> <6DB8451D7F3D3947A5918808A59621EA08624EFA@servigilant.vigilant.local>
In-Reply-To: <6DB8451D7F3D3947A5918808A59621EA08624EFA@servigilant.vigilant.local>
Subject: Re: LF: LF EbNaut TX Announcement
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

Hi Luis, Rob,

I would vote for 15 characters rather than just 12. In JT-9 there are 13 
characters which is often a bit short and limits the fun of the mode. 
For practical reasons it is necessary to use a script/program to decode 
the messages automatically. And there it is possible to try to decode on 
different frequencies and different length, so maybe we can even define 
two types of message lengths. Also it can be done in separate scripts, 
just like we can generate different spectrograms (e.g. one for QRSS-10 
and another one for QRSS-60) to the same time, using two SpecLab 
instances. It just has to be defined.
I'm curious what you'll do when the season has fully started.

73, Stefan

Am 19.09.2018 09:03, schrieb VIGILANT Luis Fernández:
> Hi EbNaut LF
>
> Good idea Rob !
>
> We need to standarize a message format for QSOs. You proposal looks right for that
>
> I assume you will keep using 137.470
> Hope to decode you soon. I need to improve my Rx
>
> 73 de Luis
> EA5DOM
>
> -----Mensaje original-----
> De: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] En nombre de Rob Renoud
> Enviado el: martes, 18 de septiembre de 2018 14:41
> Para: rsgb_lf_group@blacksheep.org
> Asunto: Re: LF: LF EbNaut TX Announcement
>
> Hello 2200m EbNaut,
>
> The results of the EbNaut beacon tests are very encouraging for the domestic and TA paths.  Thank you to all who listened, decoded, reported and commented :-)
>
> Seeking a practicable EbNaut QSO mode for 2200m TA contacts, I propose activating my EbNaut beacon each weekend as we move into the fall and winter in the Northern Hemisphere using the following format:
>
> Code:  8K19A
> Symbol Period:  1.5 sec
> CRC: 16
> Number of Characters:  12
> Symbol Bits:  812
> Duration:  00:21:12.00
> Power:  1 watt EIRP
>
> The above format supports amateur QSOs on 2200m as follows:
>
> 1) Conforms to phase and signal stability characteristics of this band
> 2) Allows 2 x 6 character call sign exchange
> 3) Allows 30 minute Odd/Even TX/RX periods
> 4) Allows commonly used (WSJT) digital QSO format
>
> Comments welcome.  Weather permitting I will begin transmissions this coming weekend (Fri, Sat&  Sun).
>
> 73,
> Rob - K3RWR
> FM18qi
>
>    
>> On Sep 17, 2018, at 17:05, DK7FC<selberdenken@posteo.de>  wrote:
>>
>> PS: Even better results with no time offset, again attached.
>> 73, Stefan
>> <K3RWR_LF_2.png>
>>      
>
>
>