Hi Stefan, Luis, Paul, Markus and 2200 meter EbNaut,
Thank you all for the comments and suggestions. Lots of good ideas.
Stefan & Paul: Agree that 15 characters is a better choice. Expanding the
text field to 15 characters also allows for compound call signs, etc. Once
full call signs are exchanged at the beginning of a QSO, additional characters
could be made available for information by employing the QRSS practice of
shortening call signs to the last three characters in subsequent exchanges.
Let’s see what happens with this approach - everything is easily modified.
As far as my plans, I want to regularly beacon EbNaut on 2200 meters once the
season kicks off. I also am interested in learning how to use scripts for
automatically decoding EbNaut signals. I also want to fully implement the
full VLF Receiver Tool Kit assortment of applications. I will also be glad to
attempt two-way QSOs on 2200.
I recently applied for permission to operate on 68 - 76 kHz under my current
Experimental License, WH2XXC. Will likely beacon on WSPR and EbNaut to further
explore propagation and operations on these lower LF frequencies.
Markus: I agree that further testing of the 2200 meter band is needed. I will
be glad to conduct any transmissions and modes that fall within the amateur
regulations on 2200 meters that might be useful in better understanding
propagation conditions.
I plan to EbNaut beacon this coming Friday, Saturday, and Sunday on 2200 meters
(137470 Hz, 15 characters, CRC 16, 1.5 sec symbols starting on minutes 00 and
30). I will post a separate announcement with the details shortly.
73,
Rob - K3RWR FM18qi
“Practicing the Art of Radio”
> On Sep 19, 2018, at 03:30, DK7FC <[email protected]> wrote:
>
> 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: [email protected]
>> [mailto:[email protected]] En nombre de Rob Renoud
>> Enviado el: martes, 18 de septiembre de 2018 14:41
>> Para: [email protected]
>> 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
>>
>>
>>>
>>>
>>
>>
>>
>
|
