[CALV-AUXCOMM] Some Notes on MT63

[n3pph at comcast.net]

What works for me in fldigi is having a macro button  labeled RX  and 
<RX> as the contents. The default install of fldigi puts this there. 
After you start transmitting and are done typing hit "RX" and once the 
buffer is empty it will stop transmitting. Since we still need to id you 
may also want to use a macro de ME with the contents <TX> de <MYCALL> as 
this will start your transmission with you id to keep you legal.

73,
Bob N3PPH

------ Original Message ------
From: "Shawn Donley" <n3ae at comcast.net>
To: "ARES Reflector" <calv-ares at mailman.qth.net>
Sent: 4/23/2021 6:00:08 PM
Subject: [CALV-AUXCOMM] Some Notes on MT63

>Here's a nice discussion of MT63 characteristics.
>
>https://www.satern.org/Training/digital_radio/DigitalPrimer4.html
>
>One of the aspects of MT63 that is different is the latency time between going into transmit and data actually being sent, as well as that data showing up at the other end.  Takes a bit to get use to.  When sending, watch for your message going out on the FLDIGI screen and you can switch back to receive as soon as the complete message text has been sent.
>
>From the link above:
>
>Changeover from transmit to receive and vice–versa is therefore considerably slower than most modes due to the data latency in the decoder as the buffers are flushed. It therefore, requires some skill and patience in a QSO as it is not a “break–in” mode as you would think of CW or PSK that have virtually no latency time. Correctly decoded text can take up to 15 seconds to appear on the screen. A clue to synchronized reception can sometimes be gleaned if the software has a digital squelch facility (software based vs. hardware squelch). If the squelch is set up to be closed when no MT63 signal is present, it can often be seen to open as soon as it finds MT63 and ideally the text will follow quite a number of seconds later! In order to make the decoder start printing valid text as soon as possible, software should be chosen that has an effective squelch, so as to minimize feeding the decoder garbage before valid text. Latency in this mode is considerably longer than other 2FSK or multi–AFSK modes like MFSK16 or even MFSK64L. For instance the shortest latency time for MT63 is 3.2 sec. in short interleave 2K transmission mode. The latency time for RTTY is 330 ms. Unlike OLIVIA and MFSK16 the narrower 500 Hz operational modes are much slower using MT63 than the wide (2K) mode. OLIVIA is several times faster and more noise tolerant in the narrow band mode yielding a lower latency, while conversely MT63 becomes much more robust and has a longer latency time in the wide band mode. Accurate text copy can be obtained from MT63–2K when the tones are near or below the noise level under optimal conditions similar to PACTOR III, although at a much lower text throughput.
>______________________________________________________________
>Visit us on the web: https://ares.k3cal.org
>
>CALV-ARES mailing list
>Home: http://mailman.qth.net/mailman/listinfo/calv-ares
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:CALV-ARES at mailman.qth.net
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html