Although it will be some years before I can have the necessary
equipment to run EbNaut I am *very* interested in QSO modes, so I
want to comment on this.

Please use more than 12 character messages. Rememberfor QSOs you
need room for two call signs plus some kind of signal report or
other piece of information. That means at least 13 characters. Also
some may need to use compound callsigns which are longer than 6
characters. I think 15 should be a minimum, but this still leaves no
room for some compound call signs. More than 15 would be better if
it can be done without giving up too much. Look at some of the
problems they have had with WSJT because of the very short message
length and special compression used.

I must agree that EbNaut can only become popular as a QSO mode after
all the protocols have been worked out *and* someone writes user
friendly software *and* more "beginner level" help is written. As it
stands now, I think only a few "professors" are able to understand
it. Some of us are completely lost.

73,
Paul N1BUG



On 09/18/2018 08:40 AM, Rob Renoud wrote:
> 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 <[email protected]>
>> wrote:
>> 
>> PS: Even better results with no time offset, again attached. 
>> 73, Stefan <K3RWR_LF_2.png>