Two short guides and one long one. The first walks you through running JTTYAF from first launch to a logged QSO. The second explains the mode from the tones up. The third shows how to capture a debug log and file a bug report we can act on.
Plug in your rig, set your callsign, pick a band, watch the print fill, then work a station with the F-keys and log it. Step by step.
JTTYAF writes a structured event log every time it runs. Share it from Settings in two taps, attach it to a GitHub issue, and we can usually pinpoint what went wrong — instead of guessing.
debug.log and jtty_all.txt liveThe JTTY page covers the waveform, the 59-symbol frame, CRC-12 and the K=10 tail-biting code, the message grammar, chaining, the receiver and the preliminary frequencies — everything the clean-room codec implements. For Q&A-style answers (pricing, supported radios, the FT8AF relationship) head over to the FAQ.
Field reports from real on-the-air use are the most useful thing we get. Open an issue, tell us what happened, drop in a log if you have one.