qFT8 User Manual

Table of Contents

Disclaimer of Liability: By using qFT8, you assume all responsibility for legal compliance, safety, and equipment damage

What is qFT8?

qFT8 is an amateur radio app for Android phones and tablets, for iOS, and for Windows, macOS and Linux computers that decodes and transmits FT8, FT4, FT2, LQ8, Q65, MSK144, FST4, FST4W, JS8, or WSPR digital data messages using a transceiver. It also works voice (SSB), Morse code (CW), RTTY and pictures (SSTV) with the same transceiver and the same cable.

Both versions work the same way. Where they differ, this manual says so ("On Android ...", "On the computer ..."). The screenshots show the Android app, and "tap" means tapping the screen on Android or clicking with the mouse on the computer.

qFT8 Camera qFT8 Screenshot

Although qFT8 features out-of-the-box (plug-and-play) support for the QMX and ICOM 7300, you may also use it with any transceiver by placing the phone or computer close to the speaker and microphone with VOX enabled, or using an audio link cable. You may also just try qFT8 without a transceiver: it transmits using the speaker and listens to signals using the microphone. Several phones or computers running qFT8 can contact each other via audio when they are close enough.

qFT8 is a free app and does not contain ads. The license for its source code will be decided when the source code is released (LICENSE).

Luis Quesada Torres (HB9IPH) developed qFT8 in 2026, owns the copyright, and reserves all rights.

qFT8 includes parts from usb-serial-for-android (Copyright © 2011-2020 Google Inc., Mike Wakerly, Andreas Butti, Kai Morich, BSD-3-Clause), Roboto (Copyright © 2015 Google Inc. / Christian Robertson, Apache-2.0), Roboto Mono (Copyright © 2015 Google / The Roboto Mono Project Authors, OFL-1.1), Natural Earth (Public Domain), hamradio-zones-geojson (Copyright © 2024 HB9HIL, HA8TKS, MIT license), RADE V1 and V2 speech-codec model weights (data) (Copyright © 2024, drowe67, BSD-2-Clause), FARGAN vocoder and pitch estimator model weights (data) (Copyright © 2001-2023 Xiph.Org, Skype Limited, Octasic, Jean-Marc Valin, Timothy B. Terriberry, CSIRO, Gregory Maxwell, Mark Borgerding, Erik de Castro Lopo, Mozilla, Amazon, BSD-3-Clause), Big CTY (Copyright © Jim Reisert AD1C), SatNOGS DB (CC BY-SA 4.0), CelesTrak, and Eclipse Temurin / BellSoft Liberica (OpenJDK) Java Runtime (Copyright © Oracle and/or its affiliates and other contributors, GPLv2 with the Classpath Exception). None of these third-party authors or projects endorse or are affiliated with qFT8.

Key Features

Supported Devices

qFT8 supports three main ways of connecting your transceiver:

Direct CAT/Audio Transceivers (USB Cable Control)

These transceivers are directly supported via a USB cable, which handles both CAT control (for frequency tuning and PTT keying) and high-quality USB audio transmission:

On iPhone and iPad the radio is not controlled over a USB cable: see qFT8 on iPhone and iPad.

Leave Settings > Device on AUTO: a supported radio connected by USB is recognized automatically. You can also pick your radio from that list yourself.

Note on External Interfaces (Digirig, generic USB-serial cables): Auto-detection (AUTO) is designed for transceivers with native USB controllers or model-branded cables. When using a generic external interface (like Digirig), auto-detection only sees the generic interface chip and defaults to VOX mode. To use CAT control with radios connected via external interfaces (e.g., Lab599 TX-500), please select your transceiver model by hand in Settings > Device; its serial port and speed are set in Settings > DEVICE CONFIGURATION.

More devices are supported via VOX, which is a partial audio-only integration.

Note: For safety reasons, qFT8 does not allow changing the Tx power of the transceiver. Adjust power manually in your transceiver.

Other transceivers

↑ Back to Table of Contents

qFT8 on a computer (Windows, macOS, Linux)

qFT8 for the computer does the same job as qFT8 for Android: the same modes, the same AUTO and CALL operation, the same log and services. This section is for what is different when you use it on Windows, macOS or Linux: how to install it, how the window is arranged, the two volume sliders, how the sound devices and the radio are chosen, and how to use the mouse. The rest of this manual applies as it is; where a part is different on the computer it says so ("On the computer ...").

Install and first start

Download the file for your system from qft8.com. Every download holds one folder or app with the program, the license and this manual. Nothing else has to be installed: the Java runtime qFT8 needs is inside.

System Windows
Download .zip, 64-bit or 32-bit
You need Windows 10 or newer. Windows 7 SP1 and 8.1 also run it, but they are not supported. Use the 32-bit file only on a 32-bit Windows.
System macOS
Download .dmg, one file for every Mac (Apple Silicon and Intel)
You need macOS 10.13 or newer
System Linux
Download .tar.gz: 64-bit PC, 32-bit PC, ARM 64-bit or ARM 32-bit (a Raspberry Pi)
You need A desktop with a sound server (PulseAudio or PipeWire). Tested on recent Ubuntu, on X11 and on Wayland (through XWayland).
System Any other computer
Download .jar
You need Java 21 or newer, installed by you

qFT8 needs a computer with at least 2 processor cores (4 are recommended) and room for a window of at least 960 x 560 pixels. On 2 cores it works, only more slowly: see Slow computers.

Windows

  1. Open the .zip and drag the qFT8 folder somewhere you keep programs, for example your Documents or Desktop folder. Do not run qFT8 from inside the zip.
  2. Open the folder and double-click qFT8.exe.
  3. Windows may show "Windows protected your PC" the first time. Press More info, then Run anyway. qFT8.exe is signed with the author's certificate; Windows learns to trust a new program slowly.
  4. If Windows asks whether to allow qFT8 (shown as "OpenJDK Platform binary") through the firewall, allow it only on a private network, and only if you use the web remote or the bridge.

macOS

  1. Open the .dmg and drag qFT8 onto the Applications shortcut in the same window. Then eject the .dmg.
  2. Start qFT8 from Applications. If you start it from inside the .dmg window, or from where the browser put it, qFT8 asks "Move qFT8 to Applications?": press MOVE (macOS may ask for your password, as the Finder does) or NOT NOW.
  3. macOS asks once whether qFT8 may use the microphone. Press Allow: this is how qFT8 hears the radio. If you missed or refused it, qFT8 shows a card saying it is waiting for microphone permission; grant it in System Settings > Privacy & Security > Microphone (macOS 13 and newer) or System Preferences > Security & Privacy > Privacy > Microphone (older macOS), and start qFT8 again.

Linux

  1. Unpack the .tar.gz (tar -xzf qFT8-*.tar.gz, or your file manager). It gives a qFT8 folder.
  2. Run ./qFT8 in that folder (double-click works if your file manager runs programs). The first start unpacks the program into ~/.cache/qft8, which takes a few seconds; a newer version replaces the older one there by itself.
  3. The radio's serial (CAT) port belongs to a group: dialout on Ubuntu, Debian and Fedora, uucp on Arch. Its USB sound card belongs to audio. If your account is not in the port's group, qFT8 says so in a card: FIX IT adds you to the group (it asks for your password) and restarts qFT8, so the change applies without logging out. If that does not work, TRY IN A TERMINAL and COPY COMMAND give you the command to run yourself; then log out and back in once.

First start

qFT8 asks for your callsign, as on Android (see Enter Callsign). Right after it, a card named Device configuration opens: choose the radio, then the sound devices connected to it. The waterfall under the input shows what the radio is sending: with the radio on, you should see noise or signals. You can open the same card at any time with the button right of the gear in the bottom bar, and the red No audio badge on the waterfall opens it too. See Sound devices and the radio's connection.

↑ Back to Table of Contents

What is the same, what is different

Everything about operating is the same: your first QSO, the digital modes, AUTO, CALL, the log, ADIF, QRZ, LoTW and the other services, SSB, CW, RTTY, SSTV, the transmit limit and the safety rules: TX is always off when qFT8 starts and only the TX button turns it on, and qFT8 never changes your radio's transmit power. The screenshots in this manual show the Android app; "tap" means clicking with the mouse. The differences:

Screen
Android One screen: the spectrogram and one tab; Orientation and Quadrants in Settings
Computer Three layouts, chosen with the layout button: all in one window, side by side like the phone, or every pane in its own window. More
Volume
Android The phone's volume, and "Produce tone with volume" and "Set device volume ... when using radio" in Settings
Computer Two sliders in the bottom bar: the sound device's own volume and qFT8's tone volume. qFT8 never changes the device volume by itself. More
Sound devices
Android The phone's own, or the radio's USB sound card
Computer You choose them in Device configuration: THE RADIO and YOU (THE OPERATOR). More
Radio connection
Android USB with a permission dialog
Computer A serial (COM) port; no dialog, but on Linux a group and on macOS a microphone permission. More
Input
Android Touch: tap, long-press, swipe
Computer Mouse: click, right-click, wheel. The keyboard does not operate the controls. More
Settings and data
Android Inside the app
Computer In a folder in your user folder; the same settings file as Android. More
Background
Android Foreground service, screen off, battery saving
Computer None of these: the window keeps running while it is open. Slow computers have their own mode. More
Updates
Android Google Play
Computer A notice with a download button; you replace the program yourself. More

The screen layouts and the layout button

The button at the right end of the bottom bar is the layout button. Each click on it changes the layout to the next one: Floating, then Pinned, then All in one, then Floating again. Its picture shows the layout you are in now (a screen reader says its name, for example "Layout: Pinned"). qFT8 remembers the layout for the next start, and the size and place of every window in each layout separately.

The right end of the bottom bar in each layout: the layout button is the last one
The All in one layout: spectrogram, Stations, World Map and QSO log in four parts, Settings at the right, the bottom bar below

Changing the layout only rearranges the windows: nothing is lost, a transmission goes on and TX stays as it was. The World Map has a full screen button (top right of the map): it fills the screen until you press the button again or Esc.

Tip: The Android settings Orientation, Quadrants and App covers (see Screen layouts) do not exist on the computer: the layout button and the size of the window replace them.

↑ Back to Table of Contents

Working with the windows

Volumes: the device and the tone

Two small sliders sit in the bottom bar, between the Device configuration button and the layout button, one above the other. They control two different things, and both matter for transmitting.

How the device slider behaves.

Tip: The two sliders do the work of the volume advice for Android in [QMX Only] Audio Check: if the radio shows that the audio is too low or too high (the QMX's two dots instead of a bar), try other positions of the device volume slider first (for example 70 %, 80 %, 60 %, 100 %), and use the tone volume to fine-tune. Otherwise leave the tone volume at its default (100 %). qFT8 never sets your radio's transmit power: adjust that on the radio.

↑ Back to Table of Contents

Sound devices and the radio's connection

The Device configuration card

Open it with the button right of the gear (it also opens by itself at the first start and from the No audio badge). It has two halves:

The same choices, and more (buffer sizes, the glitch warning), are in Settings > DEVICE CONFIGURATION. The Android rows "Audio system" and "Audio input source" do not exist on the computer. Leave the devices on AUTO: it prefers the radio's own sound card for the radio, and for you a device that is not the radio's.

Notices you may see

By system

Choosing the radio and its port

As on Android, leave Settings > Device on AUTO: a supported radio is recognized when it is plugged in. For a radio behind a generic USB-serial interface (a Digirig, for example), pick the radio by hand, then choose its port in Settings > DEVICE CONFIGURATION > Communication Port Settings > USB Device; baud rate, data bits, stop bits, parity and the keying method (DTR, RTS or CAT) are there too, set by qFT8 for the radio you chose unless you tick Allow overriding settings. Radios that only use sound (VOX) need no port at all. The command line can list the ports and sound devices qFT8 sees.

↑ Back to Table of Contents

Mouse and keyboard

The computer program is operated with the mouse. For safety, the keyboard never presses a control: Tab does not move between controls, and Space and Enter never press a button, tick a box or turn TX on. (A key that is pressed by accident cannot transmit.) What the keyboard does:

The mouse takes the place of the touch gestures:

On Android Tap
On the computer Left click
On Android Long press (a station tab, a group tab, a memory in SSB)
On the computer Right click
On Android Tap on a message in the JS8 chat
On the computer Double click
On Android Select several QSOs in the log
On the computer Ctrl-click, or Shift-click for a range
On Android Swipe on the tuning wheel; drag on the waterfall
On the computer Mouse wheel over the spectrogram in SSB and CW moves the tuning bar (Shift: finer steps); click and drag as on the phone
On Android Pinch to zoom the world map
On the computer Mouse wheel over the map zooms at the pointer; drag moves it

There is no menu bar: everything is in the bottom bar, the panes and Settings.

↑ Back to Table of Contents

Settings: where they live, moving from a phone

qFT8 keeps everything it stores in one folder, the profile folder: settings, passwords, the QSO log, backups and pictures.

The folder stays when you update or delete the program, so a new version finds your settings and your log. At the bottom of the main Settings page, under the version, Configuration directory: shows the folder (click it to open it), and the Open log folder button beside REPORT BUG opens the folder with qFT8's logs, which is useful when you send a bug report. Earlier Windows versions kept it in a settings folder beside qFT8.exe: the first start of a newer version moves it, checks the copy, and keeps the old folder as settings.old.

Moving your settings from a phone (or to one)

EXPORT SETTINGS and IMPORT SETTINGS, on the main Settings page (under Settings files), make and read one file that is the same on Android and on the computer. Export on the phone, copy the file to the computer (mail, cloud, cable), import it there; the other way works as well.

On the computer, an export never replaces a file that is already there (see ADIF Import/Export).

↑ Back to Table of Contents

Several copies, the bridge, the web remote, the command line

Slow computers

Settings > APPLICATION > Slow device / low battery mode makes qFT8 lighter: about 30 pictures a second, the waterfall redrawn less often, and the world map working only while it is shown. It changes only what is drawn, never the decoder: qFT8 decodes the same with it on or off.

Slow mode turns on only when you tick its checkbox, never by itself. On a computer with one or two processor cores, qFT8 asks when it starts whether to turn it on: ENABLE SLOW MODE ticks the box, DISMISS asks again at the next start, and DON'T ASK AGAIN stops asking. On such a computer qFT8 also gives its decoder a fair share of the processor by itself, slow mode or not, so another busy program cannot starve it.

Updates and uninstalling

Updates

With Check for new versions on startup ticked (the default; see Check for new versions on startup), qFT8 asks once a day whether a newer version exists and shows A new version is available with DISMISS and DOWNLOAD NOW, which opens the download page in your browser. qFT8 never updates itself. To update, download the new file and replace the old program:

Your settings and log stay in the profile folder.

Uninstalling

Close qFT8 and delete the program: the qFT8 folder (Windows, Linux) or qFT8 in Applications (macOS); on Linux also ~/.cache/qft8. This keeps your settings and your log. To remove those as well, delete the profile folder (above). That erases your QSO log: export it first with ADIF.

If something does not work

↑ Back to Table of Contents

qFT8 on iPhone and iPad

qFT8 for iPhone and iPad works like qFT8 for Android, and the rest of this manual applies to it; it needs iOS 17 or newer. What is different is how it reaches the radio.

An iPhone or iPad cannot control a radio over a cable: there is no CAT, so qFT8 cannot set the radio's frequency or switch it to transmit through USB. It hears the radio and sends its tones through the radio's USB sound interface, another audio interface or an audio cable. To make the radio transmit, use one of these:

↑ Back to Table of Contents

Quick Setup

Please ensure that you are using the right power supply for the transceiver (e.g. ≤12V for a QMX) or you will damage it.

Please also ensure that the USB cable and adapter you are using to connect the phone or computer and the transceiver is rated for data transfer. On Android, for devices that use connectors other than USB-C, a specific OTG (on-the-go) cable is often required. Most connectivity issues where qFT8 doesn't see the transceiver are due to using an incompatible cable or adapter.

On Android, some devices have USB OTG disabled by default. This must be enabled in your device settings (the option may be hidden in advanced, system, or additional settings). If you are having connection issues—in particular if you are able to receive signal from qFT8 but not transmit and CAT commands don't work even when the device is fully supported (shown in the device dropdown, autorecognized in AUTO mode, etc.)—this is very likely the cause.

Grant Initial Permissions

On Android, when opening qFT8 for the first time, it will request several permissions:

On the computer there are fewer of these. On macOS, the system asks once whether qFT8 may use the microphone: allow it, as this is how qFT8 hears the transceiver. On Linux, using the radio's serial (CAT) port needs your account to be in the port's group (usually dialout); if it is not, qFT8 explains it and offers to fix it.

Key Principle: qFT8 does not submit any information to a server dedicated to this app. All data processing happens locally on your device. You may explicitly authorize sharing callsign, date and time, and optionally approximate location if you enter a valid QRZ API Key.

For more details, see the qFT8 Privacy Policy - License.

Enter Callsign

Inputting a callsign is mandatory for qFT8 to function. If you do not intend to connect to an actual transceiver, any callsign can be input for testing purposes, e.g. XX1XXX.

qFT8 will ask you to input your callsign and acknowledge the following:

Grant USB Connection Permission

On Android, when the transceiver is plugged in and qFT8 is open, a system dialog will appear (the computer does not ask: there, see the Linux note above):

"Open qFT8 to handle Transceiver."

If you have issues connecting the transceiver, see the troubleshooting section The phone or computer doesn't recognize the transceiver or it gets disconnected.

qFT8 automatically configures the transceiver whenever it is connected.

↑ Back to Table of Contents

[QMX Only] Audio Check

Before you start operating, it is important to verify that the audio signal between your phone or computer and the QMX is working correctly. Press the TX button and wait for the QMX to start transmitting in one of the next sequences.

Everything is working

If the TX button shows power output (e.g. 5W), everything is working correctly. On the QMX LCD, you should see a bar under the "A" VFO marker at the top-left of the screen — this means the QMX is receiving a good audio signal from qFT8. You should also confirm that there is no "S" shown after the frequency on the LCD, which would indicate SWR protection.

"S" shown after the frequency

If the QMX LCD shows an "S" after the frequency, it means SWR protection has engaged. Your antenna is not properly tuned for the current band. You can use the SWR check option in the QMX menu to measure the SWR and will need to tune your antenna.

qFT8 has its own check too: when the SWR it reads goes above the limit in Stop transmission if SWR is greater than, it stops the transmission and turns TX OFF, with a warning (on the phone, the computer, the iPhone and the web remote). Nothing is sent in the next slot: tune the antenna, then press TX ON yourself.

Two dots instead of a bar

If the QMX shows two dots instead of a bar under the "A" VFO marker at the top-left of the screen, the audio volume is either too low or too high.

Try: Go to qFT8 Settings, find the "Set device volume to [X] when using radio" option, and try different values (e.g. 70%, 80%, 60%, 100%). One of these should turn the two dots into a bar.

On some phones, this option may not work. In that case, uncheck it and manually adjust the phone's volume to different values (100%, 90%, 80%, etc.) until the bar appears.

Also, common-mode current may be impacting the QMX behavior, and adding a common-mode choke to the antenna may help with audio issues as well.

Nothing under the "A"

If there is no bar and no dots under the "A" VFO marker at the top-left of the QMX LCD screen, qFT8 may not be properly controlling the transceiver. This usually means USB permissions were not granted or were accidentally dismissed. Receiving will work, but transmitting will not.

Try: Unplug the QMX and plug it back in — on Android, the permission dialog should appear again. It may also be that the cable is not suitable for the QMX; try a different USB-C cable.

Once you see a bar under the "A" VFO marker at the top-left of the QMX LCD screen and power output in the TX button, your QMX is properly set up and ready to operate!

↑ Back to Table of Contents

[Optional] Import QSOs

You may now import your existing QSOs; there are two approaches. Both ways require going to settings using the right-most button in the bottom bar of qFT8.

qFT8 Camera qFT8 Settings Button

The manual approach: Go to the "ADIF File Import" section in settings, click the "IMPORT QSOs" button, and select the .adi file to import.

qFT8 Camera qFT8 ADIF Import

The QRZ automatic approach: Requires an active QRZ paid subscription. Go to the "QRZ Syncing" section in settings, enter the QRZ API Key for your callsign, press "VALIDATE", and then click the "IMPORT QSOs FROM QRZ" button. This will also set up automated uploads to QRZ and confirmation checks.

qFT8 Camera qFT8 QRZ Syncing

The LoTW automatic approach: Free of charge. Go to the "LoTW Syncing" section in settings, enter your Callsign and LoTW password, and enable background synchronization if desired. This will also allow you to perform the initial "IMPORT QSOs FROM LoTW".

↑ Back to Table of Contents

Your First QSO With qFT8

Note: Accurate time is critical for FT8. qFT8 automatically synchronizes time upon app initialization via NTP (internet) or GPS (satellites). If you are operating in the field without internet access, you can use the GPS SYNC button in the Settings tab to synchronize your clock directly from GPS satellites. This requires precise location permission and a clear view of the sky.

At this point, the transceiver should be connected to the right power supply and the antenna, and all permissions should be granted. Make sure that the antenna is tuned to a band with a reasonable SWR (ideally consistently below 2) that will not trigger SWR protections. It is a bad idea to disable SWR protection in the QMX; it could damage the finals or the antenna tuner.

You may now choose the band you want to use in the bottom bar of qFT8 or in the transceiver. Setting it in one of them will sync it to the other.

qFT8 Camera qFT8 Band Selector

At this point, the spectrogram will show signals and start decoding messages, and the Stations tab will be updating with the stations you're hearing.

qFT8 Camera qFT8 Stations Button

Pressing the TX button (left-most button in the bottom) will enable transmission.

If everything is correct, the TX button will eventually light up with "TX Transmitting" and will show the transmission power and SWR (e.g., "5.0W SWR 1.2").

qFT8 Camera qFT8 TX Button

Given the "AUTO" mode is selected by default, qFT8 will start making QSOs and logging them in the Log tab.

qFT8 Camera qFT8 Log Button

You may tap in the spectrogram to change the Tx frequency offset (additionally, tapping on the top part of the spectrogram, where the peak indicators are, allows you to input a frequency manually), you may change sequence by tapping the 0 and 1 buttons in the bottom bar, you may tap the different "CALL" buttons to call specific stations, or you may tweak the bar with the "AUTO" button in the Stations tab to decide on the strategy. More on all of these advanced features in the following sections.

Note that qFT8 will start calling stations or, if none of them are reachable, will start calling CQ. Eventually, if everything is properly set up and the propagation is good, qFT8 will achieve QSOs.

If qFT8 is not receiving proper signals and not decoding messages, that is a clear sign that something is wrong: propagation in that band may be closed, the antenna may not be properly tuned, the antenna may not be properly connected to the transceiver, the transceiver may not be properly connected to the phone or computer, or some of your equipment may not be functioning correctly. See the troubleshooting section below for common issues.

↑ Back to Table of Contents

Intro to digital modes

Amateur radio digital modes encode text and data into audio frequency-shift keying (FSK) tones transmitted over single-sideband (SSB) radio. Combining narrow bandwidths, advanced forward error correction (FEC), and strict time synchronization, digital modes enable reliable worldwide communication even when signals are buried deep below the audible noise floor. qFT8 supports the leading modern digital modes—FT8, FT4, FT2, JS8, WSPR, LQ8, Q65, FST4, and FST4W (experimental)—each engineered for distinct operational goals ranging from ultra-weak-signal propagation beaconing to rapid contesting and conversational keyboard-to-keyboard messaging.

FT8

FT8 (Franke-Taylor design, 8-GFSK) is the world's most widely used weak-signal digital protocol, engineered for challenging HF/VHF conditions, multi-hop sporadic-E, and crowded bands. It operates with structured messages, precise 15-second time synchronization, and robust error correction.

Cycles and Sequences

FT8 operates in 15-second cycles. Every communication cycle is strictly timed, starting exactly at 00, 15, 30, and 45 seconds of every minute. For this reason, your device's clock must be accurately synchronized to UTC time.

There are two sequences within the protocol:

Stations generally alternate between transmitting and receiving. A station transmitting in Sequence 0 will listen for a response in Sequence 1, and vice versa. Within each 15-second cycle, the message is transmitted in a window between approximately +0.5s and +13s. This leaves time at the end of the cycle for decoding and at the beginning for preparing the next transmission.

Signal Characteristics

Each FT8 message is transmitted as a sequence of tones with slight frequency variations (sometimes described as "wiggliness"). An FT8 signal is very narrow, occupying only about 50Hz of bandwidth. This efficiency allows dozens of simultaneous conversations to fit within a single 3kHz radio band.

The 6 Stages of a QSO

A standard FT8 contact typically moves through six stages. Here is an example of an exchange between HB9IPH and XX1XXX:

  1. 1/6 CQ: A station looks for anyone to talk to.
    Example: CQ HB9IPH JN47
    Note: JN47 is a Maidenhead grid locator, which indicates the station's approximate geographic location. There may also be a CQ modifier, which is a note for other operators (e.g., CQ SOTA HB9IPH for the Summits On The Air program, or CQ US HB9IPH when trying to contact someone in the US). Both the modifier and location might not fit in the same message; in such cases, the location is omitted. If the callsign is very long, it is possible that neither the location nor the modifier will fit in the CQ!
  2. 2/6 CALL: Another station responds to the CQ.
    Example: HB9IPH XX1XXX JO21
    Note: The responder also shares their location (JO21), which may be omitted if the callsigns are too long to fit everything.
  3. 3/6 RPT: The first station sends a signal report.
    Example: XX1XXX HB9IPH -10
    Note: The signal report (e.g., -10) indicates the signal strength relative to the noise floor in dB.
  4. 4/6 RRPT: The second station acknowledges the report and sends their own.
    Example: HB9IPH XX1XXX R-12
    Note: The "R" prefix confirms the previous report was received, followed by the signal report for the first station.
  5. 5/6 RR73: The first station confirms everything and sends a "Roger-Roger 73".
    Example: XX1XXX HB9IPH RR73
  6. 6/6 73: The second station sends a final "73" to close the contact.
    Example: HB9IPH XX1XXX 73

Because of the Two Generals' Problem, it is theoretically impossible to know for certain that the other station received your last communication unless they confirm so. However, then you would need to confirm their confirmation, and they would need to confirm that, and so on. The FT8 digital mode mitigates this by having structured stages: a QSO can technically be considered complete after stage 4/6 (when both signal reports have been exchanged). In practice, to ensure both stations agree that the exchange happened, a QSO is logged when a station has received an RR73 and has sent out a 73. Effectively, either transmitting an RR73 or a 73 triggers the logging of a QSO.

Note that stations may also call other stations even if they haven't transmitted a CQ first. For example, stations in rare locations may have a "pile-up" of many stations calling them simultaneously; in such cases, the rare station may simply move from one QSO to the next without needing to invite new callers with a CQ.

Some stations may use RRR instead of RR73 in stage 5. In that case, the contact requires an extra exchange: the second station sends 73, and then the first station sends 73 again to finish.

FT8 also supports free text messages (up to 13 characters), but qFT8 does not currently support sending these custom messages.

Protocol Limitations and Fallbacks

FT8 messages are highly compressed into 77 bits. Sometimes, complex information (like long, non-standard callsigns) does not fit in the standard message format.

Messages you will see but never send

Some stations send message shapes that qFT8 shows but does not send itself:

Specifications: S. Franke, B. Somerville, J. Taylor, “The FT4 and FT8 Communication Protocols”, QEX, July/August 2020.

FT4

FT4 is a streamlined digital mode designed specifically for amateur radio contesting, where rapid contact turnover is vital:

Specifications: S. Franke, B. Somerville, J. Taylor, “The FT4 and FT8 Communication Protocols”, QEX, July/August 2020.

FT2

FT2 is designed for ultra-high-speed exchanges under favorable signal conditions, VHF/UHF meteor scatter bursts, and high-rate contesting:

Specifications: no published specification.

JS8

JS8 (Jordan Sherer design, 8-GFSK) is created for conversational ragchewing, keyboard-to-keyboard chat, and ad-hoc networking rather than structured contest exchanges:

Specifications: no published specification.

WSPR

WSPR (Weak Signal Propagation Reporter) is designed exclusively for probing radio propagation paths and automated beaconing rather than two-way conversational QSOs:

Specifications: J. Taylor (K1JT), “WSPRing Around the World”, QST, November 2010.

LQ8

LQ8 is an advanced weak-signal digital mode developed by Luis Quesada (HB9IPH), the author and creator of qFT8:

Specifications: L. Quesada (HB9IPH), “The LQ Digital Mode Family: Protocol Architecture and Reference Specification for Weak-Signal Communications”, arXiv:2609.06427 (2026); reference library: lq_lib.

For more information, specifications, and tools, visit https://lq8.org, the portal for the LQ modes.

LQ4

LQ4 is the faster sibling of LQ8 in the LQ family by Luis Quesada (HB9IPH). It is experimental in qFT8:

LQ2

LQ2 is LQ4’s frame at twice the speed, the fastest of the LQ family. It is experimental in qFT8:

LQ16

LQ16 is LQ8’s frame at half the speed, the most sensitive of the LQ family. It is experimental in qFT8:

Q65

Q65 is a weak-signal QSO mode for difficult paths: ionospheric and tropospheric scatter on 6 m and 2 m, and moonbounce (EME) on 2 m and up. It is experimental in qFT8:

The sub-mode picker, the bands and every option are described in Settings > Q65; the stations list in Q65 is described in The Stations tab.

MSK144

MSK144 is made for meteor scatter on 10 m, 6 m, 2 m and 70 cm. It is experimental in qFT8:

The options are described in Settings > MSK144; the stations list in MSK144 is described in The Stations tab.

FST4

FST4 is a weak-signal QSO mode for the low bands (2200 m, 630 m, 160 m) and for HF when signals are very weak. It is experimental in qFT8:

The options are described in Settings > FST4; the stations list in FST4 is described in The Stations tab. Its beacon companion, FST4W, works like WSPR.

JT65 and JT9

JT65 and JT9 are the older one-minute weak-signal QSO modes. Both are experimental in qFT8:

The options are described in Settings > JT65 and Settings > JT9.

JT4

JT4 is the one-minute weak-signal QSO mode of the VHF, UHF and microwave bands (EME, microwave beacons). It is experimental in qFT8:

The options are described in Settings > JT4.

↑ Back to Table of Contents

qFT8 User Interface

The qFT8 app is split in three parts:

qFT8 Camera qFT8 Overview
  1. The bottom bar: Always visible, to oversee and control transmission and to control qFT8.
  2. The spectrogram: Always visible, to see decoded messages, see UTC time live and tuned frequency, and control transmission frequency offset.
  3. The tab area: Shows one out of four tabs (Stations, Log, World Map, and Settings). Which one is shown here can be controlled with the buttons at the right-most part of the bottom bar.

The following sections describe all these components in detail.

The Bottom bar

The bottom bar shows important information: the transmission armed/disarmed state, whether qFT8 is transmitting, the transmission power, the Standing Wave Ratio (SWR), the message being transmitted, the current and selected sequence, the band selector, and the buttons to navigate the different tabs.

qFT8 Camera qFT8 Bottom bar

These are the components of the bottom bar in detail:

  1. The cycle progress bar: The yellow bar starts at 0s within the cycle (left-most) and ends at 15s within the cycle (right-most).
  2. The Tx trigger marker: The red dot at the left part of the bar indicates the Tx trigger time. If Tx is ON (see item #4) and the current sequence is the selected sequence (see item #6) transmission starts at this point.
  3. The decoding time marker: The white dot at the right part of the bar indicates the decoding time, that is, when messages are decoded from signals received and subsequently processed.
  4. The TX button: Can be disarmed (OFF) or armed (ON). It also shows when transmission is happening, and the transmit power and SWR; while transmitting, the power and the SWR are the average of the radio's last 2 seconds of readings, so they do not flicker. The button's words stay in English in every language. It reads NO TX / SDR while a receive-only SDR is the receiver, NO TX / I/Q while a QMX is in I/Q mode, NO TX / SWL in SWL mode and NO TX / RX while a receiver (marine VHF, airband, a beacon or time-signal receiver ...) has the radio: nothing can transmit then, and TX stays OFF afterwards until you press TX ON again. With the Ham features off it reads NO CALLSIGN on red; tapping it explains that transmitting needs an amateur licence, a callsign and the Ham features, and SET UP asks for your callsign and switches the Ham features on (TX stays OFF). In QMX firmwares above 1_04, this button will show "HOLD: TUNE". Holding the button will enable tuning mode and report on SWR live.
  5. The message selector: It shows the message selected to be sent or being sent (if that is the case, highlighted in yellow). In AUTO mode, it is managed automatically. In CALL mode it is also managed automatically by default, but it can be tapped on to select the next message to send manually. In FT8, FT4, FT2 and LQ8 the list ends with Free text...: type a short message of your own (in FT8 / FT4 / FT2 up to 13 characters, A-Z, 0-9, space and + - . / ?; an accented letter is sent as its plain letter; in LQ8 the editor shows how full the message is). A CQ or QSO message is refused there (pick it from the list). Picked while AUTO is selected, it switches to a manual CQ.
  6. The sequence selector: The yellow line on top of the buttons show the current sequence (0 or 1). Tapping on 0 or 1 selects that sequence for outgoing transmissions.
  7. The mode selector: It changes the mode (every mode is listed in The mode selector, below). Changing from the digital modes to a mode with its own pane (SSB, CW, RTTY, SSTV, and the other ones that change the bottom bar and the Stations tab as their sections describe), back, or between them switches TX OFF: arm it again when you are ready. Changing between digital modes leaves it as it is.
  8. The band selector: Opens the list of bands with their frequencies and, when a transceiver is connected, changes the band in the transceiver (see The band selector, below).
  9. The Stations tab button: Opens the tab that lists all the stations you've heard or can communicate with.
  10. The Log tab button: Opens the tab that lists all the QSO you've made. This button will be marked with a yellow dot if you have QSOs that aren't uploaded to QRZ.
  11. The World Map tab button: Opens the tab that displays the interactive global world map.
  12. The Settings tab button: Opens the tab to configure qFT8.
↑ Back to Table of Contents

The Spectrogram

The spectrogram shows a peak view, and the waterfall with incoming signals and messages, outgoing signals and messages, markers for the change of sequence annotated with UTC time and time to decode, and the selected offset frequency for transmission.

qFT8 Camera qFT8 Spectrogram

These are the components of the spectrogram in detail:

  1. Waterfall view: Displays the recent history of received signals over time. Tapping in that view will change the selected frequency offset.
  2. Real-time peaks: Show the instantaneous strength of signals across the frequency range. Tapping in that view will open a dialog to input the precise selected frequency offset.
  3. Sequence separators: These red horizontal lines act as visual separators of cycles, and are annotated with UTC time and time spent decoding.
  4. Selected frequency offset: This vertical yellow overlay on the spectrogram indicates the currently selected frequency offset for transmission.
  5. Incoming messages, shown color-coded:
    • Green: CQ messages.
    • Cyan: Messages between other stations.
    • Yellow: Your transmitted messages.
    • Orange: Incoming messages directed to you.
  6. Current UTC time and sequence: Displayed at the top of the waterfall.
  7. Tuned frequency and band: Frequency and band the transceiver is currently tuned to.
  8. Frequency axis: Shows the frequency scale in Hz within the selected band.
↑ Back to Table of Contents

The Stations tab

The Stations tab is the command center for monitoring activity on the band and operating qFT8. It features filtering and automation controls at the top, followed by a list of active stations.

qFT8 Camera qFT8 Stations tab

These are the components of the Stations tab in detail:

  1. AUTO call mode button: Engaging "AUTO" will try to call the best station according to the criteria selected by the user.
  2. Manual CALL mode button: Engaging "CALL" for a station will insist on calling that station until achieving a QSO, then will fall back to "AUTO".
  3. Target: Sets the criteria for the AUTO mode:
    • Anyone: Any callsign that you don't have a QSO for yet.
    • Nearby: Prioritize nearest stations based on Maidenhead grid distance.
    • Far: Prioritize farthest stations based on Maidenhead grid distance.
    • Signal strength: Prioritize stations with the strongest signal (SNR).
    • Call CQ: Just calls CQ and replies to any station that calls your station.
    • POTA hunter: Prioritize Parks on the Air stations.
    • SOTA hunter: Prioritize Summits on the Air stations.
    • POTA + SOTA hunter: Prioritize both Parks on the Air and Summits on the Air stations, then stations that are neither, ordered by SNR.
    • DXCC: Prioritize new countries/entities.
    • Grid: Prioritize new Maidenhead grid squares.
    • ITU zone: Prioritize new ITU zones.
    • CQ zone: Prioritize new CQ zones.
    • I/C/D/G: Prioritize first ITU zone, then CQ zone, then DXCC, then Grid.
    In all cases, stations that meet the same criteria are sorted by signal strength. For example, Anyone will prioritize new callsigns first, but among them the strongest signals will be at the top of the list. The stations that meet the target criteria are always listed first; a short gap with the line "Stations below don't meet the target criteria" separates them from the rest. When no station meets the criteria, the line "None of the stations are targets" is shown at the top of the list.
  4. Periodicity: How often to contact that target:
    • once: In a lifetime.
    • daily: Once per UTC date.
    • weekly: Once every 7 days rolling window.
    • monthly: Once every month rolling window.
    • yearly: Once every year rolling window.
  5. Qualifier: How those constraints apply:
    • per callsign
    • in different bands
    • in different modes
    • until zone confirmed
    • per band+until zone
    • per mode+until zone
    • in different bands or modes
    • per band/mode+until zone
  6. Spy mode: When enabled, qFT8 will also try to call stations you haven't heard call CQ yet (marked as DIRECT). This is useful to have more stations at reach and join pile-ups.
  7. Busy mode: When enabled, qFT8 will also try to call stations engaged in a QSO with someone else (marked as BUSY). This is useful to join a pile-up.
  8. + button: Manually call any arbitrary station by inputting their callsign.
  9. Station information: Displays detailed status for each decoded station.

Individual station entries consist of four information-rich rows:

The first row shows station details (left to right):

The second row shows communication status (left to right):

The third and fourth rows show message exchanges with that station, including UTC time, frequency offset, and the message text (prefixed with RX: for received messages or TX: for transmitted messages). Depending on the Stations display mode configured in Settings → Application → User interface (which defaults to Compact - Last Rx, with options for Compact - Alternating, Compact - Last Rx/Tx, and Expanded), station cards display either three rows or four rows with both Rx and Tx messages.

Key visual indicators to watch for:

Stations are automatically sorted by relevance. Changing your target criteria or constraints will immediately re-sort the list.

The order of the list

From the top of the list to the bottom:

  1. Stations you have just completed a QSO with (DONE).
  2. The station you chose with CALL.
  3. Stations in a QSO with you, the furthest along first: the ones waiting for your 73, then the ones that sent you their report, then the ones that called you.
  4. Stations on your band that meet the target criteria, the best match first. Among equal matches the strongest signal comes first; with a distance target, the distance decides first.
  5. The line “Stations below don't meet the target criteria”, then every other station, ordered the same way.
  6. Stations no longer heard (GONE), then, at the very bottom, stations whose callsign and yours cannot fit together in one message (TOO LONG).

Within each group, stations last heard on another band come after the ones on your band. Stations heard in another mode are not shown; they come back the first time they are heard in the current mode. Stations you added with the + button always stay in the list. The line between the targets and the other stations is the same on the phone, the computer, the iPhone and the web remote; it is only a label, and tapping it does nothing.

The Stations tab in every QSO mode

FT8, FT4, FT2, LQ8, Q65, MSK144 and FST4 all use this same tab: the same controls at the top, the same station rows and the same order. The list shows only the stations heard in the mode you are using. What changes from mode to mode:

FT8
Period 15 s
Steps of a QSO 1/6 – 6/6
FT4
Period 7.5 s
Steps of a QSO 1/6 – 6/6
FT2
Period 3.75 s
Steps of a QSO 1/6 – 6/6
LQ8
Period 15 s
Steps of a QSO 1/4 – 4/4
Q65
Period 15 – 300 s
Steps of a QSO 1/6 – 6/6
Chosen in the bottom bar the sub-mode (30A ...)
MSK144
Period 5 – 30 s
Steps of a QSO 1/6 – 6/6
Chosen in the bottom bar the period (15s ...)
FST4
Period 15 – 1800 s
Steps of a QSO 1/6 – 6/6
Chosen in the bottom bar the period

The picker beside the mode in the bottom bar is there on the phone, the computer, the iPhone and the web remote. Sequence 0 and 1 are the even and odd periods of the mode, whatever their length. With the long periods, a station counts as no longer heard (GONE) only after a matching number of silent periods.

FT4 / FT2: Everything works as in FT8, only faster. Each period is short, so a QSO moves quickly: in FT2 a whole QSO can be over in well under a minute.

LQ8: An LQ8 QSO has four steps instead of six, and the state column shows them:

There is no separate report step and no RR73 in LQ8: this is how the protocol is made. DIRECT, BUSY, GONE and TOO LONG mean the same as in FT8. If you press CALL on a station whose callsign cannot be sent in LQ8 together with yours, qFT8 says so and does not call.

Q65: Choose the sub-mode beside the mode in the bottom bar before you call; stations using another sub-mode are not decoded. With the longer sub-modes each step of the QSO takes a whole period (up to 5 minutes), so a QSO takes much longer, and the station rows change once per period. With averaging on, a station may appear only after several of its transmissions have been added up. The long sub-modes need a large enough Continuous transmission limit.

MSK144: Choose the period beside the mode in the bottom bar. A station appears when one of its pings is decoded, so rows come and go with the meteors; its signal strength is that of the ping, and its Δt is the moment of the ping within the period, not a clock error. A short message is shown with both callsigns, like the long form, for example K1ABC W9XYZ R+03; only the two stations of that QSO can read it. With short messages turned on in Settings, qFT8 sends your reports, RRR and 73 that way; your CQ, your call and your RR73 always go out as normal messages. All stations transmit at 1500 Hz, so a station's offset tells you little.

FST4: Choose the period beside the mode in the bottom bar; it must be the same as the other station's. With 900 or 1800 second periods one QSO can take an hour or more, and each of your transmissions keeps the radio keyed for up to 30 minutes: set the Continuous transmission limit to allow it, or qFT8 will not transmit.

The AUTO settings, the targets and the retries are the same in every one of these modes; see Automated operation (AUTO).

↑ Back to Table of Contents

The mode selector

The button with the mode's name in the bottom bar opens the mode selector. At the top are two tabs, HAM and SWL, that stay in place while the list scrolls, and at their right the PROBE button (see below). The selector opens on the tab you used last, keeps its size when you switch tabs (a taller tab scrolls inside it) and closes when you tap outside it. With only the Ham features on there is no tab row (only HAM); with the SWL features on both tabs show, and with the Ham features off the HAM tab stays, for receiving only.

The gear at the right of the title opens Mode Selection (also in Settings > MODES): tick the modes you want listed, with ALL and NONE for each section. The selector then lists only the ticked modes; a section or a tab with none ticked disappears, and the mode in use is always listed. Everything is ticked at first; RESET TO DEFAULTS ticks everything again. The Experimental check box still applies.

PROBE (mode detector, experimental; listed with the Experimental check box on) opens the free AUTO MODE DETECTOR, whatever is switched on (the bottom bar then reads PROBE). It names the signals on the spectrogram as you watch; the ones qFT8 decoded get a check mark. Tap a label and qFT8 asks “Go to FT8 on 14075.250 kHz?” (the mode and the frequency of that signal): YES switches to it. It is experimental: it can be wrong, and it never names room noise, voices, music or hum. In Settings > Spectrogram the check box Name other signals on the spectrogram (mode detector) lets it keep listening while you operate.

The band selector

The band button of the bottom bar opens the band selector: the bands one per row, each with the frequencies of the current mode (for example FT8 on 20 m: 14.074 Standard and 14.090 DXpedition; on 6 m: 50.313 and 50.323 Alternate). Tap a frequency to go there; the one you pick is remembered for each mode and band. Each mode lists the frequencies its stations meet on (the "watering holes"): the keyboard modes of the RTTY pane (PSK, Olivia, Hell, JTTY ...) show their own, and FreeDV shows its calling frequencies (20 m 14.236 and 14.240, 40 m 7.177 and 7.197, ...; 80 m and 60 m by region). A band in red has no frequency in this mode (60 m in FT4, for example) and cannot be picked. Below the bands are your custom bands A to E (an empty one opens the settings to fill it), a box for any frequency (in FT8 and the other band modes it becomes that band's frequency; in SSB, CW, RTTY and SSTV it tunes the radio), a gear to the band settings and the check box Keep the radio on the selected frequency: on, a radio turned by hand is put back on the frequency you chose; off, qFT8 follows the radio. It closes when you tap outside it. In marine VHF, airband, the broadcast radio and the signals receivers the button only shows the receiver's frequency (for example 156.8) and does not open the list; pick an amateur mode to change band. In the web remote each band of the list shows the same frequency buttons.

The Log tab

The log tab shows achieved QSOs.

qFT8 Camera qFT8 Log tab

These are the components of the Log tab in detail:

  1. Callsign text filter: A filter for QSOs based on whether the callsign contains the text inputted.
  2. Status filter: A filter for QSOs that shows:
    • QSO / SWL: once something has been heard, or the SWL features are on, the top of the log has one dropdown, QSO / SWL, in the colour of the log you are looking at (QSO blue, SWL red). QSO, your own log, is the default; SWL shows what you heard, newest first, in its place. The choice is remembered. The SWL page has the same filter bar (Contains, Show, recent), which searches the whole SWL log, and a tap on an entry opens it to edit or delete (nothing is ever deleted on eQSL or any online service). Beside the + a file button asks IMPORT QSO LOG / EXPORT QSO LOG, or IMPORT SWL LOG / EXPORT SWL LOG, for the log shown (the same as Settings > Log files; the web remote only exports).
    • All: Shows all recorded QSOs.
    • Confirmed: Shows only QSOs that have been confirmed.
    • POTA hunter / SOTA hunter: Shows the QSOs with a park or a summit.
    • Not confirmed: Shows QSOs that are not yet confirmed.
    • Not uploaded: Shows QSOs that are not uploaded yet (see When does a QSO count as uploaded?).
    • Duplicated: Shows QSOs that appear more than once in the log.
    • Rejected: Shows QSOs that an online logbook refused.
    • Other callsign: Shows QSOs recorded with a callsign different from the one currently configured.
  3. Recent limit filter: A filter that shows only the most recent 100 QSOs with the given criteria.
  4. The list of QSOs: Displays the log entries with the following columns (from left to right):
    • QRZ: Indicates your history with this station:
      • ✗: No QSO records.
      • ✓: Logged locally / Pending upload.
      • ✓🕒: Uploaded to LoTW, awaiting confirmation.
      • ✓: Uploaded to QRZ.
      • ★: Confirmed on QRZ or LoTW (for QRZ-uploaded QSOs) or manually.
      • ⟳ / ♻️: Circular arrow: Reported as duplicate by QRZ (only shown when actual duplicate entries exist in the log; unique QSOs already on QRZ are automatically marked as uploaded with a green tick).
      • ❕: Station callsign mismatch, already uploaded.
      • ⚠️: Station callsign mismatch, not uploaded.
      • ⛔: Rejected status.
    • Callsign: The station's callsign.
    • DXCC: The country or entity this station's callsign belongs to.
    • Grid cell: The Maidenhead grid square this station is reporting.
    • CQ zone: The CQ zone this station's callsign belongs to.
    • ITU zone: The ITU zone this station's callsign belongs to.
    • Band: The band on which the station was last heard.

Key visual indicators to watch for:

Editing QSOs: Tapping on any QSO in the list opens the QSO editor, where every field of the QSO can be corrected, the QSO can be marked as confirmed or unconfirmed by hand, uploaded again, or deleted. Deleting a QSO only deletes it in the app, never on QRZ or LoTW, and is irreversible unless you keep an exported copy of the log file or it was uploaded to QRZ.

Logging by hand and selecting: The + button opens the logger, to log QSOs you made yourself. A long press on a QSO starts a selection of several QSOs.

↑ Back to Table of Contents

The World Map tab

The World Map tab displays a real-time, interactive global map showing station geography, decoded traffic, your QSO achievements, and solar propagation conditions.

qFT8 Camera qFT8 World Map tab

These are the components and features of the World Map tab in detail:

  1. Interactive Map Canvas & Controls:
    • Navigation: Drag to pan smoothly across the globe with horizontal wrapping across the antimeridian. Pinch with two fingers to zoom in and out.
    • Map Themes: Switch between four visual styles (Bright Future, Console, Earth, and Midnight Navy) from the top toolbar.
    • HUD Coordinates: Displays real-time geographic coordinates (latitude, longitude) and Maidenhead grid locator under your touch position.
  2. Left Toolbar (Overlay & Info Toggles):
    • INFO: Toggles the on-screen information overlay cards (time, solar terminator, subsolar position, and crosshair coordinates).
    • MSGs: Toggles direct message route overlays and markers: shown in Orange for received messages (addressed to your station) and Yellow for sent messages (transmitted from your station). Tapping the arrow midpoint opens the message text overlay.
    • QSOs: Toggles your recent session contact markers (Amber for logged, Emerald for confirmed). With both MSGs and SPOT off, a thin line joins your station to each QSO station on the map (no arrows), so you see at a glance where your QSOs went; the shared map picture shows these lines too.
    • SPOT: Toggles live decoded traffic spots on the band heard by your station (Cyan for RX/CQ) and reverse spotters reporting your signal on PSKReporter / WSPRnet (Red diamonds).
    • SOTA: Toggles Summits On The Air summit references and active summit activators (⛰️).
    • POTA: Toggles Parks On The Air park references and active park activators (🌲).
    • Band: Shows band propagation from online reports and a blindspot around the user. This is updated in real time when switching band if there's internet connection.

    The SOTA, POTA, STATS, and SPOT buttons may be blinking, this means it was not possible to download updates.

  3. Right Toolbar (Achievement & Boundary Layers):
    • STATS: Toggles the summary statistics panel showing total logged and confirmed counts for the active boundary layer.
    • DXCC: Displays country and territory boundaries color-coded by your log status (Green for logged/unconfirmed, Yellow for confirmed). Small island and micro-entities appear as visible markers.
    • GRID: Global Maidenhead grid squares (fields and 4-character squares) with achievement fills.
    • ITU: Overlays the 90 ITU radio zones with achievement fills.
    • CQ: Overlays the 40 CQ magazine WAZ zones with achievement fills.
  4. SAT and the compass button: satellites on the map and the map compass have their own section, Satellites and the map compass.
  5. Entity Details Card & Quick CALL Action:

    Tapping on any station, spot, park, or summit opens an informative detail card displaying:

    • Callsign or reference name, DXCC entity, and park/summit title.
    • Decoded message text, frequency, band, and mode.
    • Signal strength (SNR) or signal report (RST).
    • Grid locator, distance (km / mi), bearing (°), and elapsed time.
    • CALL button: Instantly initiate contact with the station (automatically switching band and operating mode if necessary).
↑ Back to Table of Contents

The Settings tab

The settings tab allows configuration of qFT8.

qFT8 Camera qFT8 Settings tab

The main Settings page, from top to bottom:

Speakers and microphone

The digital modes only need one sound device: the radio's. SSB and CW need a second one for you: a speaker or headphones to hear the radio, and for SSB a microphone to talk into. These two must never be the radio's own sound card, because what you say would loop straight back.

qFT8 Camera qFT8 Speakers and microphone

There are two choices:

Both start on AUTO, which picks a device that is not the radio's: on a phone a headset when one is connected and otherwise the phone's own microphone and speaker; on the computer the first sound device that is not the radio's card. Change them only if AUTO picked the wrong one.

Tip: Use headphones for SSB. With a loudspeaker next to the microphone, the received audio can key the VOX or be heard in your transmission.

The CAT console

CAT CONSOLE (Settings, under Device) is for talking to the radio yourself, in its own command language. Type a command in the box at the bottom, for example FA; on a QMX or a Kenwood, and press SEND. The log above shows what is sent and what the radio answers. EXPORT saves or shares that log as a text file and CLEAR empties it.

The Settings pages

Each button with an arrow opens a page of its own; ‹ back at its top returns to the main Settings page. Most pages end with RESET TO DEFAULTS, which puts back that page's settings only (never an account, a key, a password or a QSO).

DEVICE CONFIGURATION

TIME AND LOCATION

APPLICATION SETTINGS

SPECTROGRAM

WORLD MAP

AUTO OPERATION

DIGITAL MODES

Focus decoding on the station you are working (AUTO mode) and Focus decoding on the station you are working (manual CALL) are two sliders, from 0 to 30 %: the share of the decoder's time that goes first to the station you are working; the rest goes to every other station. They act only while you are calling or working a station with TX on; with no contact, every station gets all the decoding time. The first applies when AUTO chose the station, the second when you chose it yourself with CALL in the Stations tab. At 0 % the decoder works exactly as without them. By default AUTO gets 5 % and a station you CALL gets 10 %. With several stations marked CALL at once, they share the one percentage. The percentage is a cap: time your contact does not need goes back to the other stations. For one station about 2 % is enough; higher values help when several stations are marked CALL at once, in LQ8, and on slower phones and computers, where the same work takes a bigger part of the time. It costs about one decode of another station in 2,000. The value is shown next to each slider; tap it to type a value. They work in FT8, FT4, FT2, LQ8, LQ4, LQ2, LQ16 for now; in the other modes they are greyed out and say Not yet for this mode.

Stations you add by hand with + in the Stations tab (the 10 most recently added) are looked for in every slot anywhere in the band, even before they have been heard, within the same share (the AUTO one when TX is off or nobody is being worked; at 0 % this search is off). Once such a station has been heard, it is looked for where it was heard.

Continue decoding after the end of the cycle (on by default in the computer program, off on the phone and the iPhone) lets the decoder keep working on a period after qFT8 has decided what to send next, until the next period's decoding starts; what it finds then is a late decode. On a phone or tablet this keeps the processor busy for most of each period, so the device uses more battery and can get warm: that is why it is off there by default. A late decode never changes a transmission already decided, and the next period is always decoded first. The waterfall labels each late decode as soon as it is found, on its own period and frequency, also during a transmission. Update stations as soon as late decoding is done (greyed out while the checkbox is off) says when late decodes reach the Stations tab, the map, the log and AUTO: No keeps them and adds them all together with the next period's decodes, just before qFT8 decides again, so the list does not change under your finger; In AUTO mode (the default) adds them as soon as they arrive while AUTO is selected, and keeps them as with No while you CALL a station yourself; Always adds them as soon as they arrive. While you transmit they always wait until the transmission ends. Each late decode keeps the time of its own period. Late decoding goes on while you transmit, at the lowest priority, so your transmission always comes first. On a phone or iPhone that is getting warm, late decoding pauses until it cools down. It works in FT8 and LQ8 for now.

The message is chosen once more as your transmission starts (FT8 and LQ8, in AUTO; nothing to set). The first second of every FT8 and LQ8 transmission is the same whatever its message (the sync), so while it plays qFT8 keeps decoding the period before it, and AUTO chooses the message once more just before the first data symbol: a reply found only then is answered in this transmission instead of the next one. The other stations receive exactly the final message. Whether you transmit is still decided at the usual moment; a message you pick yourself always wins; the screen shows the message once it is final. This is the only way something decoded after the decision can change what is sent, and only before the data symbols start. On a device that keeps a lot of audio queued there is no time for it, and the first choice is sent, as before.

BAND SELECTION

DATA SOURCES

What qFT8 downloads for the map, all on by default: spots from PSKReporter and WSPRnet, LQ8 activity, SOTA and POTA activations, and propagation reports. Use the qFT8 data cache fetches this public data from qFT8's own server first, and from the original sites only when that fails; LQ8 activity, events and satellites always come from qFT8's service. Not shown while the world map is turned off.

DELETE QSOs

DELETE ALL QSOs, DELETE QSOs FOR OTHER CALLSIGNS (QSOs logged under a callsign that is not your current one) and DELETE ALL DUPLICATE QSOs. Each asks first. They delete only the QSOs on this device, never on an online service.

Settings files

EXPORT SETTINGS saves all your settings into one file and IMPORT SETTINGS reads it back, on this device or another one, phone or computer (see Settings: where they live, moving from a phone). The file holds your keys and passwords: never share it.

Raw message logs

qFT8 can keep a plain text record of every message it receives, in every mode: your partners' messages and everyone else's. This is useful to show that a contact took place when it was never completed or logged, for example a DXpedition QSO where the last 73 was lost. Your own transmissions are not in these files.

Turn it on at the top of Settings > More settings > MODES: Log all decoded messages (off by default). OPEN FOLDER under it takes you to the files. Nothing is sent anywhere, and nothing is deleted automatically.

The files are in a folder called raw_logs. It has one folder per day, named after the UTC date (raw_logs/2026-11-07/), and one file per mode in each day folder (FT8.tsv, LQ8.tsv, CW.tsv, ...). A new day starts at 00:00 UTC.

Each file is tab-separated text. The first line names the mode and the qFT8 version, the second line names the columns, and after that there is one line per message, added as it is received. Times are in UTC and frequencies in Hz. Open a file in a spreadsheet (LibreOffice Calc, Excel, Numbers) or a text editor and search for the callsign. Each line shows the time, the frequency, the signal report and the exact message the station sent.

One short example per kind of mode (columns shortened here):

A busy FT8 band fills about 3 to 6 MB a day. Delete old day folders yourself when you no longer need them.

Community

The Community section of Settings has two buttons that open qFT8's groups on Telegram in your browser or the Telegram app: qFT8 Telegram group (news, help and test versions) and LQ8 Telegram group (the LQ8 mode's community).

↑ Back to Table of Contents

Automated operation (AUTO)

AUTO mode is the primary way to use qFT8. In this mode, the application automatically analyzes the decoded messages at the end of every cycle and selects the most relevant station to contact based on your target criteria.

How Target Selection Works

The Stations tab displays a list of active stations, sorted such that the most relevant candidates (based on your criteria) appear at the top. At the end of each decode cycle, qFT8 looks at this sorted list and attempts to call the first eligible station. If no eligible target is found, it will automatically start calling CQ to attract callers. qFT8 always replies to calls in AUTO mode.

Criteria and Filters

You can fine-tune the automation using the three dropdown menus at the top of the Stations tab:

Manual Override: You can always manually intervene by tapping the CALL button for a specific station. This enters CALL mode for that specific QSO. Once finished, qFT8 seamlessly drops back into AUTO mode.

Directed CQs

Some stations call CQ for a part of the world only: CQ DX, CQ NA, CQ JA. The word after CQ is their CQ modifier. With Avoid calling stations whose CQ modifier does not target us ticked (Settings > AUTO OPERATION, on by default), AUTO does not call a station whose CQ is not meant for you. Where you are is taken from the country of your callsign and, when that is not known, from your locator.

Their CQ modifier DX
AUTO calls them when we are on another continent than the caller
Their CQ modifier NA
AUTO calls them when we are in North America (Central America and the Caribbean included)
Their CQ modifier SA
AUTO calls them when we are in South America
Their CQ modifier EU, EUR
AUTO calls them when we are in Europe
Their CQ modifier AS, ASIA
AUTO calls them when we are in Asia
Their CQ modifier AF, AFR
AUTO calls them when we are in Africa
Their CQ modifier OC, PAC
AUTO calls them when we are in Oceania
Their CQ modifier AN, ANT
AUTO calls them when we are in Antarctica
Their CQ modifier USA, US, W, K
AUTO calls them when our country is the United States (not Hawaii, not Alaska: those are asked for as KH6 and KL)
Their CQ modifier VE, CAN
AUTO calls them when our country is Canada
Their CQ modifier JA, JPN
AUTO calls them when our country is Japan
Their CQ modifier VK
AUTO calls them when our country is Australia
Their CQ modifier ZL
AUTO calls them when our country is New Zealand
Their CQ modifier UK, G
AUTO calls them when our country is England, Scotland, Wales, Northern Ireland or one of their islands
Their CQ modifier DL
AUTO calls them when our country is Germany
Their CQ modifier EA
AUTO calls them when our country is Spain (not the Balearic Islands, the Canary Islands, Ceuta and Melilla: those are asked for as EA6, EA8 and EA9)
Their CQ modifier BY, CHN
AUTO calls them when our country is China
Their CQ modifier UA, RUS
AUTO calls them when our country is Russia (European or Asiatic)
Their CQ modifier PY
AUTO calls them when our country is Brazil
Their CQ modifier LU
AUTO calls them when our country is Argentina
Their CQ modifier ZS
AUTO calls them when our country is South Africa
Their CQ modifier VU
AUTO calls them when our country is India
Their CQ modifier HL
AUTO calls them when our country is South Korea
Their CQ modifier YB
AUTO calls them when our country is Indonesia
Their CQ modifier CAR
AUTO calls them when our country is in the Caribbean
Their CQ modifier ME
AUTO calls them when our country is in the Middle East
Their CQ modifier A country's callsign prefix of one to three characters (F, I, SM, 9A, KH6, EA8...)
AUTO calls them when our country is that country
Their CQ modifier Anything else (TEST, POTA, SOTA, QRP, FD, WW, state and province codes, free text)
AUTO calls them when always: it is not about a place

Retry Mechanism

To prevent qFT8 from calling a non-responsive station indefinitely, qFT8 offers a built-in retry and ban system, enabled by default. You can configure these in the Settings tab under Retry Logic:

Example Optimized Setups

Here are some recommended combinations of criteria for common goals:

Goal Maximize unique stations
Target Anyone
Interval Once
Condition Per callsign or zone
Goal Maximize unique stations per band
Target Anyone
Interval Once
Condition In different bands
Goal Maximize unique DXCC entities
Target DXCC
Interval Once
Condition Per callsign or zone
Goal Maximize unique DXCC per band
Target DXCC
Interval Once
Condition In different bands
Goal Maximize confirmed DXCC entities
Target DXCC
Interval Once
Condition Until zone confirmed
Goal Maximize confirmed DXCC per band
Target DXCC
Interval Once
Condition Per band + Until zone
Goal Collect unique Grids per band
Target Grid
Interval Once
Condition Per band + Until zone
Goal Work all Zones (CQ/ITU)
Target I/C/D/G
Interval Once
Condition Until zone confirmed
Goal Contest: Unique stations on different bands
Target Anyone
Interval Once
Condition In different bands
Goal Contest: Points for same station on different days
Target Anyone
Interval Daily
Condition In different bands

Note that in all these cases, you may enable Spy and Busy to reach out to more stations and enter their pile-ups.

Note: If your callsign is not standard (e.g. with "/"-separated suffixes or prefixes, long callsigns, or other callsigns with numbers in rare positions), you probably want to set Target to Call CQ as your callsign will likely be sent out hashed and only stations who have seen you call CQ will be able to map the hash to your callsign. You may still call stations but they will only map the message to your callsign if they recently heard you call CQ.

↑ Back to Table of Contents

Manual operation (CALL)

While qFT8 is highly automated, you can take control at any time. Tapping the CALL button next to any station in the Stations tab will immediately enter CALL mode and attempt to establish a QSO with that specific station.

Once the QSO for the manual target is completed (successfully or not), qFT8 will automatically fallback to AUTO mode and resume your previous automated strategy (e.g., calling CQ).

Timing for Manual Operators

If you find that you'd like more time at the end of the cycle to make manual decisions, you can get yourself more margin by adjusting the FT8 Settings in the Settings tab:

Warning: Adjusting these values aggressively into the margins may make your messages much more difficult for other stations to decode, as you are reducing the effective time available for the actual FT8 signal within the sync window.

↑ Back to Table of Contents

Editing and logging QSOs by hand

qFT8 logs the QSOs it makes in the digital modes by itself. This section covers the three things you do by hand in the Log tab: correcting a QSO, logging a QSO you made in another way (voice, Morse, another radio), and working on several QSOs at once.

The QSO editor

Tap a QSO in the Log tab and the tab becomes its editor. Every stored field is there: your callsign and locator, theirs, mode, band, frequencies, date and times, power, reports, POTA and SOTA references, and the comment.

qFT8 Camera qFT8 QSO editor
  1. The QSO being edited: callsign, mode, band, date and time.
  2. Status: whether the QSO is confirmed. Tap it to Manually confirm or Manually unconfirm it (this only changes your own log).
  3. Uploaded: where the QSO stands on QRZ and LoTW. Tap it to upload the QSO again to one service or to all.
  4. A changed field is highlighted, with its old value in red next to it and an arrow that puts the old value back. Tap any value to change it. Mode and band are picked from the app's lists, the band follows a frequency you type, and a value that cannot be right (a callsign, a locator, a date...) is refused with the reason.
  5. BACK: Leaves the editor. If there are changes it asks whether to discard them.
  6. The number of changes not saved yet.
  7. DELETE: Deletes the QSO from this app's log only, after you type yes.
  8. SAVE: Asks for confirmation, then saves.

What happens on QRZ and LoTW when you save. The confirmation question tells you, for the QSO you are editing:

qFT8 never deletes anything on QRZ or LoTW. Deleting a QSO only removes it from the app. If that QSO is on a service, it may come back at the next sync: delete it on the service first. Deleting is irreversible unless you keep an exported copy of the log.

The logger

The + button of the Log tab opens the logger, a fast form for QSOs you make yourself. On a phone it turns the screen to portrait, with a thin strip of the spectrogram on top (this can be switched off in Settings > APPLICATION > User interface).

qFT8 logger
  1. QSO / SWL (the first field, blue for QSO, red for SWL): where the entry goes. SWL writes the station into the SWL log, never into the QSO log. The SWL page of the log opens it on SWL and the QSO page on QSO; anywhere else it starts on QSO with the Ham features on and on SWL with them off.
  2. Callsign: Type the callsign and press Enter on the keyboard: the QSO is logged with the current time, the box empties, and you can type the next one. The keyboard stays open from one QSO to the next.
  3. LOG: The same as Enter.
  4. CLEAR / UNDO: While a callsign is typed it reads CLEAR and empties the box. Otherwise it reads UNDO and takes the last QSO of this session out of the log and back into the form, to correct it.
  5. DONE: Closes the logger. If a callsign is typed but not logged, it asks whether to log it.
  6. The lookup line: The country of the callsign, your last QSO with it, and whether it is a duplicate. DUPE in orange means you already logged that station on that band and mode today (you can still log it).
  7. The details (swipe sideways for more): the time (Now, or tap it to set a date and time), band, mode, frequency in kHz, the receive frequency when it differs, power, reports sent and received, their POTA / SOTA reference and yours. They start from what the app is tuned to and are kept from one QSO to the next.
  8. This session: How many QSOs you logged since opening the logger. On a phone, tap it to see them as a list.
  9. The session's QSOs are shown in coral with a clock icon: they are already in your log, but they are not uploaded to QRZ or LoTW until you press DONE, so that a typing mistake can still be undone. Tap one of them to undo or edit it.

The QSO button of the SSB, CW, RTTY and SSTV panes opens the same form as a small card, already filled in with the mode, the frequency and the station, for one QSO at a time.

Selecting several QSOs

Long-press a QSO in the Log tab to start a selection (on the computer, Ctrl-click, or Shift-click for a range). Then tap other QSOs to add or remove them.

qFT8 Camera qFT8 Log selection
  1. X: Leaves the selection without doing anything.
  2. How many QSOs are selected.
  3. SELECT RANGE: Tap it, then tap the QSO where the range ends: everything in between is selected.
  4. ALL and NONE.
  5. ACTIONS: What to do with the selected QSOs:
    • Manually confirm / Manually unconfirm.
    • Export (ADIF): a file with just these QSOs.
    • Export with a POTA / SOTA reference: the same, with your park or summit written into every QSO of the file (the log itself is not changed).
    • Add to a POTA / SOTA activation and Remove from their activation (see Activating a park or a summit).
  6. The selected QSOs are ticked and highlighted.

Every action first tells you how many QSOs it will change and asks for confirmation, and a change can be undone right after. Nothing is ever deleted on QRZ or LoTW.

↑ Back to Table of Contents

ADIF Import/Export

qFT8 supports the standard ADIF (Amateur Data Interchange Format) for interoperability with other logging software, cloud services, and for manual backups.

Importing QSOs

The import feature allows you to bring records from other sources (like other logging programs or backups from other devices) into your local qFT8 log.

Exporting QSOs

Tapping EXPORT QSOs generates an ADIF 3.1.6 file. On Android it opens the system Share sheet, allowing you to save the log to your device or send it via email/messaging; on the computer you choose where to save the file.

The names of the exported files

Note: For very large logs (over 100KB), qFT8 will display a warning as the deduplication and sorting process may take a few moments to complete, especially on a phone.

↑ Back to Table of Contents

QSO upload services

qFT8 can send every QSO you log to several online or home-network logbooks: QRZ, LoTW, Wavelog, Cloudlog, eQSL and another qFT8 (qFT8log). and Club Log too (below). Each one you use has a row under QSO syncing in Settings: a check box too (below). Each one you use has a row under QSO syncing in Settings: a check box to switch it on, and a gear button that opens the service's own page.

When does a QSO count as uploaded?

The green tick in the log, the stations list, the map and the web remote all follow one rule. Every service's page has a check box Consider a QSO uploaded if it is uploaded here. It is on for QRZ and LoTW and off for the others.

The ADIF export can pick Not uploaded to one service at a time; the choices of services that are not set up are greyed out. qFT8 never deletes a QSO on any service: deleting a QSO here only warns you that it is still there.

Choosing services and servers

QSO syncing lists every service, one line each: its switch, an icon for its state and its gear, which opens the service's page. There is no icon while the service is not set up (or, for a server, while it is off), a green tick while it sends your QSOs, an amber pause while it is set up but switched off, and a red “!” when it could not connect; only then does a second, red line under the row say what went wrong. The logging programs on your network keep a second line naming the programs they work with; what they cannot promise (UDP, no password) is explained on their own pages.

More settings > SERVERS, right below DATA SOURCES, holds what this device serves to other programs: the remote control web server and the qFT8 bridge (the iPhone has neither), the Wavelog, Cloudlog and qFT8log servers and the receivers for logging programs on your network. A row's check box, for example “Remote Control Web Server on port 13497”, is the same switch as the one on that server's page, and its gear opens the page; BACK from there returns to SERVERS. A server you switch off stops at once and comes back as it was when you switch it on again.

The downloads that feed the map are in More settings > DATA SOURCES, right below MODES; all of them are on by default. With the world map turned off, DATA SOURCES is not shown (nothing is downloaded for the map then).

Every service and server

What qFT8 can send your QSOs and reports to, what it can serve to other programs, and where each one is described:

To share one log between qFT8s, qFT8log is the recommended way: it works the same on every qFT8, it is the safest (a password, every message signed and, by default, encrypted), and the other qFT8 confirms each QSO, so none is lost on the way. The services that travel over UDP cannot promise that, and Settings says so under each of their switches (below).

HRDLog, HamQTH, World Radio League and Club Log

Each has its own page. HRDLog asks for the HRDLog upload code shown on your HRDLog profile (not your password); HamQTH for HamQTH callsign and HamQTH password; World Radio League for the WRL API key you create on its site (Integrations > Developer API) and, if you have several, the WRL logbook; Club Log, for Club Log e-mail and Club Log application password. Then press VALIDATE. qFT8 never deletes a QSO on them; on Club Log, a QSO whose call, date, time, band or mode you changed leaves its old entry behind (remove it on the website).

HAMLOG.online is the online log that RAZA, RDA and other awards use. Its page has one row, Connection. Tap it: qFT8 shows a card with the code in large letters, the time the code stays valid (it counts down) and the address as a QR code, with COPY URL and OPEN. Open the page on this device or scan the code with your phone, sign in, tick your callsign and approve qFT8 (it asks only to read and upload QSOs); the card closes by itself once you have answered. The web remote shows the same code, address and QR code while qFT8 waits. Then tap VALIDATE and tick the box. Each QSO is uploaded as you log it, under the callsign at the top of Settings (or the QSO's own portable call, e.g. /P); an edit changes the QSO there; qFT8 never deletes anything on HAMLOG.online. Each device connects by itself (the connection is not exported with the settings); remove an old one under Connected loggers on the website. A RAZA activation's UPLOAD points to HAMLOG.online too: with this service on, the activation's QSOs are already there, and you send the activation to the RAZA moderator on the website.

Logging programs on your network

qFT8 can send each QSO you log to logging and map programs on your local network. Under QSO syncing find the row of FT8 network log (UDP port 2237) or ADIF over UDP (UDP port 2333) and open its gear. On its page type the address of the computer that runs the other program (127.0.0.1 is this computer) and the port, press VALIDATE, then tick its box. FT8 network log can also send your decodes and your station's status (Also send my decodes and my station's status (for maps and alerts)), which the other program's map and alerts use: every decode of FT8, FT4, FT2, JT65, JT9, JT4, Q65, MSK144, FST4 and the LQ modes, and a status with the radio's real dial frequency, the mode, the station you are calling and whether TX is on. With the box under it that lets the program pick the station to call ticked (off at first), a double-click on one of your decodes in the other program selects that station in qFT8, as a tap on it would, and its stop-TX button turns TX off; nothing it sends can turn TX on, change the band, the mode or the power. These messages carry no receipt, so a QSO sent this way never counts as uploaded. Settings names, under each one, the programs it was tested with.

N1MM Logger+ (Windows, tested with version 1.0.11469) takes QSOs from qFT8 on its UDP port 2237. In its Config > Configure Ports window tick Enable next to UDP port 2237 and restart it; then in qFT8 add FT8 network log, or ADIF over UDP with the port changed to 2237, with the address of that computer. Each QSO appears in its log with the call, frequency, mode, reports, locator and time. It does not listen on port 2333.

Log4OM 2 (Windows, tested with version 2.42.1) works both ways. In its connection settings add a UDP inbound connection with its JT preset (port 2237) for FT8 network log, or with its ADIF preset (port 2234; set the same port in qFT8) for ADIF over UDP. An outbound ADIF connection to port 2333 of qFT8's computer sends the QSOs logged in it to qFT8's ADIF over UDP receiver.

N3FJP AC Log (Windows, tested with version 7.0.12) takes FT8 network log on UDP port 2237: tick the box that listens for FT8 programs in the API window of its Settings menu. It does not take ADIF over UDP.

CQRLOG (Linux, tested with version 2.5.2) takes FT8 network log in its remote mode for FT8 programs (port 2237; in its preferences take the frequency from the other program), and ADIF over UDP in its remote mode for ADIF (port 2333).

GridTracker2 (tested with version 2.261019.5) maps and logs what FT8 network log sends to port 2237 (its decode list, call roster and map fill from your decodes, and it shows your dial frequency); with the box above ticked, a double-click on a station in its call roster selects that station in qFT8; with its ADIF UDP receiving switched on it also takes ADIF over UDP on port 2333. Its logging forwarders send its QSOs to qFT8's receivers.

The other way round, qFT8 can take QSOs from other programs into its log. In More settings > SERVERS tick the row of the receiver for the format the other program sends: FT8 network log (UDP 2237), ADIF over UDP (UDP 2333), the AC Log interface (TCP 1100) or the DXLab interface (TCP 52001). Its page shows the address to enter in the other program and lets you change the port and take QSOs only from some addresses. Nothing received this way can transmit, change the radio or delete a QSO. The receivers are off until you switch them on; on the iPhone they run only while qFT8 is open and never join a multicast group.

UDP logging is not perfect: FT8 network log and ADIF over UDP send each QSO once, with no receipt, so if that packet is lost (for example on a poor Wi-Fi connection) the QSO is lost. None of these formats has a password either: a receiver you switch on lets anyone on the network submit QSOs as you, and a client sends your QSOs to whatever listens at the address you typed. Settings shows this under each of their switches, on the rows and on their pages. A receiver's list of addresses to accept limits who can send to it. For your QSOs, qFT8log is recommended instead: compatible across qFT8s, the safest, and encrypted (see qFT8log).

PSKReporter

PSKReporter collects reception reports from all over the world: which station was heard where, on which band and mode, and how strongly. In Settings, under Reporting, Upload reports to PSKReporter (off by default) sends the stations you decode, in every mode qFT8 decodes, with your callsign, your locator and your Rig and Antenna. Its gear opens the page:

The other way round, Download spots from PSKReporter (Settings, Data sources) fetches who heard your own signal and shows them on the world map. WSPRnet, the beacon network, is described with WSPR.

LQ8 activity on the live map

Announce LQ8 activity to the qFT8 service (Settings, Reporting, off by default): while you transmit in LQ8 through a radio, qFT8 sends your callsign, your 4-character locator, the band and frequency, the mode, the time and the qFT8 version. Other qFT8s and the live map at lq8.org/live show it for 10 minutes; it is kept in memory only. The first time you arm TX in LQ8 with it off, qFT8 asks once whether to switch it on. Also announce it when communicating via speaker/microphone does the same when no radio is cabled. Download LQ8 activity from the qFT8 server (Settings, Data sources) shows the other stations' LQ8 activity on your map.

↑ Back to Table of Contents

QRZ Integration

qFT8 offers deep integration with QRZ.com to keep your logbook automatically synchronized. Note that QRZ integration is a subscription service that requires a QRZ paid subscription (XML Logbook Data or higher). If you prefer a free alternative, consider using LoTW integration, which is provided at no charge by the ARRL.

How it Works

To enable QRZ integration, you need to provide your QRZ API Key in the settings tab. You can find your API Key on the official QRZ Logbook API page. Once entered and VALIDATED, you can enable "Upload QSOs to QRZ" for automatic background management.

Syncing Confirmations

The integration goes beyond just uploading. qFT8 also polls QRZ to see if your QSOs have been confirmed.

Pro Tip: You can see the sync progress in settings under "Oldest QSO synced for confirmation". There's no urgency in keeping this up to date, as qFT8 will take care of it over time.

Log Syncing Strategy

In the synchronization settings, you can choose how qFT8 determines if a QSO is "fully uploaded" via the "Consider a QSO uploaded when uploaded to:" option:

↑ Back to Table of Contents

Logbook of the World (LoTW) Integration

qFT8 provides a robust integration with the ARRL Logbook of the World (LoTW). Integrating with LoTW is highly recommended for confirming your contacts and earning awards like DXCC and WAS.

Setup Requirements

To fully enable LoTW features, including automatic uploads and confirmation checks, you need to provide four specific pieces of information in the settings tab:

Station Location Automation: Details such as ITU Zone, CQ Zone, and Station Name are automatically determined from your callsign. No manual configuration is required for these fields.

Features

Log Syncing Strategy

In the synchronization settings, you can choose how qFT8 determines if a QSO is "fully uploaded" via the "Consider a QSO uploaded when uploaded to:" option:

↑ Back to Table of Contents

Wavelog

Wavelog is a logbook program you run on a web server of your own (a small computer at home or rented web space) and open in a browser. qFT8 sends each QSO to it as soon as it is logged, and reads back which of them your Wavelog has confirmed. qFT8 talks to it through Wavelog's published interface: docs.wavelog.org/developer/api.

Setting it up

  1. In Wavelog, open the account menu > API Keys and create a key with read and write rights.
  2. In qFT8, open Settings, press the gear next to Wavelog and type the Server address (the address you open Wavelog at, for example https://log.example.org) and the API key. An address typed without http:// or https:// is tried with https first; when the server only speaks plain http (another qFT8's server does), qFT8 uses http and the page says the key travels unprotected.
  3. Optional: to have edits sent too, create an API v2 token in Wavelog (account menu > API Keys, the API v2 tab, with the qso:read and qso:write scopes) and type it as the Edit token. VALIDATE checks it without changing anything.
  4. Press VALIDATE. qFT8 checks the key and lists your Wavelog station locations; pick the one your QSOs belong to (with only one, it is picked for you).
  5. Tick Wavelog at the top of Settings. From now on every new QSO goes to it, and the ones logged before are sent too.

What happens

Importing QSOs from Wavelog

IMPORT QSOs FROM WAVELOG, at the bottom of the Wavelog page, copies the QSOs of the chosen station location into the log of qFT8, with their LoTW, paper QSL and eQSL confirmations.

Secure connections

Wavelog and Cloudlog compared

Uploads, duplicates, offline queue
Wavelog yes
Cloudlog yes
VALIDATE checks
Wavelog version, key rights, station locations
Cloudlog key, station locations
Confirmations back to qFT8
Wavelog yes, hourly
Cloudlog no (it offers no way to read them)
A read-only key
Wavelog refused
Cloudlog accepted, but VALIDATE asks for read and write
A QSO made under another callsign than the station location's
Wavelog accepted
Cloudlog refused by Cloudlog
QSOs of other callsigns
Wavelog sent (a setting, on by default)
Cloudlog held back
Edits
Wavelog sent with the Edit token (API v2)
Cloudlog not sent
Importing into qFT8
Wavelog IMPORT QSOs FROM WAVELOG
Cloudlog export an ADIF file in Cloudlog, then IMPORT QSOs FROM ADIF

Activations (POTA / SOTA)

Wavelog takes your own park or summit from the station location a QSO goes to, never from the QSO itself. For an activation, create (or choose) a station location in Wavelog with the park or summit reference in its POTA / SOTA field and in its name, for example Park US-0001. While the activation runs, qFT8 uploads its QSOs to that location by itself. When no location has the reference, qFT8 says so once per activation and uploads to your usual location, without the reference.

↑ Back to Table of Contents

Cloudlog

Cloudlog is the program Wavelog grew from: a logbook on a web server of your own. It is a separate service in qFT8, with its own settings, set up exactly like Wavelog (in Cloudlog: account menu > API > create a key with read and write rights). Its published interface: github.com/magicbug/Cloudlog/wiki/API.

Differences from Wavelog

Activations (POTA / SOTA)

Cloudlog takes your own park or summit from the station location a QSO goes to, never from the QSO itself. For an activation, create (or choose) a station location in Cloudlog with the park or summit reference in its POTA / SOTA field and in its name, for example Park US-0001. While the activation runs, qFT8 uploads its QSOs to that location by itself. When no location has the reference, qFT8 says so once per activation and uploads to your usual location, without the reference.

↑ Back to Table of Contents

eQSL

eQSL (eqsl.cc) exchanges electronic QSL cards: every QSO sent there becomes a card in the other station's eQSL inbox. qFT8 only adds cards; it never deletes anything on eQSL.

Setting it up

  1. Tap the gear of the Sync QSOs with eQSL row at the top of Settings.
  2. Enter your eQSL user name (usually your callsign) and eQSL password. If you have several eQSL accounts (locations) under one callsign, enter the location's QTH nickname as it is written on eqsl.cc; otherwise leave it empty and eQSL picks the account by the QSO's date.
  3. Press VALIDATE. It only reads your eQSL inbox to check the login: no card is sent.
  4. Tick Sync QSOs with eQSL. The QSOs not sent yet go at once, one a second, and every new QSO goes when it is logged.

What to know

↑ Back to Table of Contents

qFT8 as a Wavelog server

In Settings > More settings > SERVERS > Wavelog server, qFT8 answers on your home network as if it were a Wavelog: any program that can send QSOs to Wavelog (another qFT8 among them) can send them to this qFT8 instead.

Setting it up

  1. Turn on Run the Wavelog server, keep the Port (13500) or choose another, and type an API key of at least 8 characters (make it long and random: it is the only thing keeping others out).
  2. In the other program set up Wavelog with the address the page shows, written in full: http://, this device's address, a colon and the port, for example http://192.168.1.20:13500/ (most logging programs need the http:// and the port typed out; another qFT8 finds them by itself), the same key, and station 1 (in another qFT8: VALIDATE picks it).

The port can be changed at any time: the server moves to the new port at once (and stops at once when switched off).

Looking at the log in a browser

Open the same address (http://192.168.1.20:13500/) in a browser on your home network: after you type the server's key, it shows your QSO log, newest first, read only; older QSOs load as you scroll, and new or changed ones appear by themselves. The key is never sent: the browser answers a one-time challenge with a value made from it, and an address that answers wrongly is locked out for a while. The Cloudlog server and the qFT8log server show the same page on their own ports, with their own key or password.

What it does

Chains

Servers and services combine into chains: several stations (phones, computers) send their QSOs to one qFT8 that collects them and is the only one uploading to QRZ and LoTW; that one can also send everything on to a Wavelog or another qFT8 kept as a backup. Confirmations travel back down: the collecting qFT8 learns them from QRZ / LoTW / its Wavelog, and the qFT8s that send to its Wavelog server read them back every hour. Duplicates are never forwarded, so a loop in a chain stops by itself.

↑ Back to Table of Contents

qFT8 as a Cloudlog server

The same as the Wavelog server, for programs that send QSOs to Cloudlog, on its own port (13501) with its own key. It answers as Cloudlog does: no api/version and no api/get_contacts_adif (so no confirmations go back down through it), and it also accepts a form-encoded upload. Both servers feed the same log: a QSO received by one is a duplicate for the other.

↑ Back to Table of Contents

Summits On The Air (SOTA)

qFT8 provides comprehensive, built-in tools for both SOTA (Summits On The Air) Chasers (Hunters) and Activators, complete with automated spot fetching, real-time reference tracking, achievement highlights, and dedicated ADIF export filters.

Live Summit Spot Auto-Fetching

When internet access is available, qFT8 automatically connects to the official SOTA API in the background (refreshing every 90 seconds) to fetch active summit activations worldwide.

Operating as a SOTA Chaser / Hunter

To hunt stations activating summits:

  1. In the Stations tab, set the target priority dropdown to SOTA hunter (or POTA + SOTA hunter).
  2. Visual Badges & Reference Column: Active SOTA stations (spotted online or transmitting CQ SOTA) are marked with a SOTA badge in Row 2. In addition, the DXCC column header switches to SOTA Reference, displaying the summit code directly.
  3. Worked vs. Needed Summit Highlights:
    • Unworked Summit: Marked with a vibrant purple SOTA badge and purple reference text, indicating a new summit to chase.
    • Already Worked Summit: Displayed in a subtle grey badge, allowing you to instantly distinguish fresh summits from those already in your log.
  4. AUTO Chasing: In AUTO mode, qFT8 automatically prioritizes calling unworked SOTA activators over regular CQers, ordering them by strongest signal strength (SNR).

Managing & Editing SOTA References in the Log

qFT8 offers dedicated tools to inspect and edit your SOTA chase history:

Operating as a SOTA Activator

To run a SOTA activation from a summit:

  1. Synchronize time: Ensure your device clock is accurate before heading into the field.
  2. Start the activation: In the Settings tab, press SOTA ACTIVATION and enter your summit, so that every QSO is logged with it and counted (see Activating a park or a summit).
  3. Set your CQ Modifier: In the Settings tab, set CQ modifier to SOTA. Every CQ call will transmit CQ SOTA [Callsign].
  4. Configure AUTO Mode: In the Stations tab, set the target priority to Call CQ and engage AUTO mode.
  5. Start Activating: Enable TX. qFT8 will automatically call CQ and reply to incoming chasers in sequence.

Manual Overrides: If several chasers call you simultaneously and you wish to pick a specific station, tap CALL on their entry. Once that contact completes, qFT8 automatically returns to calling CQ.

Exporting your SOTA Logs (Chasers & Activators)

qFT8 allows generating tailored ADIF exports for both hunter submissions and activator logs:

  1. Go to Settings and tap ADIF File Export.
  2. For Chasers / Hunters:
    • Set Hunter criteria to Only SOTA contacts (summits) to export only QSOs where a summit reference was contacted (with <SOTA_REF> populated).
  3. For Activators (the quickest way is the EXPORT button of your activation; the steps below do the same by hand):
    • Select Selected time range to match your activation start and end times.
    • In Event, choose SOTA and enter your activated summit code (e.g., HB/BE-001). qFT8 injects your reference into <MY_SOTA_REF> on every record.
  4. Summit-to-Summit (S2S): If you worked another activator while activating a summit, qFT8 includes both your activator summit (<MY_SOTA_REF>) and the contact's summit (<SOTA_REF>) in the exported file.
  5. Press EXPORT QSOs to share or save the standardized ADIF file.
↑ Back to Table of Contents

Parks On The Air (POTA)

qFT8 provides full, native integration with the POTA (Parks On The Air) program for both Hunters and Activators, featuring automatic spot retrieval, worked park tracking, reference editing, and flexible export options.

Live Park Spot Auto-Fetching

When connected to the internet, qFT8 automatically queries the official POTA API in the background (every 90 seconds) to retrieve all active park activations across the globe.

Operating as a POTA Hunter

To hunt stations activating parks:

  1. In the Stations tab, set the target priority dropdown to POTA hunter (or POTA + SOTA hunter).
  2. Visual Badges & Reference Column: Active POTA stations are tagged with a POTA badge in Row 2, and the DXCC header switches to POTA Reference to show the park code.
  3. Worked vs. Needed Park Highlights:
    • Unworked Park: Marked with a bright purple POTA badge and purple reference text, indicating a park you have not yet worked.
    • Already Worked Park: Displayed in a subtle grey badge, making it easy to prioritize unworked parks during busy band conditions.
  4. AUTO Chasing: In AUTO mode, qFT8 prioritizes unworked POTA activators over regular stations, ordering candidate targets by signal strength (SNR).

Managing & Editing POTA References in the Log

Inspect and maintain your park hunter logbook directly within the app:

Operating as a POTA Activator

To activate a park:

  1. Synchronize time: Ensure device clock accuracy before beginning your activation.
  2. Start the activation: In the Settings tab, press POTA ACTIVATION and enter your park, so that every QSO is logged with it and counted (see Activating a park or a summit).
  3. Set your CQ Modifier: In the Settings tab, set CQ modifier to POTA to transmit CQ POTA [Callsign].
  4. Configure AUTO Mode: In the Stations tab, set target priority to Call CQ and engage AUTO mode.
  5. Start Activating: Enable TX. qFT8 will continuously call CQ and work incoming hunters automatically.

Manual Overrides: Tapping CALL on any queued station prioritizes that QSO before returning to AUTO CQ mode.

Exporting your POTA Logs (Hunters & Activators)

Generate standardized ADIF files ready for upload to pota.app:

  1. Go to Settings and tap ADIF File Export.
  2. For Hunters:
    • Set Hunter criteria to Only POTA contacts (parks) to export only QSOs where a park was hunted (with <POTA_REF> populated).
  3. For Activators (the quickest way is the EXPORT button of your activation; the steps below do the same by hand):
    • Select Selected time range to match your activation window.
    • In Event, select POTA and enter your park reference (e.g., K-1234). qFT8 automatically populates <MY_SIG>POTA, <MY_SIG_INFO>, and <MY_POTA_REF> across all exported records.
  4. Park-to-Park (P2P) & Park-to-Summit (P2S): When hunting other parks or summits during your activation, both your activator park (<MY_POTA_REF>) and the remote contact's reference (<POTA_REF> / <SOTA_REF>) are exported simultaneously.
  5. Press EXPORT QSOs to share or save your log file.
↑ Back to Table of Contents

Multi-tone: several signals at once

Settings has a section Special transmission, directly above Events. Its ? opens a card with all the explanations and a link to this page. In it, in this order: the button Multi-tone (experimental; blue while on, a tap switches it on or off); under it Fox mode (off by default, usable only while Multi-tone is ticked: multi-tone the way a DXpedition runs it), the red power line, Add a CQ message with Always at its right, and Maximum tones: 2 tones to 5 tones (greyed while Multi-tone is off, and in Fox mode, which sends as many signals as fit); then the button Hound mode (call a DXpedition). Multi-tone and Hound mode cannot be on together: switching one on switches the other off, with a short message. While Multi-tone is on, each transmission in FT8, FT4, FT2 and the LQ modes can carry that many ordinary signals side by side, each with its own message to its own station. The price is power: to keep the audio from clipping, the signals share it, so each one reaches the other station weaker (2 tones: 6 dB weaker each, 3: 9.5 dB, 4: 12 dB, 5: 14 dB). A cycle that needs fewer messages sends fewer signals, each then stronger. A blue Multi-tone marker on the spectrogram reminds you while it is on; the transmit frequency is drawn as one bar per signal, and every station being worked has its receive bar.

Fox and Hound (DXpeditions)

Under Multi-tone in Settings are two more boxes, both off by default: Hound mode (call a DXpedition) and Fox mode (DXpeditions only). They work in FT8, FT4, FT2 and the LQ modes. Only one of the two can be on, and Fox mode not together with multi-tone: ticking one unticks the other, and a short message says so. The ? beside the section's title opens this page.

Fox and Hound are not multi-tone. Multi-tone only sends several ordinary signals at once. Fox and Hound are the DXpedition protocol: the Fox tells each Hound where to move and answers several of them with special combined messages, and qFT8 follows those instructions by itself only while one of the two modes is on.

Hound mode: working a DXpedition

Fox mode: running a pileup

Activating a park or a summit

When you operate from a park (POTA) or a summit (SOTA), start an activation in qFT8. From then on every QSO you log, in any mode, automatically carries your park or summit, qFT8 counts them for you, and at the end it writes the files the programmes ask for with one tap.

The Events section of Settings

Settings has a section Events for operating events. Today it holds:

Hunting parks and summits from home is described in the POTA and SOTA sections.

Starting

  1. In the Settings tab, press POTA ACTIVATION or SOTA ACTIVATION (in the Events section).
  2. Type your reference, for example US-1234 for a park or W1/HA-001 for a summit. If you are in several parks at once (a "two-fer"), separate them with commas. qFT8 checks the format as you type and offers the references you used recently.
  3. Press START. The button turns blue and shows the reference and the number of QSOs.

A park and a summit activation can be open at the same time; every QSO then gets both references. To call CQ POTA or CQ SOTA in the digital modes, set the CQ modifier as described in the POTA and SOTA sections.

qFT8 can also offer to start for you: if the spots it downloads for the world map show your own callsign as an activator, it asks Start a POTA activation there? And if you type your park or summit into the empty My POTA / My SOTA box of the logger, it asks whether to start an activation with it.

Announcing it, so hunters find you

qFT8 announces POTA and SOTA activations. SOTA uses your own SOTAwatch user name and password (the gear beside SOTA ACTIVATION; VALIDATE there says Signed in as and your callsign). If SOTA stops accepting sign-ins from apps, qFT8 says so once and offers SPOT ON SOTAWATCH instead, which opens its page so you announce yourself. While TX is off a SOTA activation is not announced again by itself. When you start a POTA activation yourself (not from a spot that already announced you), qFT8 asks Announce it on POTA? and says what hunters would see, for example FT8 on 20m (14074 kHz). NOT NOW announces nothing. ANNOUNCE opens a short dialog:

After that, qFT8 announces the activation again every 30 minutes (announcements disappear from the list after about an hour; the gear beside POTA ACTIVATION sets Re-spot every, from 20 to 60 minutes, and Retry a failed spot after, 5 or 10 minutes), as long as the activation is open and qFT8 is working: on screen, or minimised with qFT8 kept running in the background and the radio connected. It stops when you finish the activation, and it never announces by itself when qFT8 was closed: at the next start, once you have chosen to continue the activation, it asks Announce again?

If an announcement does not get through (no internet, or the site refuses it), qFT8 says what went wrong and offers RETRY, or SPOT BY HAND, which opens the programme's spot page in your browser so you can announce yourself. Without a connection it also tries again by itself (every 5 minutes unless you chose 10).

To announce with other bands or modes, or to see when it was last announced, press ANNOUNCE on the activation's card (tap the blue marker) or in the activation's QSO view. The dialog then also offers STOP RE-ANNOUNCING. When you change mode during an announced activation, qFT8 asks whether to announce the new mode too.

The Comment box under the modes is what every announcement says. It starts with qFT8's own text (the real mode, for a mode announced as DATA) and you can change it, for example to add QRP 5 W. Once the activation has been announced, the modes also offer QRT: tick it when you stop, and ANNOUNCE sends one last announcement saying you are QRT, with the comment (your thanks, for example). The bands are greyed out, re-announcing stops, and it is sent only once. Finishing an announced activation also asks whether to tell the programme you are QRT.

While it is open: the blue marker

A blue POTA or SOTA marker stays at the bottom right of the waterfall for as long as the activation is open, with the number of QSOs of the activation next to the word: POTA 10. Every QSO you log counts once: working the same station again on the same band and mode is a duplicate and is not counted. The number goes down again when a QSO is removed from the activation, deleted, or undone in the logger. For POTA it starts again from zero at 00:00 UTC. With two parks at once there is still one number, because each QSO counts for both parks. Where there is little room the marker shows the number alone beside its icon, and where even that does not fit it is drawn smaller, together with the red warning that shares its line. Tap it for the state of the activation:

qFT8 Camera qFT8 POTA activation card

The activation's QSOs

qFT8 Camera qFT8 POTA activation view
  1. Back to the whole QSO log.
  2. The activation: programme and reference, when it started (UTC), and its QSOs.
  3. +: Opens the logger to log a QSO by hand straight into this activation.
  4. ADD QSOs: Adds QSOs that are already in your log, by time range. Use it when you forgot to start the activation: choose from and to, and qFT8 says how many QSOs it will add before doing it.
  5. EXPORT: Writes the files to upload (below).
  6. The other station's park or summit, when it was activating too.
  7. The marker of the open activation.

To take QSOs out of an activation, long-press one to select it, tap any others, press ACTIONS and choose REMOVE FROM THIS ACTIVATION. The QSOs stay in your log; only your reference is removed from them. You can also move a single QSO from the QSO editor, with its POTA activation / SOTA activation row.

Finishing, and resuming

FINISH ACTIVATION shows a summary: references, start and end time, and QSOs per mode. QSOs logged after finishing are not part of it.

Exporting

EXPORT (in the summary and in the activation's list) writes ADIF files named the way each programme expects, ready to upload on its website:

You can save the files or share them. The magnifying-glass button next to POTA ACTIVATION / SOTA ACTIVATION in Settings lists your past activations, newest first, and marks each as ACTIVE, CAN RESUME, EXPORTED or not exported; tap one to open it and export it again. qFT8 does not upload to the programmes' websites itself.

Several parks in a row

On a day with several parks, one after the other, each park is its own activation and its own file:

  1. At the first park, press POTA ACTIVATION in Settings, type its reference and press START.
  2. Operate. Every QSO gets the park, and the blue marker counts them.
  3. Before you leave, tap the marker and press FINISH ACTIVATION, then EXPORT in the summary, and save or share the file (K1ABC@US-1234-20261006.adi).
  4. At the next park, start again with the new reference.

There is nothing to retype or to sort out at home. If you have no time to export in the field, the list of past activations (the magnifying glass) exports each one later.

"Which park goes in the file?"

A park's file can only name one park. When you export QSOs that were made from several parks at once without going through an activation (the whole log from Settings, or Export (ADIF) on a selection), qFT8 asks Which park goes in the file? Choose the park this file is for; export again for the other one. The log is not changed. Exporting from the activation itself never asks: it writes one file per park.

To get a file for every park without an activation, type the parks yourself, separated by commas (US-1234, US-5678), in the POTA reference box of EXPORT LOGS or in Export with a POTA reference on a selection: qFT8 writes one file per park, with the same QSOs in each. A summit is always one reference.

When the station you work is in two parks at once, qFT8 keeps both: it reads the second park from the spot's comment when the spotter wrote it there. The log shows the first park and how many more (US-1234 +1). If a park is wrong or missing, correct the POTA field of the QSO in the QSO editor; it takes several parks separated by commas. A park that is named twice for the same station (in the spot and again in its comment, or twice in a typed list) counts once, in the log and in every exported file.

The QSO counter

For any other event, START COUNTER in the Events section asks the number to start from (0 unless you type another) and counts every QSO you log from then on, also across restarts, until you finish it. While it counts, the button turns blue and reads COUNTER 12, and a blue label with the count ("12 QSOs", or "1 QSO") shows at the bottom right of the waterfall. A tap on either one finishes counting; nothing is kept afterwards. The count carries on if the app is closed and opened again.

↑ Back to Table of Contents

Events supported

POTA and SOTA are on by default. In Settings > Events, the COUNTER button (for example COUNTER 12) shows how many QSOs count for the running activation or contest.

To switch on the others, press ADD MORE EVENTS in Settings > Events and tick the programme or contest you want. They are marked experimental.

Award programmes

Contests (experimental)

Press START CONTEST and type your exchange. In the contests whose rules forbid automated QSOs (all of these except Winter Field Day) AUTO is switched off while the contest runs: its button turns red, and tapping it says “AUTO operation is not allowed in this contest”. You start every QSO yourself.

SWL mode (shortwave listeners)

If you listen without transmitting, press SWL MODE (LISTEN ONLY) at the end of Settings > Events and type your SWL identifier (for example R4-123-456) or your callsign. While it is on, qFT8 never transmits: the TX button reads NO TX / SWL and does nothing. Every complete QSO heard between two other stations (both calls, time, band, frequency, mode, both reports and the grids when they were decoded) goes to the heard log, not to your own QSO log; a QSO counts as complete once its confirmation (RR73, RRR, or a 73 after the other station's roger report) was heard, in FT8, FT4 and LQ8 alike. The magnifier beside the button opens the heard log: EXPORT ADIF (one record per heard station, two per QSO: SWL=Y, your identifier as operator, the station heard in CALL with your report on it, the station it was working in the card message "Heard working ..." and in the comment, plus any programme reference heard for it, for example RAZA), EXPORT CSV and CLEAR THE HEARD LOG. The web remote shows the heard QSOs (read only).

↑ Back to Table of Contents

JS8 (keyboard chat)

JS8 is for conversations typed on the keyboard: free text of any length, messages to one station or to a group, and short questions that the other station's program answers by itself. A message longer than one transmission is cut into frames and sent one frame per time slot; the receiving station puts the frames back together into one message.

Pick JS8 with the mode selector of the bottom bar. The Stations tab becomes the JS8 chat pane, and the speed button (item #11) takes the place of the sequence button in the bottom bar. The spectrogram, the band selector, the main TX ON / TX OFF button and the red bar of your transmit frequency work as in FT8.

qFT8 Camera qFT8 JS8 Chat

The JS8 chat pane

From left to right and from top to bottom:

  1. AUTO: Automatic answers, on (green) or off (black); on by default. With AUTO on and the main button at TX ON, qFT8 answers the questions other stations send you (see Automatic answers). AUTO never turns your transmitter on.
  2. JS8 Chat: The title of the pane.
  3. Request: Opens the list of standard questions to send to the chat that is open (see Questions to other stations). It is grey in a chat with a group other than @ALLCALL.
  4. QSO: Logs a QSO with the station whose chat is open (see Logging a JS8 QSO). It is grey in [GLOBAL] and in group chats.
  5. CQ: Sends a general call to @ALLCALL: CQ followed by the first four characters of your locator, for example CQ JN47.
  6. +: Opens Add Chat, where you type a callsign or a group (@NAME) to start a chat with it, even before anything has been heard from it.
  7. The messages: The messages of the chat that is open, the newest at the bottom. Above each one: the band, the audio frequency, the signal strength (for received messages), the UTC date and time. Your own messages are green; messages addressed to you are blue; the others are grey-blue. A message waiting for its slot is dark yellow, and the one on the air has a gold border and starts with TX (sending 2/5)...: while its frames go out, the part already sent turning green.
  8. The chat list: The chats you can open (see The chat list). The open chat is highlighted in blue; a chat with messages you have not read yet is amber.
  9. The message box: Where you type. Letters are turned to capitals; up to 100 characters.
  10. The send arrow: Sends what you typed to the chat that is open. With the box empty it does nothing.
  11. The speed button in the bottom bar: Slow, Normal, Fast, Turbo or Ultra (see Speeds).

While the main button says TX OFF, a red line over the message box says Enable TX to start transmission when a message is waiting, or Enable TX to allow AUTO operation when AUTO is on. Messages you send with TX OFF wait in the chat; nothing goes on the air until you press the main button.

Speeds

Every speed has its own time slot. Slower speeds use less bandwidth and decode weaker signals; faster ones send more text per minute. qFT8 receives only the speed chosen with the speed button, so choose the same speed as the stations you want to talk to (Normal is the usual one).

Slow
Slot 30 s
Bandwidth about 25 Hz
Normal
Slot 15 s
Bandwidth about 50 Hz
Fast
Slot 10 s
Bandwidth about 80 Hz
Turbo
Slot 6 s
Bandwidth about 160 Hz
Ultra
Slot 4 s
Bandwidth about 250 Hz

The speed names stay in English in every language. Each frame carries 75 bits; how much text fits in one frame depends on the words, because common words are sent in a shorter code.

The chat list

From the top:

A long press on a chat (on the computer: a right click) opens its options: Join group or Leave group (groups only; never for @ALLCALL), Export (local save) and Export (share) (its messages as a text file), Clear (deletes its messages), Clear and close (also removes it from the list; a group is left), Clear all chats and Clear and close all chats. [GLOBAL] and @ALLCALL cannot be closed.

Not private: every JS8 message goes on the air in the clear. A callsign chat only sorts the messages for you; anyone on the frequency can read them.

Sending a message

  1. Open the chat: a station, a group, @ALLCALL or [GLOBAL].
  2. Choose your transmit frequency on the spectrogram, in a free spot, as in FT8.
  3. Type the text and press the send arrow. The message appears in the chat, waiting for the next slot.
  4. Press the main button so that it reads TX ON. The frames go out one per slot; the message shows how many have been sent. Several messages go out one after the other.

A message waiting or on the air has an x beside it: it opens Abort Transmission? with Abort message and, when more than one is waiting, Abort all messages. TX OFF also stops the message on the air.

A long message keeps the radio keyed for many slots in a row. When it would key the radio for longer than the radio's Continuous transmission limit allows, qFT8 asks once, before the first frame: Send with pauses (some slots are left empty so the radio can rest; the other station still receives one message), Shorten (back to the text, with the part that would have to wait selected) or Cancel. Always send long JS8 messages with pauses in that question (and in Settings) stops the question.

JS8 needs a standard callsign: in JS8, Settings warns This callsign is not standard and doesn't fit in JS8. when yours cannot be sent.

Tapping a message

A tap on a message that has been received or sent (on the computer: a double click) opens its details: the UTC date and time, who sent it and to whom, the band, the frequency, the speed, the signal strength, the locator and the distance when known, and the text. Below them, the actions:

A question addressed to you that has not been answered yet also shows a small arrow beside it: a tap sends the answer at once. On the computer, a single click on a message puts the sender's callsign into the message box.

Colours inside the text: your own callsign is red, group names are orange, questions and commands (SNR?, GRID? ...) are yellow, relay paths (>CALL>) are teal, and the mark ◇ that ends a message is cyan. A ~ in orange marks a frame that was not received, so you know a part of the text is missing.

Questions to other stations

Request sends one of the standard JS8 questions to the chat that is open (from [GLOBAL]: to @ALLCALL):

You can also type other JS8 commands yourself, for example MSG TO:, or a spot for the APRS network: @APRSIS GRID JN47AB. A relay path such as K1ABC>W9XYZ HELLO is sent as you type it; qFT8 does not relay messages for other stations, and it does not keep messages for them.

Automatic answers (AUTO)

With AUTO on and the main button at TX ON, when a question to your callsign has been received completely, qFT8 puts the answer in the queue and sends it in the next slot:

The same question is not answered twice while the answer is still waiting, and your own messages are never answered. qFT8 does not send heartbeats or CQ by itself: it sends them only when you press CQ or choose them in Request. AUTO in JS8 is separate from AUTO in FT8.

Logging a JS8 QSO

JS8 has no fixed sequence of messages, so a QSO is logged when you decide it is complete. Open the station's chat and press QSO: Log JS8 QSO asks Log JS8 QSO with K1ABC? (and says when the last JS8 QSO with that station was logged, if there is one). Log QSO writes it to the log with mode JS8, the band and frequency, the time, the station's locator when it was heard, and the reports exchanged in the chat as signed two-digit numbers (+05, -12). From the log it is uploaded like any other QSO, and the station's chat in the list shows a tick (logged), a tick with a clock (waiting to be uploaded) or a star (confirmed).

Settings > JS8

The JS8 Settings section of Settings > DIGITAL MODES has:

On the computer, the iPhone and the web remote

↑ Back to Table of Contents

WSPR and FST4W (beacons)

WSPR is not for conversations: every station sends a short beacon with its callsign, its locator and its power, and listens to the others. What you get is a list of who you hear, and, through WSPRnet and PSKReporter, a map of who hears you. A WSPR transmission lasts 110.6 seconds and starts one second into an even UTC minute, so the band works in 2-minute slots. FST4W is a beacon mode of the same kind with longer slots (see FST4W in this pane).

Pick WSPR with the mode selector of the bottom bar. The Stations tab becomes the WSPR pane (in the web remote the tab is called WSPR Mode), the spectrogram scrolls slowly to match the 2-minute slots, and the part of the spectrogram outside 1400–1600 Hz is shaded: every WSPR signal of the band sits in those 200 Hz.

The WSPR pane

qFT8 Camera qFT8 WSPR pane

From left to right and from top to bottom:

  1. BEACON: Switches your own beacon on (green) and off (black). With the beacon on, qFT8 transmits in some of the slots, as many as the transmit percentage (item #2) says. The beacon never turns your transmitter on by itself: while the main button of the bottom bar says TX OFF, nothing is sent and a red line reads Enable TX to start transmission.
  2. TX: 20%: The share of slots in which the beacon transmits. A tap opens WSPR TX Percentage: 0% (RX only), 10%, 20%, 25%, 33%, 50% or 100% (Continuous). The slots are picked at random, slot by slot, so that two stations with the same setting do not keep transmitting at the same time; 20% means one slot in five on average, about one transmission every 10 minutes. The value is red when the radio's Continuous transmission limit allows fewer slots than that: the beacon then waits and transmits in the next slot it may use.
  3. The power (for example 5 W): The power your beacon message announces to the stations that hear you. A tap opens Report power:, a list from 1 mW (0 dBm) to 1000 W (60 dBm) in the steps WSPR can carry. Set it to the power your radio really puts out. It is only a number in your message: qFT8 never changes the power of the radio, that stays on the radio's own controls.
  4. EXPORT: Saves the spots of the list as an ADIF file. On the phone the dialog Share WSPR ADIF Log offers Local save and Share; the computer asks where to save the file; the iPhone opens its share sheet; the web remote downloads the file to the device you are using.
  5. CLEAR: Empties the list.
  6. The list: One row for every WSPR signal decoded, the newest at the top: the callsign, the country (DXCC), the locator (Grid), the SNR in dB (measured in 2500 Hz, as every WSPR receiver reports it), the power the other station announces, and the date and UTC time of its slot (yyMMdd HH:mm). The list is kept when the app is closed; how many rows and for how long is set in Settings > WSPR.
  7. The status line: What happens next: RX cycle ends in 01:12. TX: Off while the beacon has nothing planned, Next transmission in 05:40 while it waits for its slot, Transmitting — ends in 01:30 while it is on the air, and Transmission off when a transmission is planned but the main button says TX OFF. A red line here means your beacon cannot be sent: TX: set your callsign and locator (both are needed, in Settings), or Callsign is too long to transmit WSPR / TX: this callsign cannot be sent in WSPR.
  8. TX NEXT: Transmits in the next slot, whatever the percentage says; afterwards the beacon goes on as before. It is green while the next slot is going to be used (also when the beacon picked it), and a second tap gives that slot up. It is grey while the main button says TX OFF.

The message bar of the bottom bar shows the message your beacon sends: your callsign, the first four characters of your locator and the power of item #3, for example HB9IPH JN47 37.

Receiving and beaconing

  1. Choose the band with the band selector: the radio goes to the band's WSPR frequency (see below). Receiving needs nothing else: every 2 minutes, a few seconds after the slot ends, the signals decoded in it are added to the list.
  2. To beacon, check that your callsign and locator are set and that The power (item #3) is what your radio sends. Choose a transmit percentage (20% is usual), leave BEACON green and press the main button of the bottom bar so that it reads TX ON. The status line counts down to your next transmission.
  3. To send one beacon now, or with the beacon off, press TX NEXT.
  4. To stop, press the main button again (TX OFF) or switch BEACON off. A transmission on the air ends when TX OFF is pressed.

A WSPR transmission lasts almost two minutes: a radio whose Continuous transmission limit is shorter than that cannot send it, and qFT8 tells you so. Nothing is logged in WSPR: the spots stay in the list of this pane and are not QSOs.

Bands and frequencies

Every band of the band selector has a WSPR dial frequency, from 2200 m to 13 cm: 2200 m 136.000 kHz, 630 m 474.200 kHz, 160 m 1.836600 MHz, 80 m 3.568600, 60 m 5.287200, 40 m 7.038600, 30 m 10.138700, 20 m 14.095600, 17 m 18.104600, 15 m 21.094600, 12 m 24.924600, 10 m 28.124600, 6 m 50.293000, 4 m 70.091000, 2 m 144.489000, 70 cm 432.300000, 23 cm 1296.500000 and 13 cm 2400.048000 MHz (upper sideband).

Your beacon is sent at the audio frequency chosen on the spectrogram, inside 1400–1600 Hz. With Enable random frequency jitter (±60 Hz) on (the default) each transmission moves to a random place up to 60 Hz away, so that you do not sit on top of the same station every time.

Spots to WSPRnet and PSKReporter

Settings > WSPR

The WSPR section of Settings > DIGITAL MODES has:

FST4W in this pane

FST4W (the FST4W (experimental) row of the mode selector) uses the same pane: the same list, BEACON, TX NEXT, power, EXPORT and CLEAR, and the same uploads to WSPRnet and PSKReporter. What changes:

Its settings are described in Settings > FST4W.

↑ Back to Table of Contents

SSB (voice)

In SSB mode qFT8 is the microphone and the loudspeaker of your transceiver: the signal the radio receives is turned into voice on your speaker or headphones, and your voice goes from your microphone to the radio. The radio stays connected exactly as it is for the digital modes (the same USB cable, the same sound card), so nothing needs to be re-plugged to change from FT8 to voice and back.

Specifications: ITU emission class J3E (ITU Radio Regulations); voice has no digital protocol.

qFT8 makes the voice signal itself and sends it through the radio's sound card. It puts the radio in its data mode of the same sideband (for example USB-D or LSB-D, DATA-U or DATA-L, DIGU or DIGL; on a QMX its own USB or LSB mode), so the radio's display shows the same frequency as qFT8. The sideband follows the band: LSB below 10 MHz, USB from 10 MHz up and on 60 m.

Pick SSB with the mode selector of the bottom bar. The message area, the sequence buttons and the cycle bar disappear (voice has no time slots), a USB / LSB button appears next to the mode selector, and the Stations tab becomes the SSB pane:

qFT8 Camera qFT8 SSB pane

These are the components of the SSB screen in detail:

  1. RX / TX / RX/TX: Chooses what the tuning wheel (item #12) moves. With RX/TX you receive and transmit on the same frequency. With RX or TX only that one moves, so you can listen on one frequency and transmit on another (split). Without a CAT connection these buttons are grey and stay on RX/TX; a tap says Tuning needs a CAT connection to the radio.
  2. AUTO RIT: Keeps a station that is slightly off frequency centred, so its voice sounds natural without touching the wheel.
  3. The gear: Opens Settings > SSB (see below). BACK returns to this pane.
  4. QSO: Opens the logger with the mode, the sideband and the frequency already filled in, to log the contact you just made (see The logger). One QSO per press. The reports (59 / 59) are filled in too, and after a split contact both the frequency you transmitted on and the one you listened on.
  5. Voice memories: Your recorded messages (a CQ call, your callsign...). Until you record one, this area shows the link Configure voice memories in Settings.
  6. IN: The level of your microphone and its gain slider. The line marked VOX is the level your voice must pass to key the radio when VOX is on (item #10): drag it.
  7. OUT: The level of the received audio and the volume slider of your speaker. The volume keys of the phone do the same. At the very bottom of the slider the sound is off (MUTE).
  8. FILTER and NR: The receive filter (off, 2.7, 2.4 or 1.8 kHz) and the noise reduction (off, 1, 2 or 3). Each tap steps to the next value. These labels are the same in every language.
  9. PTT: Push to talk. It reads "hold to talk" or "tap to talk" depending on the PTT mode setting, and "ON AIR" while you are transmitting. With a keyboard (the computer, the web remote, a phone or tablet) the space bar does the same while the bottom bar, the spectrogram, the world map or this pane was the last place you clicked or tapped; in a text box it still types a space. While you transmit it also shows the seconds left when a limit applies (see below). After VOX reached the limit it reads "VOX paused", and it reads "No SSB" when the radio cannot transmit voice from the app.
  10. VOX: When on, the radio is keyed by your voice instead of the PTT button.
  11. USB / LSB: The sideband. It is chosen for you when you change band (LSB below 10 MHz, USB above); a tap changes it and the frequency you read stays the same. On 60 m it is USB too, and a band change made with the radio's own knob also picks the band's sideband.
  12. The tuning wheel: In SSB the frequency scale of the spectrogram is a wheel. Swipe along it to tune the radio; a faster swipe takes bigger steps. A tap does nothing, so the frequency never jumps by accident. On the computer the mouse wheel tunes too (hold Shift for 1 Hz steps). Tuning needs a CAT connection to the radio.
  13. Frequency and band: The frequency you would say on the air (the carrier), and the band. The orange line and the RX/TX label under it mark the part of the spectrogram you are listening to and transmitting on. A tap on the frequency opens Radio frequency (kHz) to type one; a frequency in another band changes the band. This also needs CAT.
  14. The STEP chip, under the frequency (SSB, CW, RTTY): a tap on its middle picks the step (AUTO, 10, 50, 100, 500 Hz, 1 or 5 kHz; remembered for each of SSB, CW and RTTY); its arrows tune one step down or up, to the next round frequency. With a fixed step every ridge of the SSB tuning strip moves by that step (AUTO: faster swipes take bigger steps). On the computer the LEFT and RIGHT keys step too in SSB. Needs CAT.

With a QMX or QMX+ a grey line above the PTT button reminds you that the radio's SSB audio source (its menu SSB > Input) must be the USB sound card (see What SSB needs).

Talking

  1. Arm transmission with the TX button of the bottom bar. As in every other mode, nothing transmits while it says TX OFF: the red line Press TX ON to transmit reminds you.
  2. Hold PTT and talk, then release it. Or turn VOX on and just talk.
  3. To send a voice memory, tap it. With TX ON it is transmitted, and you hear it on your speaker too. With TX OFF it is only played to you, which is a good way to check a recording. A long press (a right click on the computer) always only plays it to you.
  4. When the contact is over, press QSO to log it.

Your own live voice is never played back on your speaker. If the frequency you are about to transmit on is outside the amateur band, qFT8 does not key the radio and says so.

Transmission limit: Every SSB transmission ends by itself at the radio's continuous transmission limit (Device Configuration), or after 3 minutes when the radio has no limit. With Tap to toggle and with VOX the PTT button counts the seconds left down (with Hold to talk and voice memories, only when the radio has a limit). After the limit, VOX stays paused for the same time, or until you tap PTT. This protects the radio from a microphone that keeps hearing noise.

Voice memories

Go to Settings > SSB > Voice memories (or tap Configure voice memories in Settings in the pane) and press RECORD A NEW VOICE MEMORY. You can keep up to 6 voice memories of 30 seconds each. For each one you can give it a name, record it again, set its volume or press NORMALIZE, and cut silence from its start and end by dragging the two handles on the picture of the sound; PLAY plays the part you kept, and nothing changes until you save. Voice memories are part of the settings export, recordings included. A voice memory records your own voice from your microphone, not the sound of the radio. qFT8 does not record your contacts.

Settings > SSB

What SSB needs

QSOs are logged as SSB with their sideband, and are uploaded to QRZ and LoTW like any other QSO.

On the computer, the iPhone and the web remote

↑ Back to Table of Contents

AM, FM, airband and marine VHF (voice)

The mode list has more voice entries that open the SSB pane with another receiver behind it: AM and FM (the amateur bands, receive and transmit; each also as an I/Q row, see below), Airband voice (aircraft and towers, 118-137 MHz, receive only) and Marine VHF (ships and coast stations, receive only). The bottom bar then names the mode AM or FM, and the sideband choice goes away: these signals have none.

Specifications: ITU emission classes A3E (AM, airband) and F3E (marine VHF, narrow FM, 25 kHz channels); international maritime channels of the ITU Radio Regulations, Appendix 18; airband 118-137 MHz with 25 kHz or 8.33 kHz channels (ICAO Annex 10).

Talking in AM

AM is sent exactly as SSB is: the operator's TX ON first, then PTT or VOX, voice memories, the radio's continuous transmission limit. qFT8 sends AM only inside an amateur band (both sides of the carrier must fit) and only through a radio it has put in AM. QSOs are logged as AM.

FM voice: narrow and wide

FM is amateur FM voice (10 m, 6 m, 2 m, 70 cm and up), received and transmitted like AM, and logged as FM. It opens on 29.600 MHz the first time (the 10 m FM calling frequency) and on your last frequency afterwards. Where the AUTO RIT button is in SSB, a button shows the channel width; tap it to switch:

FM is mono: stereo belongs to broadcast FM (the broadcast screen). The width also decides the band-edge check: qFT8 transmits only when the whole channel fits inside the band. With a radio under CAT qFT8 selects the radio's plain FM mode; for narrow transmit, set the radio's own FM-N or narrow filter as well (qFT8 does not change it).

The radio or I/Q: AM / AM I/Q, FM / FM I/Q

Like SSB and SSB I/Q, each of AM and FM has two rows. The plain row lets the radio demodulate: qFT8 puts it in its own AM or FM mode and plays the radio's audio, with the audio spectrogram. The I/Q row (experimental) takes the raw I/Q of an SDR, or of a radio that gives one (a QMX in its I/Q mode), demodulates it in the app and shows the wide I/Q spectrogram. That is how a radio whose own receiver is only 3 kHz wide can still hear an FM channel: its I/Q is 48 kHz wide. FM I/Q needs I/Q at 32 kS/s or more (a KiwiSDR's 20 kS/s is too narrow). A radio without an FM (or AM) mode has the plain row greyed, shown only with Show all.

LOW BANDWIDTH on the TX button

Receiving and transmitting are separate questions. When the selected radio cannot transmit the row's mode, the TX button turns red and reads LOW BANDWIDTH (in English, like all its words): an SSB / CW / data radio's transmitter is about 3 kHz wide, while AM needs about 6 kHz and FM 11-16 kHz. You keep listening; nothing is keyed, and TX stays as you left it. qFT8 knows this from the makers' documents of each radio; when they do not settle a case (narrow FM, which depends on the radio's own setting) it does not block. With a receive-only SDR the button reads NO TX / SDR as in every mode.

Airband and marine VHF

Both are receive only: the pane has no PTT, no VOX and no QSO button. In their place it shows the channel with two arrows to step down and up (the frequency wheel steps channels too) and the frequency below it. Airband steps 8.33 kHz in Europe, Africa and the Middle East (by your locator) and 25 kHz elsewhere, and opens on 121.500 MHz the first time; marine VHF opens on channel 16 and hears each duplex channel on its coast station frequency. Each keeps the last frequency you used. Listening to these services is not allowed everywhere: check the rules of your country.

The passband tag on the spectrogram reads RX there, never RX/TX: qFT8 does not transmit in these services, and with a radio under CAT the TX button reads NO TX / RX (see The mode selector). Airband and marine VHF with an SDR never ask for a transmitting radio. In SSB and AM without one the pane stays usable for listening, and a red line at its bottom, “Connect a radio to use SSB.” (or “...to use AM.”), opens Device configuration when tapped. On the computer, with no radio under CAT (an SDR or a sound card alone), the mouse wheel over the spectrogram zooms in SSB, AM, airband and marine VHF. Picking an amateur mode or band afterwards goes back to the band you were on before the receiver.

↑ Back to Table of Contents

FreeDV (digital voice, experimental)

FreeDV in the mode list (HAM tab, digital voice, one row marked experimental) is digital voice on HF, compatible with FreeDV 700D, 700E, 1600 and 700C: your voice is coded with Codec 2 700C and sent as a narrow (about 1 kHz wide) signal of 17 carriers centred 1500 Hz above the dial, with error correction, and a station heard in it is decoded back to speech on your speaker. It opens the SSB pane with the same tuning, audio levels, memories and meters; it is always upper sideband, on every band. Besides RADE V1 and RADE V2 (below) it has four classic submodes: 700D (the most used of them), 700E (for fast fading, about 1.5 kHz wide), 1600 (the older one, with clearer speech, Codec 2 1300, about 1.2 kHz wide, which needs a stronger signal) and 700C (the same speech as 700D without error correction: every bit is sent twice, on two carriers; it locks on quickly and copes well with fast fading at medium signal levels, about 1.5 kHz wide, no text channel). Pick the submode in the list beside the mode in the bottom bar (RADE V1 and RADE V2 are at the top), or tap the status button to go from one to the next; the choice is remembered. Both stations must use the same submode.

RADE V1 is the first submode in the picker and the default: the radio-autoencoder digital voice that most FreeDV stations use today. It carries wideband speech (up to 6 kHz in qFT8) in about 1.5 kHz of RF and stays usable down to about -2 dB SNR (3 kHz), with a delay of 120 ms. Its status button reads RADE V1 NO SYNC while it searches and RADE V1 SYNC 4 dB (the signal-to-noise ratio) once locked. The receiver, transmitter, speech analysis and synthesiser are qFT8's own, running the published RADE V1 model data (credited in the licences); your callsign (Settings) is sent in the end-of-over frame of every over, as RADE stations do, and the other station's callsign, received at the end of its over, shows on the status button for a minute (for example RADE V1 NO SYNC HB9IPH) and in the raw message log. PTT, VOX and the memories work with TX ON as for the other submodes, the same transmit limits apply, and both stations must use the same submode. It is experimental, like FreeDV. RADE V2, just below it, is the next version of the same idea (narrower, about 0.9 kHz, and a few dB more sensitive); its published waveform is still being developed and may change, so it is marked experimental and needs the other station on RADE V2 too.

Specifications: FreeDV 700D: OFDM, 17 data carriers spaced 55.6 Hz (1000-2000 Hz audio), coherent QPSK with one pilot row every 8 symbols, 20 ms symbols (2 ms cyclic prefix), 160 ms frames, LDPC (224,112), speech 700 bit/s (Codec 2 700C), a 25 bit/s text channel (varicode); used about 14.236 MHz and 7.177 MHz USB. FreeDV 700E: 21 data carriers spaced 71.4 Hz (750-2250 Hz audio), one pilot row every 4 symbols, 20 ms symbols (6 ms cyclic prefix), 80 ms frames, LDPC (112,56), the same speech codec and text channel. FreeDV 1600: 16 DQPSK carriers spaced 75 Hz (900-2100 Hz audio) and a BPSK pilot at 1500 Hz with twice their amplitude that marks the frames, 50 baud (20 ms symbols, root raised cosine 50 %), 40 ms frames, speech 1300 bit/s (Codec 2 1300) with its 12 most important bits protected by a Golay (23,12) code, a 25 bit/s text channel (varicode). FreeDV 700C: 14 carriers (770-2150 Hz audio, spaced about 106 Hz), each data symbol sent on two of them (diversity), coherent QPSK with 2 pilot symbols and 4 data symbols per carrier in each 80 ms frame, 75 baud (root raised cosine 50 %), speech 700 bit/s (two Codec 2 700C frames per frame), no error correction and no text channel. RADE V1: OFDM, 30 carriers spaced 50 Hz (750-2200 Hz audio), one pilot row every 5 rows, 20 ms rows (4 ms cyclic prefix), 120 ms frames carrying the speech as continuous-valued symbols from the published radio-autoencoder model, envelope clipped (peak-to-average under 1 dB), an end-of-over frame; speech 16 kHz (6 kHz in qFT8). RADE V2: 14 carriers spaced 62.5 Hz (1062-1875 Hz audio), no pilots, 16 ms symbols (4 ms cyclic prefix), 40 ms frames.

↑ Back to Table of Contents

CW (Morse code)

In CW mode qFT8 reads every Morse signal in the passband and writes its text on the spectrogram, and sends Morse from on-screen paddles, your own keys, ready-made messages or typed text. With TX OFF everything works as practice: you hear your sending on the speaker and nothing goes on the air.

Specifications: ITU-R Recommendation M.1677-1, “International Morse code” (2009).

qFT8 sends CW as a clean, shaped audio tone through the radio's data mode (for example DIGU or DIGL, USB-D or LSB-D), so the radio switches to that mode while it transmits and receiving stays wide. The QRP Labs QMX is the exception: it is keyed in true CW over CAT.

Pick CW with the mode selector of the bottom bar:

qFT8 Camera qFT8 CW pane

These are the components of the CW screen in detail:

  1. AUTO: Lets qFT8 hold whole CW QSOs by itself (see AUTO in CW).
  2. RX / TX / RX/TX: Chooses which bar a tap on the waterfall or the tuning wheel moves: the receive bar, the transmit bar, or both together. AUTO RIT, after them, moves the receive bar onto a station that calls you (see AUTO RIT).
  3. The gear opens Settings > CW, and QSO opens the logger with CW, the frequency and the target already filled in.
  4. Target: The callsign of the station you are working. It fills the [TARGET] part of your messages. Tap it to type one, or tap a callsign in the decoder line (item #10) to take it from there. While AUTO is on and TX is off, a grey line under it says K1ABC calls you – press TX ON when a station calls you.
  5. Memories: Ready-made messages. A tap sends one. Your own callsign is shown in blue and the report in yellow. A memory that still needs something (a target, your name...) is dimmed; tap it to see what is missing. With AUTO RIT on, the Follow K1ABC +150 Hz? lines of the stations calling you appear at the top of this list.
  6. WPM and FARNSWORTH: The sending speed in words per minute, and the optional Farnsworth speed (the letters keep their speed and the gaps between them get longer).
  7. FILTER, NR and SIDETONE: The width of the receive filter around the receive bar, the noise reduction, and the volume of your own sidetone (see Sidetone).
  8. The paddles: The left one sends dits and the right one sends dahs. Press both for the iambic modes.
  9. The red line: Press TX ON to transmit. While it shows, your keying is practice.
  10. The decoder line: Where the message selector is in FT8. It shows the text of the station inside your filter in white and what you send in green, newest at the right. A tap on a callsign offers it as the target; a tap anywhere else puts the whole conversation on that frequency in the place of the spectrogram, newest at the bottom (drag to read older text), while the decoder line becomes a small waterfall: a short tap on it brings the spectrogram back, and holding it and dragging sideways retunes.
  11. Decoded text on the waterfall: Every signal has its text written along its own trace, so you can read the whole band at once: the station inside your filter in green, the target in magenta, the others in white and what you send in yellow; a word still being re-read is written in italics. The label under the receive bar shows the callsign and speed of the station you are on.
  12. The tuning wheel: The frequency scale. Swipe along it to move the selected bar (and the radio, when the bar reaches the edge). A tap or a drag on the waterfall moves the bar directly.
  13. Go to frequency: Tap the strip with the white signal-strength line to type a frequency in kHz.

Sending

There are four ways to send, and all of them use the speed set with WPM:

On the air, CW is always a clean tone with soft edges, whatever sidetone you choose to hear. As a safety net, a key held down for 10 seconds is released and a transmission is stopped after 3 minutes.

Practice with TX OFF

While the bottom bar says TX OFF, the paddles, your keys, the memories and the Keyboard box all work, but only on your speaker. What you key is decoded and shown in green in the decoder line, so you can see whether your sending is readable. Nothing reaches the radio. No radio is needed at all for this.

Paddles and keyer

In Settings > CW, the Keyer section sets how the paddles behave:

The Paddle input section sets what counts as a paddle:

While a text box is open, only the Ctrl keys and F1 / F2 act as paddles, so typing a callsign never sends Morse.

Keying with an adapter, the keyboard or the mouse

You do not have to tap the screen to send Morse. Four things can act as the paddles, and they can all be used at the same time:

All of them follow the Keyer mode and the speed you have chosen, and all of them work with TX OFF as practice (see Practice with TX OFF).

Connecting an adapter

  1. Plug your key or paddle into the adapter, and the adapter into the phone, the tablet or the computer. Nothing has to be installed and qFT8 asks for no permission: the adapter is an ordinary keyboard or mouse. On a phone whose only USB socket is taken by the transceiver, use a USB hub or a Bluetooth adapter.
  2. Open the CW screen and key. An adapter that acts as a keyboard works at once when it sends keys of the default list below (the left and right Ctrl keys, and [ and ], are the usual ones). It was tested with the original VBand adapter.
  3. If nothing sounds, the adapter sends other keys. Go to Settings > CW > Paddle input, press ADD A KEY under Left paddle (dit) and close the dit contact of your key; then do the same under Right paddle (dah) with the dah contact.
  4. An adapter that acts as a mouse needs the paddles on the screen: leave the mouse pointer over the left paddle and key. The same goes for an ordinary mouse.

The keys and buttons that work without setting anything

Keyboard, or an adapter that acts as a keyboard
Left paddle (dit) [  A  ,  Left arrow  1  0  Num 1  Num 0  L-Ctrl  L-Shift  L-Alt  Num .  F1
Right paddle (dah) ]  D  S  .  Right arrow  3  9  Num 3  Num 9  R-Ctrl  R-Shift  R-Alt  Num Enter  F2
The same, while a text box is open
Left paddle (dit) L-Ctrl  F1
Right paddle (dah) R-Ctrl  F2
Mouse, with the pointer over the left paddle
Left paddle (dit) left button
Right paddle (dah) right button
Mouse, with the pointer over the right paddle
Left paddle (dit) right button
Right paddle (dah) left button

The mouse rule is decided when the first button goes down: the main (left) button is the paddle under the pointer and the other button is the other paddle, until both are released. A held key does not repeat. A press while a memory or a typed text is being sent stops that text and sends nothing itself; release and key again.

A straight key, a paddle, a bug

Keyer mode (Settings > CW > Keyer) decides what the two sides do, whatever you key with:

Making it yours

Everything is in Settings > CW, in the section Paddle input:

Two more options are in the Keyer section: Inverse paddles swaps dits and dahs for every source at once (for a paddle wired the other way round, or a left-handed operator), and Keyer mode is described above. RESET TO DEFAULTS, at the end of the page, puts every CW setting back, the key lists included.

Android and the computer

If something does not work

Memories, macros and prosigns

Edit your messages in Settings > CW > Memories (ADD MEMORY, or tap one to change it). Two kinds of special words can be used in a message:

Loop: the button with two arrows in a loop, at the right end of each memory, sends that memory again and again, for a CQ or a beacon-like call. A tap on it asks for the pause between two sends: 15, 30, 60, 90 or 120 seconds, counted from the end of the message (Off stops it). While it loops the button is green and counts down the pause. It works only while TX is ON; any touch of the paddles or the key (that touch is not sent), another memory, a typed message, STOP, TX OFF or a station answering you ends it. Every send counts against your radio's transmission limit, like any message.

Your report, name, location and exchange are typed once, in the same Settings page. A ready-made message that needs one of them stays dimmed until you fill it in, and tapping it takes you to the place to do so. While a POTA or SOTA activation is open, a CQ POTA message is offered as the first memory.

Receiving

Decoding is automatic and follows each station's own speed. The station inside your filter is the one written in the decoder line of the bottom bar; move the receive bar onto another signal to follow that one instead (what was already copied on that frequency is shown at once). When two stations are inside the filter the bottom bar says so. The received signal is played on your speaker at the Monitor pitch you choose, the same pitch as your own sidetone, so a station that sounds at the same note as your sidetone is exactly on your frequency.

Settings > CW also has Tones (how your sidetone sounds: pitch, volume, soft or hard edges, a tone or sounder clicks), Decoding and display (Auto-decode, Multi-decoder for the text of every signal on the waterfall, the horizontal spectrogram, the filter when entering the mode), Monitor (speaker) and Prosigns and signs.

Sidetone

The sidetone is what you hear of your own sending, on the speaker or headphones of the phone or the computer. It never goes to the radio. SIDETONE, the last button of the right-hand column, shows its volume; a tap opens a slider beside it, Sidetone volume, and another tap closes it. It is the same setting as in Settings > CW > Tones. While you send, the volume keys change the sidetone too.

In Tones you also choose its Monitor pitch (the same pitch as the received signal), Sidetone rise / fall, Sidetone wave and Sidetone sound (Tone or Clicks (sounder)). These only change what you hear: on the air CW is always a clean tone with soft edges. Speaker keep-alive keeps phones and Bluetooth headphones awake between presses so that the first dit is not cut; raise it if the start of a dit is missing. To switch the sidetone or the received signal off, use Play what you send (sidetone) and Play the received signal on the speaker in Monitor (speaker).

Mute the radio's sound while transmitting (in Tones, off by default) keeps the received signal silent while qFT8 transmits and for a moment after each over, while the radio's own sidetone still comes back over USB; your own sidetone keeps playing. When you send with your own key or paddles plugged into the radio, qFT8 cannot tell that the radio is transmitting, and the radio's sidetone reaches you through the phone or the computer a little late: listen on the radio's own headphone jack instead, where it has no delay.

On the iPhone there is no sidetone and no SIDETONE button.

AUTO in CW

The AUTO button at the top left of the pane lets qFT8 hold complete CW QSOs. It is off every time you enter the mode. Tap it to switch it on (it turns green) and again to switch it off. It only ever sends while TX is ON: AUTO never arms transmission by itself.

While it is on, and TX is ON, qFT8:

While AUTO is on the paddles are disabled and a line says Disable AUTO to transmit manually. STOP also switches AUTO off. If you never want it, turn Show auto mode off in Settings > CW and the button is hidden.

AUTO RIT: following a station that calls you

A station that answers your CQ is often a little off your frequency. AUTO RIT, the button after RX/TX, takes care of that. It is off until you switch it on, and qFT8 remembers your choice. When it is on it turns green, and:

AUTO RIT only moves the receive bar. It never transmits and never switches TX on, and nothing heard while you are sending counts.

How the radio is keyed

In both cases STOP or TX OFF in the middle of a dit or dah ends it cleanly and the radio goes back to receive. While qFT8 sends, the TX button shows that it is transmitting.

Logging a CW QSO

QSO, at the top right of the pane, opens the logger already filled in: mode CW, the band and your transmit frequency (and the receive frequency when the two bars are apart), the callsign in Target, and the reports. The reports are the ones really exchanged when AUTO worked that station; otherwise the report you send is your Report to send [RST] (or, when that is empty, the one measured from the signal) and the report you received is the one read from the other station's sending. The park or summit of an open activation is filled in too. Check it, change what you need and save (see The logger).

AUTO logs each QSO it completes by itself, with both reports and the other station's name and location in the comment, and says Logged K1ABC. With Send cut numbers (5NN) on, reports are keyed as 5NN, but the log always stores 599.

Logging the QSOs you key yourself

qFT8 listens to your keying through the radio (if the radio passes it back) and logs your CW QSOs. Many radios send their own transmit audio (the TX monitor, or the sidetone) to the computer or phone over USB. When you key the radio with your own key or paddles, qFT8 reads your sending and the other station's replies with the same decoder, follows the exchange (the other callsign, the report each way, the name and the QTH if they are sent) and logs the QSO once it is finished, the way AUTO does, with Logged K1ABC.

A QSO is logged only when your own call was heard after DE in it (that is how qFT8 knows the radio passes your keying back), the other callsign was copied clearly, and both reports were exchanged. Anything less is not logged. Turn it off with Log the QSOs I key myself through the radio in Settings > CW. It needs Auto-decode on, and it rests while AUTO is on.

CW key line (on the computer): a radio keyed through its key jack, for example with an optoisolator on a second serial port, can be keyed by that port's DTR or RTS line. Choose the line and the port in Settings > CW; it is kept for each radio and is off unless you choose it. qFT8 keys it only while you have TX ON, with the same transmit limits, and the key goes up on STOP, TX OFF, at the limit, when the port goes away and when qFT8 closes.

On the computer, the iPhone and the web remote

↑ Back to Table of Contents

RTTY and JTTY

RTTY (radioteletype) sends text as two alternating tones. In qFT8 it shares the screen of CW, without the paddles: every RTTY signal in the passband is decoded, each at its own speed and shift, and written along its trace on the waterfall. The same screen also runs JTTY, a newer weak-signal text mode (see RTTY and JTTY: the differences).

Specifications: ITU-T Recommendation S.1, “International Telegraph Alphabet No. 2”; 45.45 baud and 170 Hz shift are amateur practice.

qFT8 Camera qFT8 RTTY pane

These are the components of the RTTY screen in detail:

  1. Target and Exch: The callsign of the station you are working and the contest exchange. They fill [TARGET] and [EXCH] in your messages. Tap one to type it; tap a callsign in the decoder line (item #7) to take it as the target.
  2. BAUD: The speed: 45.45 (the usual one), 50 or 75. Each tap steps to the next.
  3. SHIFT: The distance between the two tones: 170 Hz (the usual one), 200, 425 or 850 Hz. The filter follows the shift.
  4. REV: Swaps the two tones, for a station that sends them the other way round. It is amber while it is on.
  5. FILTER and NR: The receive filter and the noise reduction.
  6. Memories: Ready-made messages with the same macros as in CW. A tap sends one. A message with an empty field is dimmed: tap it to see what is missing. Keyboard (and Voice on the phone and the iPhone) are at the end of the list.
  7. The decoder line: The text of the station under the receive bar, in green; what you send, in red. Tap it (anywhere but on a callsign) to see the whole conversation on that frequency in the spectrogram's place; tap the small spectrogram that replaces the line to go back.
  8. The receive bar and its label: The label shows the callsign, speed and shift of the station under the bar. A tap near a signal puts the bar on its centre.
  9. A station with other settings: When the station under the bar uses a different speed, shift or tone order than yours, its label turns amber, and the BAUD, SHIFT or REV buttons that differ turn amber and read match with that station's value. Tap the label or one of those buttons and qFT8 takes all of that station's values, so that you can answer it.
  10. Other signals: Their text is written along their own traces. Only the station under the receive bar says how it differs from your settings.
  11. Frequency: In RTTY the header shows the mark frequency, which is the frequency operators quote and the one written to the log.

Also on this screen:

On the computer the same screen is used with the mouse and the keyboard. The web remote shows the received text with a box to type and send a message, a button to stop it, the AUTO RIT button and the Follow chips; its TX button is the app's own.

Sending

Arm TX, then tap a memory, or open Keyboard, type and press SEND. On Android, Voice does the same from speech: say the message, and what the phone understood opens in the Keyboard box to correct and send. A strip with STOP shows while the text goes out. With TX OFF the same actions are a preview: the message is played on your speaker and shown in red, and nothing goes on the air. Characters that the RTTY code does not have are left out and listed. The memory being sent stays green until it ends.

RTTY is a continuous full-power transmission, so the radio's continuous transmission limit applies: a message longer than the limit is not started, and a transmission stops when the limit is reached.

AUTO RIT and the Follow chips

A station that answers your CQ is often a little off your frequency. AUTO RIT, next to RX/TX, takes care of it. It is off until you switch it on; it turns green while it is on, and qFT8 remembers it. RTTY and JTTY each have their own switch. While it is on:

In JTTY a message arrives in frames, so the station's transmission counts as finished when its last frame has arrived.

Logging

QSO opens the logger (see The logger) with the mode, the band, the mark frequency, the target and the reports already filled in: the report you send is the one in your settings, and the report you received is read from the station's text when it sent one. One QSO per press. RTTY QSOs are logged as RTTY; JTTY QSOs as JTTY (in ADIF files and uploads, mode MFSK with submode JTTY). While a park or summit activation is open, its reference goes into the QSO too.

Settings > RTTY

There is no AUTO in RTTY or JTTY: qFT8 does not hold these QSOs by itself.

RTTY and JTTY: the differences

Pick JTTY (experimental) in the mode selector: the same screen opens with the JTTY modem and the mode button reads JTTY; the RTTY row brings RTTY back. Each one has its own frequency on every band, so switching between them moves the dial (on 20 m, for example, JTTY is on 14.090 MHz). JTTY is new and may still change. It works on the phone, the computer and the iPhone; the web remote shows it as it shows RTTY: the received text, AUTO RIT and its chips, and the text you send.

Settings > JTTY

JTTY (the JTTY (experimental) row of the mode selector) uses this same pane with the JTTY modem. Its settings have their own page, next to RTTY in the settings list; the pane's gear button opens it while the pane runs JTTY. It has only what JTTY uses: Decoding and display, Monitor (speaker), Memories with their values and RESET TO DEFAULTS; the Modem and Transmit settings of RTTY do not apply to it. The first time JTTY is used it takes over what you had changed in Settings > RTTY (for example your memories, name and location); anything you had not changed starts at JTTY's own defaults, such as short memories that each fit one JTTY message. After that, changing one does not change the other.

Specifications: no published specification.

Settings > Q65

Q65 (the Q65 (experimental) row of the mode selector) is one mode with a sub-mode picker beside the selector: the period (15, 30, 60, 120 or 300 s) and the tone spacing (A to E), named like 30A. There are 22 sub-modes (15 s: A-C, 30 s: A-D, 60, 120 and 300 s: A-E); the default is 30A. Q65 uses the FT8 messages and the same QSO flow (CQ, reports, RR73/73, AUTO, the stations list). QSOs are logged as MODE=MFSK SUBMODE=Q65 and spots go to PSKReporter as Q65.

Specifications: J. Taylor, B. Somerville, S. Franke, N. Palermo, “Q65 Quick Start”, 2021.

Typical uses are 6 m ionospheric scatter (30A, 50.275 MHz), 2 m scatter (60C, 144.170 MHz) and EME on 2 m and up (60A, 60B, 60C). The bands offered are 10 m (28.140), 6 m (50.275), 2 m (144.170), 70 cm, 23 cm and 13 cm (these three use the FT8 dial frequency until a Q65 one is confirmed). Transmissions last 12.75, 25.5, 51, 113.3 or 293.8 s and appear in the Continuous transmission limit setting; a 300 s sub-mode needs a limit large enough for it. Q65 is sent as audio only: qFT8 does not key it through the radio's CAT tone mode.

The Q65 section of Settings > DIGITAL MODES has:

Nothing is decoded that was not received: a decode found with a priori information has to pass the same checks as any other.

Settings > MSK144

MSK144 (the MSK144 (experimental) row of the mode selector) is made for meteor scatter: a meteor trail reflects the signal for a moment, so it is heard only as short pings. A transmission repeats its message for the whole period, and any ping long enough to carry it is decoded. MSK144 uses the FT8 messages and the same QSO flow (CQ, calls and grid, reports, RRR/RR73/73, AUTO, the stations list). QSOs are logged as MODE=MSK144 and spots go to PSKReporter as MSK144.

Specifications: S. Franke, J. Taylor, “The MSK144 Protocol for Meteor-Scatter Communication”, QEX, July/August 2017.

Every transmission is centred on 1500 Hz audio, with its tones at 1000 and 2000 Hz: the TX offset does not apply to MSK144. Each band's MSK144 calling frequency is set when you pick the band. MSK144 appears in the Continuous transmission limit setting like every mode.

The MSK144 section of Settings > DIGITAL MODES has:

References: the MSK144 article by Franke and Taylor in QEX (2016).

Settings > FST4

FST4 (the FST4 (experimental) row of the mode selector) is a weak-signal QSO mode for LF, MF and HF. It uses the FT8 messages and the same QSO flow (CQ, reports, RR73/73, AUTO, the stations list, the log), with 4 tones (GFSK) and 160 symbols. QSOs are logged as MODE=MFSK SUBMODE=FST4 and spots go to PSKReporter as FST4.

Specifications: S. Franke, J. Taylor, B. Somerville, “Protocol Specifications” (FST4, FST4W), 2020.

The transmit and receive period is 15, 30, 60, 120, 300, 900 or 1800 s, chosen in the bottom bar or in Settings. The longer the period, the narrower and more sensitive the mode: about -21 dB at 15 s to -43 dB at 1800 s (in 2500 Hz). Usual frequencies: 2200 m 136.000 kHz, 630 m 474.200 kHz, 160 m 1.8390 MHz. With the very long periods the transmitter stays on for up to 30 minutes: the Continuous transmission limit setting must allow it. FST4 is experimental.

The FST4 section of Settings > DIGITAL MODES has:

Settings > FST4W

FST4W (the FST4W (experimental) row of the mode selector) is a beacon mode like WSPR: it uses the same WSPR pane (spots list, beacon transmit percentage, upload to WSPRnet). Messages have 50 bits: CALL GRID POWER, or PFX/CALL POWER or CALL/X POWER. The period is 120, 300, 900 or 1800 s; sensitivity is about -33 dB (120 s) to -45 dB (1800 s). It decodes within the receive tolerance (default 100 Hz) around the receive frequency (normally 1500 Hz). Spots go to WSPRnet with the period.

Specifications: S. Franke, J. Taylor, B. Somerville, “Protocol Specifications” (FST4, FST4W), 2020.

Usual frequencies: 2200 m 136.000 kHz, 630 m 474.200 kHz, 160 m 1.8368 MHz. On the higher bands it uses the frequencies next to the WSPR dial frequencies. With the very long periods the transmitter stays on for up to 30 minutes: the Continuous transmission limit setting must allow it. FST4W is experimental.

The FST4W section of Settings > DIGITAL MODES has:

Settings > JT65

JT65 (the JT65 (experimental) row of the mode selector) is a one-minute QSO mode with 65 tones and a Reed-Solomon code; sensitivity about -25 dB (in 2500 Hz). QSOs are logged as MODE=JT65 with the sub-mode (JT65A, JT65B, JT65C) and spots go to PSKReporter as JT65. Usual frequencies (USB dial): 160 m 1.838, 80 m 3.570, 40 m 7.076, 30 m 10.138, 20 m 14.076, 17 m 18.102, 15 m 21.076, 12 m 24.917, 10 m 28.076, 6 m 50.276, 2 m 144.120 MHz.

Settings > JT9

JT9 (the JT9 (experimental) row of the mode selector) is a one-minute QSO mode with 9 tones, 16 Hz wide; sensitivity about -27 dB (in 2500 Hz). QSOs are logged as MODE=JT9 and spots go to PSKReporter as JT9. Usual frequencies (USB dial): 2 kHz above the JT65 ones from 160 m to 10 m (20 m 14.078 MHz).

Settings > JT4

JT4 (the JT4 (experimental) row of the mode selector) is a one-minute QSO mode with 4 tones and a convolutional code; sensitivity about -23 dB (in 2500 Hz) in JT4A. QSOs are logged as MODE=JT4 with the sub-mode (JT4A to JT4G) and spots go to PSKReporter as JT4. Frequencies (USB dial): 6 m 50.276, 2 m 144.120, 70 cm 432.065, 23 cm 1296.065, 13 cm 2304.065 MHz; any other frequency with the Other band.

↑ Back to Table of Contents

PSK31 and PSK63 (experimental)

Pick PSK in the mode selector and PSK31 or PSK63 beside the mode in the bottom bar: the same screen opens with the PSK modem and the mode button reads the mode's name. PSK31 is the classic keyboard-to-keyboard mode: one carrier whose phase turns over to carry the text, about 50 Hz wide, at 31.25 baud; PSK63 is the same at twice the speed and twice the width. Every PSK signal in the passband is decoded and written along its trace, and the one under the receive bar is always followed. Each mode has its own frequency on every band (on 20 m, 14.070 MHz).

↑ Back to Table of Contents

Olivia, MFSK16 and DominoEX (experimental)

The keyboard modes that send one tone at a time are in the HAM tab of the mode selector, one button per family (OLIVIA, MFSK family with MFSK, THOR, DominoEX and Throb, and so on), each marked experimental. The speed or variant is picked beside the mode in the bottom bar, and each family remembers the last one you used. The variants: OLIVIA 8/250, OLIVIA 8/500, OLIVIA 16/500, OLIVIA 32/1000, OLIVIA 4/250, MFSK8, MFSK11, MFSK16, MFSK22, MFSK32, MFSK64, MFSK128, DOMINOEX 8, DOMINOEX 11 and DOMINOEX 16. Picking one opens the RTTY screen with that modem, and the mode button reads its name.

↑ Back to Table of Contents

THOR, Contestia and MT63 (experimental)

Three more keyboard modes are in the HAM tab of the mode selector, one button per family with the variant picked beside the mode in the bottom bar, each marked (experimental): THOR 8, THOR 11, THOR 16, THOR 22; CONTESTIA 4/250, CONTESTIA 8/250, CONTESTIA 16/500, CONTESTIA 32/1000; MT63 1000L, MT63 2000L, MT63 500L and MT63 1000S. They work exactly like Olivia (see above): the RTTY screen with that modem, the signal under the receive bar decoded, a memory sent as one transmission, typed text a line at a time.

↑ Back to Table of Contents

Hellschreiber (Feld Hell, experimental)

Hellschreiber sends text as a picture: each letter is scanned in narrow columns and the receiver paints what it hears, so you read the text off the screen -- nothing is decoded to letters, and a weak or noisy signal still shows letters your eye can make out. Pick HELL (experimental) at the bottom of the mode selector: the RTTY screen opens with the Hell modem.

↑ Back to Table of Contents

Packet (APRS) (experimental)

Packet sends short AX.25 frames as two audio tones; APRS uses them for positions, objects, weather and short messages. Pick Packet (APRS) (experimental) in the HAM tab of the mode selector: the RTTY screen opens with the packet modem, and the speed is picked beside the mode in the bottom bar.

↑ Back to Table of Contents

SSTV (pictures)

SSTV (slow-scan television) sends a still picture as sound, line by line, in half a minute to about four minutes. qFT8 receives pictures by itself while you are in the mode, and sends your own pictures, a photo or one of its ready-made pictures, with your callsign written on them.

Specifications: J. L. Barber (N7CXI), “Proposal for SSTV Mode Specifications”, Dayton Hamvention SSTV forum, May 2000.

Pick SSTV with the mode selector of the bottom bar. The radio goes to the band's SSTV calling frequency, in USB. The pane shows one half at a time: RX, the pictures received, or TX, the picture to send. The two buttons at the top left switch between them; switching only changes what you see, it never sends anything.

The receive half (RX)

qFT8 Camera qFT8 SSTV pane, receive half
  1. AUTO: On (green, the default), qFT8 finds every picture by itself, in any mode. Off, it receives in one mode all the time, as a rolling picture (manual reception). The choice is remembered.
  2. RX | TX: The half shown. A yellow dot on RX means a picture came in while the send half was shown. SEND shows the send half by itself, and the pane comes back to the receive half when the picture ends.
  3. Receive status: LISTENING (every mode, whole passband); RECEIVING with the mode, how far off frequency the station is and the line being drawn; MANUAL when AUTO is off; PAUSED while you send.
  4. The gear opens Settings > SSTV.
  5. QSO opens the logger for the picture shown (logging).
  6. The received picture: the one arriving, drawn line by line, or the kept picture you chose in the strip. The mark in its corner: an amber ring that fills while it arrives (with a green arrow inside when it will be saved at the end), a green tick once it is saved, a grey arrow while it is not saved. Tap a kept picture to edit it.
  7. The caption: the time (UTC) and the mode; while the picture arrives, the percentage and the seconds left; for a kept picture, "joined at line ...", "signal lost at line ..." or "... lines lost" when it is not complete. Beside it, the callsign field.
  8. SAVE writes the picture to the pictures folder and turns green (SAVED). Pressed while the picture is still arriving, it shows SAVES WHEN IT ENDS.
  9. EDIT improves a kept picture: brightness, contrast, colour, hue, sharpening and noise removal. The picture as received is always kept: REVERT undoes everything, and SAVE COPY saves the edited version as a file of its own.
  10. REPLY asks for the other station's callsign (it starts from the callsign field) and writes "their callsign DE yours" under their picture, shown on the screen of an oscilloscope, in one of five reply layouts. To reply to an older picture, tap it in the strip first. The palette button (or a tap on the layout's name) chooses the frame: the oscilloscope, "Own picture" (the text goes on your picture to send instead, and their picture is not sent back), or one of nine other frames (retro TV, CRT monitor, instant photo, shack wall, porthole, cinema, airmail postcard, gallery frame, transceiver display). Your choice is remembered. The mode changes to the one the received picture used. If your continuous transmission limit is too short for that mode, a notice says so; the limit is never changed for you.
  11. The bin deletes the picture shown from qFT8, after a question. A copy already saved in the pictures folder stays there, and the question says so.
  12. The strip: the picture arriving first, then the kept pictures, newest first (the received pictures).
  13. The SSTV mode selector of the bottom bar: Martin, Scottie, Robot, PD, Wraase and Pasokon modes, each with the seconds a picture takes. It is the mode pictures are sent in, and the mode received when AUTO is off. Beside it, the message area says what is happening ("listening", "receiving" with the percentage, "sending" with the seconds left).
  14. The SSTV slot on the waterfall: pictures are sent and received between 1100 and 2300 Hz, with the Morse identification at 1000 Hz. Every picture heard or sent gets a box with its mode and callsign; tap a box to show that picture.

The send half (TX)

qFT8 Camera qFT8 SSTV pane, send half
  1. The mode the picture will be sent in, with its size and colour system. It is chosen with the mode selector of the bottom bar.
  2. LOAD opens Choose a picture.
  3. The picture to send, exactly as it will go on the air. Empty, it says Tap to load a picture. Tap it to fit it to the shape of the mode again. The small arrow in its corner saves it, as it will be sent, to the pictures folder.
  4. The callsign style: the arrows step through the 16 styles and No callsign; a tap on the style's name opens the style and colour picker.
  5. The palette opens the same picker: the styles as a list and eight text colours. Every choice shows on the picture at once and is kept for the next picture.
  6. The pen adds a line of your own text to the picture (the pen turns yellow while there is one).
  7. DROP removes the loaded picture.
  8. SEND shows the seconds the whole transmission takes. While the picture is on the air it becomes STOP with the seconds left, and the lines already sent are marked on the picture.
  9. The red line, at the bottom under SEND: Press TX ON to send pictures. With a QMX whose firmware cannot send pictures, it says so instead.
  10. The quick pictures: the last six pictures you loaded, then the ready-made ones, already in your callsign style. One tap loads one as the picture to send; it is never sent until you press SEND.

Receiving pictures

With AUTO on there is nothing to set. qFT8 recognises the mode of every transmission from its start signal, and also when you tune in after the picture has started (the lines already missed stay empty). It listens across the whole passband, from about 1000 Hz below to 800 Hz above the usual tones. A picture sent slightly off frequency, or by a station whose timing is a little off, is straightened automatically. If two stations send at the same time on clearly different frequencies, both pictures are received and kept; tap a box on the waterfall to choose the one shown.

Manual reception (AUTO off)

For a station whose start signal you missed or that qFT8 does not pick up by itself, switch AUTO off. qFT8 then receives the mode chosen in the bottom bar all the time, as one long rolling picture: the newest lines are added at the bottom and the picture moves up. The status says MANUAL with the mode and the offset; when a start signal is heard in some mode it says so, only as a hint (change the mode yourself).

Whose picture is it? The callsign field

Many stations identify themselves around their picture, in Morse code before or after it, or with a short data burst after it. qFT8 reads both, and writes the callsign in the field beside the caption. When nothing was heard the field says Callsign unknown. Tap the field to type the callsign yourself (often it is written on the picture) or to correct it; what you type replaces what was heard, and REPLY and QSO start from it.

The received pictures

qFT8 keeps the latest received pictures by itself, whether you save them or not: 100 of them unless you change Received pictures kept in the app; the oldest is dropped when a new one arrives. They survive a restart. The strip under the picture shows them, newest first, each with its saved / not saved mark; the picture still arriving is first. Tap one to show it; while a picture arrives, tap the first one to follow it again. When nothing is arriving, the newest kept picture is shown.

The pictures folder

SAVE (or Auto-save every received image to the device) writes the picture as a PNG file, and a notice says where:

Auto-save is off on a phone, a tablet and an iPhone, and on on a computer. On the iPhone a saved picture also goes to your Photos (the system asks once). Saved pictures are named with the date and time (UTC), the band, the frequency in kHz, the mode and the callsign, for example 2026-10-05_1431_20m_14230_M1_Q1ABC.png, or ..._UNKNOWN.png when there is no callsign. If the callsign arrives or is typed after the picture was saved, the saved file is renamed; no second copy is made. An edited copy ends in _edit.png, and a picture saved from the send half in _tx.png. Deleting a picture in qFT8 never deletes a saved file.

Sending a picture

  1. Choose the mode with the selector of the bottom bar. If you answer a station, use the mode it used (REPLY does this for you). Robot 36, Martin 1 and Scottie 1 are the common ones.
  2. Press LOAD (or tap the empty picture). Choose a picture shows your own pictures (Gallery; Files on a computer), the Camera where there is one, and 69 ready-made pictures (CQ cards, the qFT8 logo, landscapes, optical illusions, a QSL card, 73..., and ten frames such as a retro TV or an oscilloscope with a test card on their screen). You can also share a picture to qFT8 from another app; if another mode is in use, qFT8 asks before switching to SSTV.
  3. If the picture does not have the shape of the mode, Fit the picture follows: WHOLE shows all of it with borders, CROP fills the frame (drag to move, pinch to zoom), ROTATE turns it, and brightness, contrast and Auto contrast adjust it. USE PICTURE takes it.
  4. Callsign style follows: your picture in each of the 16 callsign styles. Tap one and press USE; BACK returns to the pictures.
  5. Arm TX with the TX ON button and press SEND.

Switching TX off, pressing STOP, or changing band or mode stops the picture at once; after STOP, TX stays on, ready to send again. If a picture is arriving when you press SEND, qFT8 asks before it stops receiving.

The callsign styles

The date is the UTC date when the picture is sent, and the band the one you are on. "CQ" in a style is written as CQ DE and your callsign.

  1. CQ + date + band, in a band at the bottom (the default).
  2. Callsign alone, in a band at the bottom.
  3. Big date + band, bottom: CQ and your callsign, with the band and date in big letters.
  4. Big date + band, top: the band and date in big letters at the top, CQ and your callsign at the bottom.
  5. Strip: callsign + date + band: the picture a little smaller, above a strip with CQ, your callsign, the date and the band.
  6. Strip: callsign: the same, with your callsign only.
  7. Big CQ + date chip: a big CQ in the corner and a small label with the band and date.
  8. Callsign center: your callsign in big letters in the middle.
  9. Ticket + date: a ticket in the corner with your callsign, band and date.
  10. Callsign top left.
  11. Frame + date: a coloured frame, with your callsign and the band and date in it.
  12. Callsign shadow: your callsign with a drop shadow.
  13. CQ CQ + date: CQ CQ CQ at the top, your callsign, band and date at the bottom.
  14. Callsign top band: your callsign in a light band along the top.
  15. Postmark date: your callsign at the top left and a round postmark with the band and date.
  16. Layered callsign: your callsign with several outlines round the letters.

No callsign writes nothing on the picture (only your own line of text, if you added one). The callsign is still sent in Morse code or as FSK ID if those are on in Settings. A reply picture uses one of the five reply layouts instead (one above the other, side by side, top and bottom, big outline, with date + band); the arrows and the palette step through those.

Transmission limits

A picture is one continuous transmission at full power: about 40 seconds in Robot 36, two minutes in Martin 1, and more than four minutes in the slowest modes. Everything counts: the start signal, the Morse callsign, the picture and the FSK ID, and the seconds on SEND and in the mode list are that whole time.

A QMX or QMX+ needs firmware 1_04_001 or newer to send pictures; with older firmware SSTV is receive only and the red line of the send half says so.

Logging an SSTV QSO

Nothing is logged by itself. Show the other station's picture and press QSO: the logger opens with mode SSTV, the band, the radio's frequency, the callsign from the callsign field, and 595 sent and received. A notice asks you to check the callsign, or to type it when none was found. Save it as any other QSO; it is then uploaded to your services like the others.

On the computer, the iPhone and the web remote

Settings > SSTV

Open it with the gear of the pane, or from the Settings tab. Receiving:

Sending:

RESET TO DEFAULTS puts every SSTV setting back.

↑ Back to Table of Contents

DRAW (pictures on the waterfall)

DRAW paints a grey picture straight onto the other stations' waterfall: every column of the picture is one tone, 6.25 Hz from the next, and every line of the picture is sent for a fraction of a second, from the bottom line to the top one. Anyone with a waterfall sees your picture appear, with or without qFT8. A picture can have any shape: a photo, a drawing, or just a line of text such as your callsign. DRAW is not a standard mode; it is made to be seen.

Specifications: qFT8’s own design.

Pick DRAW with the mode selector of the bottom bar. RX and TX at the top of the pane show the receiving or the sending half:

qFT8 Camera qFT8 DRAW pane, sending side
  1. The facts: the width, the size of the picture in columns and lines, and the speed.
  2. LOAD: "Take a photo" or "Choose a picture". The picture keeps its own shape.
  3. The picture to send, in grey, drawn in the colours of your own waterfall: this is what the other stations will see. The grey around it is not sent. While it is on the air a yellow line marks the line being sent -- the bottom line goes first, so it climbs from the bottom -- with "On the air: line N of M".
  4. Callsign (on by default; the tick box on the button shows it): your callsign in big letters under the picture. The pencil changes the text of the plate (empty = your callsign). Auto contrast makes the darkest part of the picture black and the brightest white, in one press; Contrast and Brightness are yours to set by hand afterwards.
  5. DROP goes back to the callsign plate alone. SEND shows how many seconds the picture takes, and becomes STOP with the seconds left. Every picture, turned or not, and a text plate of any length, is made smaller and centred so it is sent in at most 30 seconds and within your radio's continuous transmission limit; a short picture stays as it is. If your limit is too short even for the smallest picture, SEND is greyed and reads "SEND · 12 s · too long".
  6. The red line, at the bottom under SEND, says why the picture can't be sent now, and is hidden when nothing stops it: "Press TX ON to send pictures"; "20 s: over your 15 s limit" (the picture is longer than your radio's continuous transmission limit); "Only the 500 Hz width may be sent on 30 m"; "TX would be outside the amateur bands"; or, with a QMX whose firmware cannot switch the radio to SSB over CAT, that pictures can only be received.
  7. SPEED: 3.125, 6.25 (the default: one line takes as long as one FT8 tone) or 12.5 lines per second; the list shows the picture's seconds at each speed, and a speed too long for your limit says so when you tap it. Beside it: how much of your continuous transmission limit the picture uses ("20 s of your 30 s limit").
  8. Text plates: one tap loads "CQ" and your callsign, "73" and your callsign, or your callsign alone, as the whole picture.
  9. ROTATE (the turn-arrow button beside DROP) turns the whole transmission, plate included, a quarter turn at each press, so it reads upright on a waterfall that scrolls sideways; the button shows the turn (90°, 180°, 270°). A long picture turned sideways is made smaller so all of it is sent. On the receiving side, ROTATE turns the picture shown (and saved) the same way.
  10. The width in the bottom bar: 500, 700 (the default) or 1200 Hz, with the picture's seconds at each width. A wider picture has more columns, so it is sharper and takes longer.
  11. The DRAW band on the waterfall: the picture sits between 1000 Hz and 1000 Hz plus its width.

Receiving pictures

qFT8 Camera qFT8 DRAW pane, receiving side

There is nothing to start: qFT8 listens all the time while you are in the mode, also while the sending half is shown.

  1. RX and TX: the receiving and the sending half.
  2. The status line: listening, the width and the band it listens to (1000–1700 Hz at 700 Hz). While your own picture is on the air the receiver pauses and the line says so.
  3. The received picture: the DRAW band of the last three minutes as one picture, the newest line on top, with square pixels, drawn in the colours of your waterfall: a picture sent with qFT8 appears upright. Before anything arrives it says which frequencies it listens to.
  4. The live tag: the mode, the width and the speed the picture is drawn at.
  5. SAVE (blue once there is something to save) stores the picture shown, cut to where it stands out of the noise, in grey, as received, as a PNG named with the date and time (UTC) and the width. On a phone or tablet it goes to the pictures folder, in Pictures/qFT8 DRAW; if qFT8 may not write there, it is kept in qFT8's own folder and the notice says where.
  6. ROTATE (the turn-arrow button) turns the picture shown (and saved) a quarter turn at each press; the button shows the turn (90°, 180°, 270°).
  7. SPEED: set it to the speed the other station uses (3.125, 6.25 or 12.5 lines per second); the whole received picture is drawn again at the new speed. It does not change the speed you send at.

Your radio's AGC: a radio's automatic gain control turns its gain down on a bright line and up on a dark one, which stripes a received picture. qFT8 measures the noise beside the picture on every line and corrects for it, and says so when it sees the gain moving with the picture: then set the radio's AGC to OFF or SLOW (and turn the RF gain down a little if the band is loud).

Sending a picture

  1. Choose the width in the bottom bar and the speed with SPEED.
  2. Load a picture, or tap a text plate. Set the contrast, or press Auto contrast.
  3. Arm TX and press SEND.

Switching TX off, pressing STOP, TUNE, or changing band or mode stops the picture at once. A picture is shrunk to fit your radio's continuous transmission limit; only under a limit too short for the smallest picture is it not sent: the red line says how long it is, and a faster speed brings it under the limit. All the tones are sent at once, so keep the transmit level as for FT8, with the radio's ALC low.

On the computer, the iPhone and the web remote

The pane is the same everywhere, with the same buttons. The differences:

How far does it reach?

DRAW is made to be seen, not to dig signals out of the noise. A callsign plate at the default 700 Hz and 6.25 lines per second is readable down to about -2 dB SNR (2500 Hz bandwidth), at 3.125 lines per second about -5 dB; a photo looks good from about +4 dB. FT8 reaches about -21 dB, so if the other station can barely decode your FT8, it will not see your picture. Slower speeds and narrower widths reach further. Fading costs every mode about 6 dB. What DRAW gives you that other modes don't: anyone watching a waterfall sees your picture, with no special program.

Frequencies, sideband and logging

qFT8 tunes to its DRAW frequency on each band, chosen in the "all modes" segments of the IARU band plans of the three regions, away from the SSTV, digital and voice centres of activity (dial, USB): 160 m 1.865, 80 m 3.665, 40 m 7.190, 30 m 10.145 (500 Hz only), 20 m 14.335, 17 m 18.140, 15 m 21.400, 12 m 24.975, 10 m 28.520 and 6 m 50.380 MHz. 60 m has no frequency (the rules differ from country to country). On 30 m the band plans allow 500 Hz at most, so only the 500 Hz width is sent there. Check your own licence and local band plan.

The radio is in USB on every band. A station that listens in LSB sees the picture mirrored from left to right.

QSO opens the logger with mode DRAW: the logging standard (ADIF) has no DRAW, and a still picture sent line by line is what FAX means there (it counts as an image mode, as SSTV). A QMX needs the same firmware as for SSTV. Logs, files and uploads write it as FAX with the submode DRAW; parks (POTA) and eQSL get plain FAX.

↑ Back to Table of Contents

Satellites and the map compass

Amateur satellites are drawn on the World Map, moving in real time, and a satellite can be worked from the app: where it is, when it passes, where to point, and the Doppler shift. Everything is computed on your device from orbital data that qFT8 downloads only while satellites are shown. The compass helps you aim at a satellite or a station.

The SAT button and the satellites shown

The SAT button, in the map's left toolbar, shows or hides every satellite on the map (it is on by default). Hidden satellites cost nothing to bring back: the orbital data keeps updating, so pressing it again is instant. By default the map shows the HF satellites. Settings > World map > Satellites on the map chooses what it shows: HF, VHF, UHF and SHF, each as two-way (a repeater, transponder or digipeater you can work) or listen-only (beacons, telemetry, pictures); only the two HF rows are ticked at first, and ticking another row adds its satellites. A satellite can be both, for example a repeater on VHF and a beacon on HF. A satellite with no known frequency has no row: it shows only when every row is ticked, and a line under the rows says how many there are. When you tick a VHF or UHF band (6 m, 2 m, 70 cm, 23 cm) in Settings > Band selection, qFT8 asks whether to also show that band's satellites; Yes ticks both of its rows in Settings > World map. Every satellite on the map carries its name; where they crowd, zoom in to separate them.

Selecting a satellite: its track and footprint

Tap a satellite (or its name) and it is selected: the others stay on the map, faded, so one tap on another switches to it, and a tap elsewhere on the map deselects it. The selected satellite has its track for one orbit, its footprint (the part of the Earth where it is above the horizon) and a longer track ahead with a marker such as +2 h at regular times. Two choices in Settings > World map decide how that longer track looks:

Passes

Every tap on a satellite opens its short card: whether it is up now (and until when) or when it rises and how high it gets, its main mode and frequencies, and the next pass. A geostationary satellite is shown as always up; one with no pass in the next two days says so.

Working a satellite

WORK IT on the card keeps only that satellite on the map and opens where to point: the sky circle with the pass, the satellite, where your phone points, azimuth and elevation, the range and the Doppler shift, with ON TARGET when the phone points at it (and below the horizon while it is not up). A blue SAT chip appears on the spectrogram with the Doppler correction; tap it to open where to point again. FINISHED stops working the satellite.

The map compass

On phones and tablets with a compass, a button between the settings and full-screen buttons shows a red needle pointing to true north and the bearing your phone points to. The compass is on by default; turn it off with Compass on the map in Settings > World map, and the button, the needle and the line disappear and the sensor stops. It follows the screen, so it is right in portrait and in landscape.

↑ Back to Table of Contents

Broadcast radio: FM + RDS and AM (experimental)

With an SDR (for example an RTL-SDR dongle) qFT8 is also a broadcast radio. In the mode selector's SWL tab, tap FM + RDS or AM broadcast: the radio screen opens over the app, and the back arrow closes it. The operating mode and TX are not touched: this screen only receives.

While the radio screen is open it uses the SDR; the other modes get it back when you close it. A radio without I/Q output (most transceivers) cannot be used for this screen.

↑ Back to Table of Contents

Digital broadcast radio: DAB and DAB+ (experimental)

With an SDR that tunes Band III (174-240 MHz; an RTL-SDR dongle does) qFT8 receives digital radio. In the mode selector's SWL tab, tap DAB / DAB+. qFT8 tunes the channel you were on last (the first time: 12C) and, as soon as the ensemble is heard, lists its services with their names and plays the first one. This screen only receives.

Sound: DAB always, DAB+ through your system's decoder

DAB stations (the older system) play everywhere: qFT8 decodes their sound itself. DAB+ stations send AAC audio, a patented format qFT8 does not include. qFT8 plays it through a decoder that is already on your device:

On a computer the decoder runs in a small separate program that qFT8 starts by itself. If a decoder library crashes or stops answering, only that program stops: the radio screen says the decoder is being restarted, the station list and the text keep working, and the sound comes back by itself.

Installing the decoder by hand (Linux)

Distribution Debian, Ubuntu, Mint
Recommended sudo apt install libfdk-aac2
Or sudo apt install ffmpeg
Note libfdk-aac2 is in Debian's non-free and Ubuntu's multiverse sections: enable them first.
Distribution Fedora
Recommended sudo dnf install fdk-aac
Or sudo dnf install ffmpeg
Note Both from the RPM Fusion repositories (enable them first).
Distribution openSUSE
Recommended sudo zypper install libfdk-aac2
Or sudo zypper install ffmpeg
Note The full versions come from the Packman repository.
Distribution Arch, Manjaro
Recommended sudo pacman -S libfdk-aac
Or sudo pacman -S ffmpeg

After installing, close the radio screen and open it again (or wait a few seconds): qFT8 finds the decoder by itself.

↑ Back to Table of Contents

Digital radio on short and medium wave: DRM and DRM+ (experimental)

In the mode selector, SWL tab, choose DRM / DRM+. qFT8 tunes the frequency you were on last (the first time: 11690 kHz) and finds the DRM signal by itself: the robustness mode (A, B, C, D, or E for DRM+), the channel width, the tuning error and the clock error. Within a few seconds the station's services (up to four) join the list with their names, and the text messages the station sends show under the name. The grey line shows the frequency, the robustness mode (for example DRM-B) and the audio format and bit rate.

Using qFT8 for SWL (listening)

You do not need a licence or a transmitter to use qFT8. As a shortwave (and VHF/UHF) listener, SWL, you can receive and decode every mode qFT8 knows, see the stations you hear on the World Map, and keep a log of the QSOs you hear between other stations, ready to send as SWL reports. qFT8 is Amateur Radio and SWL: the same app, on the phone, the computer, the iPhone and in the web remote.

What you can receive and decode

An SDR never transmits in qFT8: while one is the receiver, the TX button reads NO TX / SDR and nothing can key. A receiver that tunes the radio (the marine VHF, airband and signals receivers) also stops transmitting while it has the radio: the button reads NO TX / RX and TX stays OFF afterwards until you press TX ON. With a radio that can transmit, switch on SWL mode and qFT8 will not transmit either.

Devices for listening

Choose the receiver in Settings > Device. The SDR rows have their own group in that list; under the row you pick, qFT8 shows the few settings that receiver needs and a status line (“Connecting to ...”, “Connected to ... (2.4 MS/s)”, or why it is not connected).

RTL-SDR dongle (RTL-SDR Blog V3, V4, V4 Lite and other dongles with an R820T / R820T2 / R828D tuner) plugged in by USB
Device row SDR: RTL-SDR (USB)
Frequencies 0.5 MHz - 1.7 GHz (HF on the V4 by itself; V3: direct sampling)
Phone yes (USB OTG)
Computer Linux
iPhone / iPad no
The same dongle on another computer or a Raspberry Pi, through its network server
Device row SDR: RTL-SDR (network)
Frequencies as above
Phone yes
Computer yes
iPhone / iPad yes
KiwiSDR web receiver, your own or a public one
Device row SDR: KiwiSDR (network)
Frequencies 10 kHz - 30 MHz
Phone yes
Computer yes
iPhone / iPad yes
Hermes-Lite 2, Red Pitaya, older ANAN (OpenHPSDR, received only; experimental)
Device row SDR: Hermes-Lite 2 / OpenHPSDR (network)
Frequencies 0 - 38 MHz
Phone yes
Computer yes
iPhone / iPad yes
Airspy (R2, Mini, HF+) or an RTL-SDR shared by a network server on port 5555
Device row SDR: Airspy / RTL-SDR server (network, port 5555)
Frequencies what the shared receiver covers
Phone yes
Computer yes
iPhone / iPad yes
SDRplay, LimeSDR, ADALM-Pluto, HackRF, Airspy, RTL-SDR ... shared by a remote SDR host server on port 55132
Device row SDR: remote SDR host (network: SDRplay, LimeSDR, Pluto ...)
Frequencies what the shared receiver covers
Phone yes
Computer yes
iPhone / iPad yes
Any SDR shared by SDR++ in server mode (port 5259; experimental)
Device row SDR: SDR++ server (network) (its sample rate and gain are set on the server; one client at a time)
Frequencies what the shared receiver covers
Phone yes
Computer yes
iPhone / iPad yes
Airspy HF+ plugged in by USB (experimental)
Device row SDR: Airspy HF+ (USB)
Frequencies what the receiver covers
Phone yes (USB OTG)
Computer Linux
iPhone / iPad no
Airspy R2 or Airspy Mini plugged in by USB (experimental)
Device row SDR: Airspy R2 / Mini (USB)
Frequencies what the receiver covers
Phone yes (USB OTG)
Computer Linux
iPhone / iPad no
HackRF plugged in by USB, received only (experimental)
Device row SDR: HackRF (USB, receive only)
Frequencies what the receiver covers
Phone yes (USB OTG)
Computer Linux
iPhone / iPad no
ADALM-Pluto, received only (experimental): empty address = the Pluto plugged into this device (192.168.2.1)
Device row SDR: ADALM-Pluto (USB network, receive only)
Frequencies what the receiver covers
Phone yes
Computer yes
iPhone / iPad yes, over the network
A stereo I/Q receiver on a sound input: SoftRock, FUNcube ... (experimental)
Device row SDR: sound-card I/Q (SoftRock, FUNcube ...)
Frequencies around the centre frequency you type in kHz
Phone yes
Computer yes
iPhone / iPad no
ANAN, Saturn, Orion and other radios of the OpenHPSDR protocol 2 (received only; experimental)
Device row SDR: OpenHPSDR protocol 2 (network: ANAN, Saturn, Orion ...)
Frequencies what the radio covers
Phone yes
Computer yes
iPhone / iPad yes
The I/Q of a radio or SDR program that serves TCI (experimental)
Device row SDR: TCI IQ stream (network)
Frequencies what the program covers
Phone yes
Computer yes
iPhone / iPad yes
An I/Q channel made on demand by a wideband receiver server on your own network, over multicast RTP (experimental)
Device row SDR: multicast RTP receiver (network, port 5006)
Frequencies what the server covers
Phone yes
Computer yes
iPhone / iPad no
A web receiver you own or one shared openly: an audio channel inside its band (experimental)
Device row SDR: web receiver, audio channel (network)
Frequencies what the receiver covers
Phone yes
Computer yes
iPhone / iPad yes
A wideband web receiver (port 9002): qFT8 takes its own audio window in the receiver's band (experimental)
Device row SDR: wideband web receiver (network)
Frequencies what the receiver covers
Phone yes
Computer yes
iPhone / iPad yes
Any of these served by a qFT8 bridge on another device
Device row the bridge
Frequencies as the bridge's receiver
Phone yes
Computer yes
iPhone / iPad yes
An ordinary radio (156 models over USB, or any radio by audio cable)
Device row the radio's row, or AUTO
Frequencies what the radio receives
Phone yes
Computer yes
iPhone / iPad by audio (see iPhone)

Not supported: sound-card I/Q receivers (a SoftRock, or the I/Q mode of the QMX+: use the QMX+ as a normal radio, it is plug and play over USB), and RTL dongles with other tuners (E4000, FC0012, FC0013, FC2580).

An RTL-SDR dongle on the phone or the computer

Phone or tablet (Android): plug the dongle in with a USB OTG adapter or cable. Android offers to open qFT8; allow the USB permission. With Settings > Device on AUTO and no radio plugged in, qFT8 uses the dongle by itself (“AUTO - SDR: RTL-SDR (USB)”); a radio plugged in as well wins. Unplugging and replugging the dongle picks it up again. The dongle draws power from the phone: a short cable and a charged battery help.

Nothing to install, on any dongle. qFT8 has its own driver for the dongle, built into the app: it recognises the RTL-SDR Blog V4 and uses its built-in HF upconverter and input switching, so HF works on the V4 without any setting. On a V3 (or another dongle without an upconverter) tick HF without an upconverter (direct sampling) to receive below 24 MHz on its HF input. qFT8 never switches the dongle's bias tee (antenna power) on.

Computer, Linux: the same row, the same built-in driver. qFT8 takes the dongle from the TV driver the system loads for it by itself. Your user needs permission to open the dongle; if the status line says “no permission”, add a rule file once (for example /etc/udev/rules.d/20-rtlsdr.rules) with the line SUBSYSTEM=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", MODE="0666" (2832 for some older dongles), run sudo udevadm control --reload-rules and plug the dongle in again.

Computer, Windows and macOS: the dongle cannot be opened by qFT8 directly yet. Run the RTL-SDR network server on the same computer (or on any other one, such as a Raspberry Pi) and choose SDR: RTL-SDR (network) with the address 127.0.0.1, or serve the dongle from a phone or a Linux computer with the qFT8 bridge.

The RTL-SDR network server and its driver

The network server (port 1234) comes with the RTL-SDR driver package of your system. That package is a driver of its own, separate from qFT8, and its version matters:

Settings for the network row: Address, Port, Sample rate (2.4 MS/s by default; if the status line says the data arrives in bursts, tap it to use the highest rate), Gain, Frequency correction (ppm) and HF without an upconverter (direct sampling) and, for a server that can switch it, Bias tee (power on the antenna input; RTL-SDR Blog V3/V4). Any server that speaks the same RTL-SDR network protocol works too, including those made for other SDRs.

Other SDRs

An ordinary radio

Any radio qFT8 supports is also a fine receiver: plug it in as described in Quick Setup (a QMX, QMX+ or IC-7300, for example, with one USB cable). qFT8 sets its frequency over CAT when you press a band button. Switch on SWL mode so that it never transmits.

Bias tee

The device setup of an SDR whose driver can switch it (the RTL-SDR on this device's USB, RTL-SDR Blog V3 / V4, and an RTL-SDR network server) has the check box Bias tee (power on the antenna input; RTL-SDR Blog V3/V4), off by default (most other dongles have no bias tee). It puts DC voltage (about 4.5 V) on the antenna connector, for an LNA, a converter or another device made to be powered over the coax. Turning it on first shows a red warning that it can damage the SDR, the antenna or anything connected (a radio, a filter, a splitter, a DC-shorted antenna); type yes in its field, then TURN ON (CANCEL leaves it off). The web remote can only switch it off. qFT8 never switches it on by itself and switches it off whenever the SDR is closed.

SWL mode and the heard log

SWL MODE (LISTEN ONLY), at the end of Settings > Events, asks your SWL identifier (for example R4-123-456) or your callsign. While it is on, qFT8 never transmits (the TX button reads NO TX / SWL; TX, TUNE and every mode refuse to key), and your own QSO log is not touched. The details are in Events supported.

The heard log collects the QSOs you hear between two other stations:

Exports: ADIF, CSV, SOTA and RAZA SWL

The SWL log in Settings, and eQSL

Step by step

  1. Get a receiver: an RTL-SDR Blog V4 with its antenna is the simplest start (HF to UHF, no driver needed on a phone or Linux); with no hardware at all, use a public KiwiSDR.
  2. Choose it in Settings > Device (or plug the dongle in with Device on AUTO) and wait for “Connected” in its status line.
  3. Pick a mode and a band: FT8 on 20 m or 40 m is busy at almost any time and fills the map in a minute.
  4. Switch on SWL MODE (LISTEN ONLY) if you want your SWL identifier in the exports (with a radio that can transmit, also to keep TX off).
  5. Export the heard log when you want to send reports.

Phone: USB dongle or any network receiver. Computer: the USB dongle on Linux, network receivers everywhere. iPhone / iPad: network receivers, or a receiver served by a qFT8 bridge (the iPhone has no USB host for a dongle). Web remote: shows the receiver's NO TX / SDR state and the SWL log.

Awards (experimental)

qFT8 makes a diploma itself from your own logs: there is nothing to apply for. At the very top of Settings, tap the QSO button (with the Ham features on) or the SWL button (with SWL on) to open its page, HAM awards or SWL awards; each button shows a star and the stars you have earned. Settings > Features > Awards turns them off (nothing is lost).

qFT8 Camera The HAM awards page: the share button above the diploma; a tap on the diploma opens it full screen.
qFT8 Camera The diploma full screen, with its exit and share buttons at the top-right corner.

Starting without a callsign

The callsign card of the first start has a SWL ONLY button and the line “No callsign? Press SWL ONLY to receive.” It asks for an optional SWL id (one button, CONTINUE; an empty box means “SWL”) and warns when neither a callsign nor a locator is set (Settings > Time and location warns the same, and on the computer PICK ON MAP picks your locator on a world map). The welcome then says “You didn't enter a callsign, but I can guide you through the SWL features of qFT8.” and START TUTORIAL runs a short SWL tutorial. Without a callsign only the SWL features are on and the TX button reads NO CALLSIGN; to transmit, press it and then SET UP. The first time the callsign card is answered with SWL ONLY, the mode selector's experimental check box is switched on too, so the receivers are listed at once; after a first start with a callsign it stays off.

Weather fax

The weather-fax row receives the HF radiofax charts of the met and naval services through any HF radio in USB, or an SDR. Its frequency button steps through the broadcasts of the public worldwide radiofax schedule (70 frequencies, with their broadcast hours), skipping the ones that are off the air at this hour (UTC); the radio is tuned 1.9 kHz below the listed frequency. The speed (60, 90, 120 or 240 lines a minute) is found from the chart's phasing lines, and a chart that is already on the air starts by itself after a few lines; a picture ends at the stop signal, or by itself when the chart turns into noise. Receive only.

Every picture the weather-fax, weather-satellite (APT, Meteor LRPT) and balloon (SSDV) receivers end is saved at once, without asking, in the same folder as the SSTV pictures: on the phone the gallery's Pictures/qFT8 SSTV, on the computer qFT8 SSTV in your Pictures folder, on the iPhone the app's qFT8 SSTV folder and Photos. Its name says what it is, in UTC: WEFAX_20261108_1530Z_7880kHz_DDK3.png (receiver, date, time, frequency, station); a picture cut short because you stopped the receiver ends in _partial. The line under the picture says where it went; SHARE (phone, iPhone) hands it to another app, OPEN FOLDER (computer) shows it in its folder and DOWNLOAD (web remote) saves a copy on the device the browser runs on. The picture is saved as received, not as the NEGATIVE view shows it.

Digital voice data over the internet

The DMR, D-STAR, Fusion and M17 data rows can also listen over the internet (their last choice): who talks, to which talkgroup or reflector, their text and position, from the BrandMeister activity feed and the open reflectors (XLX, XRF, DCS, YSF, M17). Data only and receive only: qFT8 never transmits into a network, never bridges two of them and never plays DMR, D-STAR or Fusion voice. The reflectors see you as a listener under your own callsign. When the network drops, a channel links again by itself within about 15 seconds. Experimental.

↑ Back to Table of Contents

What shows on the map

When qFT8 receives a signal that carries a position, it draws the sender on the World Map as it is heard, moves it as new reports come in, and lets it fade out when nothing more is heard. Each kind has its own small drawing in the map's colour:

They are shown with the map's SPOT button: when it is on you see them together with the other spots, and when it is off they are hidden. Each card also says when the sender was last heard, on which frequency, and how far away it is from you. Stations and balloons stay on the map for up to an hour, getting fainter as their last report gets older.

↑ Back to Table of Contents

Feature documentation

Settings and tools that are not tied to one mode: two per-radio settings of DEVICE CONFIGURATION, the web page to operate qFT8 from another device, the bridge that lets you leave the radio in another room, and the arrangement of the screen.

Tune spectrogram offset

In Settings > DEVICE CONFIGURATION, under Tuning (this radio), Tune spectrogram offset shifts what the spectrogram shows by up to 300 Hz down or up. Its default is 0 Hz; a value you set is kept, separately for each radio.

What it is for: most radios have a blind spot at the very bottom of the audio, about 0–50 Hz (0–90 Hz on Icom radios), so the lowest part of the spectrogram stays empty. With an offset of −50 Hz (−90 Hz on an Icom), qFT8 tunes the radio that much lower and shifts the audio back by the same amount: the app shows what it should, and you gain 50 or 90 Hz of extra spectrogram.

Nothing else changes: the frequency shown, the stations' offsets, the spots, your transmit frequency and the log stay the same. Only the radio's own display reads lower by the amount of the offset. The offset works in every mode and needs a CAT connection; with VOX or the speaker it does nothing.

Continuous transmission limit

This is a safety setting for the transmitter. Small radios are built for short transmissions with pauses: an FT8 transmission lasts under 13 seconds and is followed by at least 15 seconds of rest. Some modes key the radio at full power for far longer without a break, and that can overheat the final amplifier of a small radio. The continuous transmission limit is the longest time qFT8 keys your radio in one go.

It is in Settings > DEVICE CONFIGURATION, under Tuning (this radio). The choices are 20, 40, 60, 90, 120 and 150 seconds, and No limit. Under each choice qFT8 lists what that choice adds, so you can see what you gain by raising it. The setting is kept separately for each radio.

The default for each radio

  • 60 seconds: QRPLabs QMX, QMX+ and QDX, and the (tr)uSDX.
  • 120 seconds: Xiegu X6100 and X6200.
  • No limit: every other radio, and a radio used through VOX or the speaker (qFT8 cannot know which radio that is).

These defaults are cautious. You know your radio, its power setting and its cooling: change the limit if they allow it. qFT8 never raises the limit by itself.

What the limit does

  • A transmission with a known length that is longer than the limit is not started. This is why WSPR and the long SSTV modes ask you to raise it: a WSPR transmission lasts 111 seconds, and many SSTV pictures take two minutes or more. When you choose such a mode, or press TX ON in it, a message tells you how many seconds it needs and what the limit of your radio is, with a button Open the setting. Transmission is not armed until the limit allows the mode.
  • A transmission without a fixed length stops when the limit is reached, and the radio goes back to receive: TUNE, SSB (the PTT button, VOX and voice memories) and RTTY. A notice says that the limit was reached.
  • CW is not limited: a key is down only part of the time.

QMX and WSPR: With a QMX, QMX+ or QDX, WSPR needs the limit raised from 60 to 120 seconds. For the radio's safety qFT8 asks you to do it once, by hand. Consider lowering the power of the radio for WSPR: it is a low-power mode by design.

Remote Control Web Server

qFT8 includes an embedded HTTP server that allows you to monitor and control the application from any web browser on your network. This is particularly useful for remote operation or as a secondary display.

The first time the web remote starts on Windows, Windows asks whether to allow the Java runtime (shown as "OpenJDK Platform binary") through the firewall. Allow it on a private network so that other devices can reach the page.

The page looks and works like the app itself and fills the browser window at any size. In a wide window the spectrogram is on the left and the selected pane on the right; in a tall one, such as a phone held upright, the spectrogram is on top. The bar at the bottom has the same controls as the app's: the TX button, the message, the sequence, the mode and the band, and the buttons for the stations, the QSO log, the world map and the settings. The waterfall moves live, with the same labels as in the app. This is the stations view in a tall window:

Remote Control Web Server Stations

It allows operating with the AUTO button, criteria dropdown, + button to directly add callsigns, and the list of stations with CALL buttons to manually call them. The small light at the right end of the bar is green while the page is connected to qFT8.

And this is the QSO log view:

Remote Control Web Server Log

This view shows the most recent log entries. The other two buttons open:

  • The world map, as in the app. Its full-screen button gives the map the whole window; the same button or Esc brings the panes back.
  • The page's settings (the gear): your callsign, locator and CQ modifier as the app has them (shown, not changed from the page), the time offset in steps of 100 ms, how often the app sends the waterfall, and Quadrants, which shows the spectrogram, the stations, the world map and the QSO log all at once. Quadrants is remembered by each browser. Keep the screen on keeps the phone's or tablet's screen from turning off while the page is shown (browsers allow it only on the page's secure address, https).

Two browsers can be open on the same qFT8 at once; what you do on one shows on the other within a second. A feature that is switched off in the app (see Screen layouts) is hidden on the page too. The page loads nothing from the internet: everything comes from qFT8.

While the page plays the radio's audio (Listen, or Always play the radio's audio), it keeps receiving it when the browser is in the background or the screen turns off; the waterfall pauses meanwhile and catches up when you come back. Whether a browser keeps a page running with the screen off is the browser's choice: Chrome on Android does. Where a browser stops pages with the screen off, use Keep the screen on.

Network & Connectivity

The server opens a specific TCP port (default 13497) on your phone or computer. To access it, your devices must be able to "see" each other on the network:

  • Local Network: Both the phone or computer running qFT8 and your control device (computer, tablet, or phone) must be on the same network.
  • Router Settings: Some routers have a feature called AP Isolation (or Client Isolation) enabled by default. This must be disabled for devices to communicate with each other.
  • Mobile Hotspot Scenario: If you are in the field, you can open a Wi-Fi hotspot on one phone (with internet) and connect the qFT8 phone to that Wi-Fi network. After connecting, close and reopen the web server in qFT8 settings; the IP address shown will then be accessible from the hotspot-providing phone.
  • Internet Access: Accessing the server from outside your home (over the internet) requires Port Forwarding in your router settings (mapping the internal IP and port to an external one). Note that this generally will not work over 5G/LTE connections due to carrier NAT restrictions.

Access Levels

You can configure the remote security level in the settings pane:

  • Read only: Allows viewing the live spectrogram, active stations, and the QSO log. No actions can be performed.
  • Read + Stop TX: Primarily a safety mode. Allows viewing all data and permits disarming the transmitter (stopping TX) in case of an emergency, but does not allow starting TX or changing settings.
  • Full control: Grants complete authority over the application, enabling all interactive features.

Security Note: Anyone with access to your network, IP address, and port will have the level of control you have configured. If set to Full control, they could potentially start transmitting using your station.

Capabilities

In Full control mode, the web interface offers nearly everything the app UI does:

  • Operation Modes: Toggle between AUTO and manual CALL modes.
  • Strategy: Change the AUTO criteria (Anyone, DXCC, Grid, etc.) and search constraints.
  • Transmission: Manually start/stop TX, choose specific TX messages, and change the FT8 sequence (0/1).
  • Frequency & Band: Tap the web spectrogram to move your frequency offset or change the active radio band.

SSB, CW, RTTY and SSTV are operated in qFT8 itself. While the app is in one of them, the web page shows the waterfall and whether the app is transmitting, and does not transmit; choose a digital mode on the page to work from it again.

The radio's continuous transmission limit holds for the page exactly as for the app. When it keeps TX off (for example WSPR with a limit of 60 seconds) or stops TUNE, the page shows a notice for a few seconds that says why, so you are not left wondering in front of a button that does nothing. The limit itself is only changed in the app.

Remote Control Web Server: why TX stayed off

Note: The web UI is designed to remain responsive even if the phone's screen becomes sluggish due to RF interference, providing a reliable fallback for control.

Note: The web server will function when the screen is off if the settings to run in background are enabled (the default is to keep running in the background when qFT8 is connected to a transceiver).

qFT8 bridge

The qFT8 bridge lets you leave the radio in one place and operate from another. A device beside the radio, the bridge, passes the radio's commands and its audio over your own network to qFT8 on another device. That qFT8 does everything else: it decodes, logs and decides what to send. For it, the radio works as if it were plugged in by USB.

Use it when the radio sits near the antenna, in the attic, the garage or the garden shed, and you want to operate from somewhere more comfortable; or when the device beside the radio should only look after the radio: a small computer such as a Raspberry Pi, or an old phone or tablet.

This is not the same as the Remote Control Web Server. There, qFT8 runs beside the radio and you look at it from a browser. With the bridge, qFT8 runs on the device in front of you and only the radio is somewhere else.

What you need

  • A device beside the radio, with the radio connected to it by USB as usual: a computer with Windows, macOS or Linux (a Raspberry Pi is enough), or an Android phone or tablet. This one is the bridge.
  • qFT8 on the device you operate from: the computer program or the Android app. Any of them can use any bridge: a phone can operate a radio beside a computer, a computer a radio beside a phone, and so on.
  • Both on the same local network. A network cable works as well as Wi-Fi and is steadier; if you can, give at least the bridge a cable. A phone or tablet uses its Wi-Fi, never its mobile data.
  • The bridge's password. The bridge makes one and shows it to you.

Setting up the bridge

There are two ways to run a bridge. Pick one.

1. From qFT8's Settings (the computer program or the Android app). On the device beside the radio, open Settings > qFT8 BRIDGE and tick Run as a qFT8 bridge on port. Leave the port as it is unless another program uses it.

The qFT8 bridge section of the settings

Password shows the password the other device will need. NEW PASSWORD makes another one; touch the password itself to type your own (7 characters or more).

While it is a bridge, qFT8 on that device does nothing else. TX is switched off, its own use of the radio stops, and the screen shows only qFT8 running in bridge mode, with the Address and the Password to enter on the other device and who is using the radio (Nobody is connected, or the device's name). On Android the bridge keeps running with the screen off, shown by a notification; keep the phone or tablet on its charger.

qFT8 running in bridge mode

TURN BRIDGE MODE OFF asks first, because the other device loses the radio at once, and then brings qFT8 back as it was, with TX still off. If you close qFT8 while it is a bridge, it starts as a bridge again next time.

2. From the command line (computers only). For a computer that has no other job, also a Raspberry Pi or a server without a screen: start qFT8 with --bridge. It then runs only as a bridge, with no window, and loads nothing else of qFT8 (no settings, no decoding), so it needs very little memory. Use the qFT8 you downloaded for that computer, from a terminal:

  • Windows: open a Command Prompt in the qFT8 folder and type qFT8.exe --bridge --tx-volume 70. If Windows asks whether to allow "OpenJDK Platform binary" on your networks, allow it.
  • macOS: in Terminal, type /Applications/qFT8.app/Contents/MacOS/qFT8 --bridge --tx-volume 70. The first time, macOS asks for the microphone: allow it, that is how the radio's audio is read.
  • Linux: in the qFT8 folder, type ./qFT8 --bridge --tx-volume 70.
  • Any computer with Java 21 or newer, for example a Raspberry Pi with the Java of its system: the qFT8 .jar download runs on every system. Type java -jar, the name of the .jar file, and --bridge. It carries what it needs to use serial ports on Windows, macOS and Linux (PCs and ARM boards, 32 and 64 bits).

The terminal shows the password at the first start and keeps it for the next ones. Leave the terminal open: the bridge runs as long as it does. Ctrl+C, or closing the terminal, stops it and puts the radio back to receive.

Options you may want, added after --bridge:

  • --tx-volume N: required: the audio level, 1 to 100 %, the bridge sets on the radio's sound device for transmitting, as qFT8's own TX volume setting (70 is its default; QRP Labs radios: 100). It is the sound level only: the radio's power is never changed.
  • --password TEXT: your own password instead of the one it made.
  • --show-password: show the kept password again.
  • --new-password: make a new one.
  • --name TEXT: the name other devices see in their list (it is "qFT8 bridge" otherwise), useful with more than one bridge.
  • --only TEXT: share only the radio's serial port and sound device, named by a part of their name (for example --only QMX); nothing else of the computer is offered.

--bridge --help lists the rest.

Connecting from qFT8

On the device you operate from, open Settings > DEVICE CONFIGURATION and, in Radio connection at the very top, choose qFT8 bridge. These rows appear right under it:

  • Method: qFT8 bridge.
  • Bridge: opens the list of the bridges qFT8 finds on your network. Pick yours. Search again looks once more. If yours is not listed, choose Type address and enter the address the bridge shows.
  • Password: the one the bridge shows.
  • CONNECT: the box beside it turns green and reads Connected to followed by the bridge's name.
  • Radio port on the bridge, Sound device on the bridge (receive) and Sound device on the bridge (transmit): what the radio is plugged into on the bridge's side. AUTO finds them; choose by hand only when the bridge has several. A radio reached through its own program on the bridge computer (a virtual serial port and a virtual audio cable) has a port AUTO cannot recognise: choose the port by hand, and check that both sound devices are the cable's.
Choosing a bridge found on the network
Device configuration connected to a qFT8 bridge

From here on everything is as with a USB radio: qFT8 recognises the radio, reads its frequency, receives and transmits. qFT8 remembers the bridge and its password, and a settings export carries them to your other devices. While the box is ticked, a radio plugged into the device you operate from is not used. To go back to it, choose Direct (USB / cable) in Radio connection; no restart is needed.

On a phone or tablet the status box reads No Wi-Fi. Connect this device to the bridge's network. when it is not on a Wi-Fi network: the bridge is only looked for there.

The link display

Under the bridge's devices, one line tells you how the link is doing, for example Delay 120 ms, adjusted by itself. Link: steady (jitter 3.0 ms).

  • Delay: a network never delivers sound perfectly evenly, so the audio is held for a moment before it is played, to iron that out. There is nothing to set: qFT8 and the bridge choose the delay themselves, raise it when audio arrives late and lower it again once the link has been clean for a while. It does not disturb the timing of the digital modes: your transmissions still start on time, and what you receive is placed by the moment the radio heard it.
  • Link: steady: all is well.
  • Link: irregular: audio is arriving unevenly. The delay takes care of it; there is nothing to do unless it stays like this.
  • In red, The link to the bridge is losing transmit audio: part of a transmission did not reach the radio in time. The delay is raised at once; if this keeps happening, see Troubleshooting.
  • In red, The link to the bridge cannot keep up: even the largest delay is not enough and transmit audio breaks up. See Troubleshooting.

Right after connecting the line reads Nothing measured yet.

Transmit safety

  • Only you switch TX on, with the TX button of the qFT8 in front of you. The bridge never starts a transmission by itself.
  • If the link drops (the Wi-Fi goes away, the device sleeps, qFT8 is closed), the bridge puts the radio back to receive by itself, within a second or two. qFT8 stops what it was sending, switches TX off and shows a red card that says why, such as Connection lost. Connecting again... It reconnects by itself. If the link is back within 10 seconds and you had TX on, qFT8 switches it on again once, as you had it; after a longer drop it stays off until you press it again.
  • The continuous transmission limit of your radio is kept by the bridge as well.
  • Stopping the bridge, either way, also puts the radio back to receive.

Security Note: The password protects control of your radio: nobody without it can use the bridge, and the password itself is never sent over the network. It does not make the link private: the audio and the radio's commands are not encrypted. Use the bridge inside your own network only, and do not open it to the internet.

Limits

  • Local network only. The bridge is not made to be reached over the internet. A VPN that sends your home network's traffic through its tunnel hides the bridge too: turn it off, or allow local network access in it, on both devices.
  • One device at a time. When a second device connects, it takes over; the first one reads Another device took over the bridge. Press CONNECT to take it back.
  • Every mode works through a bridge, receiving and transmitting: FT8, FT4, FT2, JS8, WSPR, LQ8, SSB, CW, RTTY, SSTV and TUNE. Your loudspeaker and microphone stay on the device in front of you; only the radio's audio crosses the network.
  • A radio that is switched to transmit by a control line (RTS or DTR) instead of a command is keyed through the bridge too.

qFT8log

qFT8log keeps the logs of several qFT8s together over your own network. One qFT8 is the qFT8log server; the others send it every QSO they make. The server adds them to its own log (the QSO list, the map, the statistics) and sends them on to the services set up on it, such as QRZ and LoTW. What happens to a QSO later, a confirmation or a correction, comes back to the qFT8 that made it while the two are connected.

Any qFT8 can be a server and a client at the same time: the computer program, the Android app and the iPhone app. On Android the server keeps running in the background when Run in background is on; on the iPhone it runs only while the app is open.

Setting up the server

  1. On the qFT8 that should collect the QSOs, open Settings, go to More settings > SERVERS and open the gear of qFT8log server.
  2. Type a password. Use the same kind of password as for the qFT8 bridge: seven characters or more.
  3. Leave the port at 13510 unless something else uses it, and switch the server on. The page shows the server's address and the qFT8s connected to it. A changed port takes effect at once.
  4. The same address opened in a browser (for example http://192.168.1.20:13510/) shows the log, read only, after you type the server's password (it is never sent): see Looking at the log in a browser.

Setting up a client

  1. On each qFT8 that should send its QSOs, open Settings, press the gear beside qFT8log at the top.
  2. Press FIND: the qFT8log servers on your network are listed by name. Pick one, or type the server's address and port yourself.
  3. Type the server's password and press VALIDATE. When the server accepts it, tick qFT8log at the top of Settings.

From then on the client connects by itself whenever it starts and reconnects by itself when the network or the server comes back. QSOs made while the server is not reachable wait in the log (they show as not uploaded to qFT8log) and are sent as soon as the connection is back, also after a restart. When the client cannot reach the server, the qFT8log row in Settings turns red with Couldn't connect as of and the time.

Consider a QSO uploaded if uploaded here is off for qFT8log by default. Tick it when the server is the place your QSOs go to, so the "waiting for upload" mark of a QSO clears once the server has it.

What travels

  • New QSOs, from the client to the server, with every field qFT8 keeps: the reports, grids, parks and summits, gear, comments, and whether the QSO was already uploaded to or confirmed by QRZ, LoTW or another service (a QSO imported from LoTW stays confirmed).
  • Confirmations, both ways, as soon as they arrive: a confirmation the server receives from LoTW shows on the client that made the QSO, and the other way round.
  • Corrections made in the QSO editor, both ways. When the same QSO was changed on both sides, the later change wins.
  • Deletes never travel. Deleting a QSO deletes it on that qFT8 only; the others keep theirs. Each qFT8 remembers the QSOs deleted on it and never takes them back from another qFT8, neither by an import nor by the live sync.

The server takes QSOs of every mode and every callsign: it is the place where you collect, and the log's filters choose what you see. A QSO the server already has (the same call, time, band and mode) is merged into the one it has, never added twice, and not sent on again.

Importing from the server, and live sync

A client sends only its own QSOs. Two ways bring the server's log to it as well:

  • IMPORT QSOs FROM THE SERVER, on the client's qFT8log page, copies once every QSO of the server inside From, To, Bands and Callsign starts with, of every mode. QSOs made under another callsign than yours are skipped unless Import QSOs for callsigns other than the current is ticked. It also works when qFT8log is not ticked at the top of Settings: the import then connects only for itself and sends nothing.
  • Keep in sync live with this server (it needs qFT8log ticked at the top of Settings): the server's QSOs come here, and from then on every QSO logged, corrected or confirmed on the server, or on any other qFT8 connected to it, appears here at once, and yours go there. Several qFT8s with this box ticked share one log through their server, and with chains, through every server of the chain.
  • When the connection drops, nothing is lost: each side catches up when it is back, also after a restart.
  • Correction times follow the server's clock, so a device whose clock is wrong does not win, or lose, every correction.

Chains: collecting and backing up

A server can itself be the client of another server, so qFT8s can be chained. A QSO is never sent back to a qFT8 it already passed through, so even a ring of qFT8s does not loop. Two examples:

  • One place that uploads. The phones and the portable computer send to the shack computer. Only the shack computer has QRZ and LoTW set up: it uploads everything, and the confirmations it receives go back to the qFT8 that made each QSO.
  • A backup. The shack computer also sends everything to another qFT8, say an old tablet that only keeps the log and shows the world map. Nothing has to be set up on the backup but its server.

Security Note: the password is never sent over the network: both qFT8s prove they know it, and every message after that is signed, so nothing can be changed or replayed on the way. With Encrypt qFT8 log connections on (the default, on the client and the server alike) the QSOs are also encrypted, so nobody else on the network can read them. Use qFT8log inside your own network only, and do not open its port to the internet.

Limits

  • Home network only, the same as the qFT8 bridge.
  • Both qFT8s must run the same qFT8log version. A server refuses a client of another version, and the client's row says which one to update.
  • At most 16 clients at a time per server.
  • A QSO the server cannot read (for example one without a date) is marked as refused on the client and sent again only after you correct it.

qFT8log protocol (version 2)

This is the complete description of what two qFT8s say to each other. Every number is big-endian. Text is UTF-8.

Finding servers

A client sends one UDP datagram to the broadcast addresses of its networks, port 13510: "qFT8L?" (6 bytes), the API version (2 bytes), a random id (8 bytes). Every server answers to the sender: "qFT8L!", its API version (2), the same id (8), its TCP port (2), its instance id (16 ASCII hex digits), the length of its name (1) and its name (at most 64 bytes). The answer says nothing secret.

Frames

Over TCP (port 13510 by default) everything travels in frames: the type (1 byte), the length of the body (3 bytes) and the body (at most 16384 bytes). The first four types travel before the keys exist; every other frame's body is sealed: an 8-byte counter, the message, and the first 16 bytes of HMAC-SHA256 (key of the direction) over the type, the counter and the message. Each direction counts from 0 and a frame must carry exactly the next number: a frame that was changed, repeated or left out ends the connection.

Type 0x01
Name HELLO (client)
Body "QFT8LOG1", API version (2), client random (32), client instance id (16 ASCII), name length (1), name
Type 0x02
Name CHALLENGE (server)
Body API version (2), server random (32), salt (16), rounds (4), server instance id (16 ASCII), name length (1), name, server proof (32)
Type 0x03
Name AUTH (client)
Body client proof (32)
Type 0x04
Name REFUSED (server)
Body reason (1): 1 other API version, 2 wrong password, 3 wait (too many wrong passwords), 4 busy, 5 not a HELLO, 6 the server's own instance; wait in ms (4); the server's API version (2)
Type 0x10
Name WELCOME (server, sealed)
Body API version (2), server time in ms (8): the client stamps its corrections on this clock
Type 0x11 / 0x12
Name PING / PONG
Body empty
Type 0x13
Name BYE
Body reason (1): 1 closing, 2 protocol error, 3 nothing heard, 4 too many; text length (1), text
Type 0x20
Name PUT
Body message number (4), the QSO record (the rest: a JSON object)
Type 0x21
Name ACK
Body message number (4), result (1): 0 same, 1 new, 2 merged, 3 skipped; the receiver's hash of the QSO (16 ASCII hex digits); the receiver's record when it differs from the one received (the rest, else nothing)
Type 0x22
Name NACK
Body message number (4), reason (1): 1 not a QSO record, 2 slow down, 3 internal error; text length (1), text
Type 0x23
Name SUBSCRIBE (client)
Body a JSON object: mode (once, live or off), from and to (YYYYMMDD, empty = no limit), bands (a list), call (the start of the callsign), station (the station callsign, empty = any)
Type 0x24
Name BACKLOG_DONE (server)
Body QSOs sent (4), new there (4), merged there (4): every QSO the subscription asked for went

The handshake

Both sides know k = PBKDF2-HMAC-SHA256(password, salt, rounds), 32 bytes. The server chooses the salt and the rounds (200000; a client refuses fewer than 10000 or more than 5000000). The transcript t is the HELLO body followed by the CHALLENGE body without its proof. With L = the ASCII text "qFT8 log v1 ":

  • server proof = HMAC-SHA256(k, L + "server proof" + t); client proof = HMAC-SHA256(k, L + "client proof" + t);
  • key client to server = HMAC-SHA256(k, L + "key client>server" + t); key server to client = HMAC-SHA256(k, L + "key server>client" + t).

The client checks the server's proof first and closes without answering when it is wrong, so nothing derived from the password ever goes to a server that does not know it. The server checks the client's proof; a wrong one locks that address out for 1 s, doubling with each wrong try in a row up to 60 s. Both randoms are new for every connection, so a recorded handshake is worth nothing. The API versions must be equal: a server refuses any other with reason 1, and a client refuses a CHALLENGE of another version. A server allows 8 handshakes at a time, 5 s for each step, and 16 clients; a client that connects again takes over from its old connection.

Records

A QSO record is a JSON object with the field names qFT8 stores (call, qso_date as YYYYMMDD, time_on as HHMM or HHMMSS, band, mode, submode, rst_sent, rst_rcvd, gridsquare, freq, station_callsign, my_gridsquare, comment, the park and summit references, the QRZ and LoTW states app_qrzlog_logid, app_qrzlog_status, app_lotw_qsl_rcvd, app_lotw_logid, app_lotw_upload_time, and app_svc), at most 16000 bytes. call, qso_date and time_on are required; any mode and any callsign are accepted. app_svc holds the other services' states and three records of the protocol itself, as id:key=value,... parts separated by ;:

  • q8u: id = the QSO's uid (made once by the qFT8 that first sent it, kept through every correction), t = when its contents were last corrected (UTC ms, missing = never);
  • q8v: id = the instance ids the QSO passed through, separated by dots (at most 32);
  • a sender leaves out its own bookkeeping: its per-peer hashes, its own upload state and its local work flags.

Hash and merge

The hash of a QSO is the first 8 bytes of SHA-256, as 16 hex digits, over the lines name=value of its contents, its correction time and its upload and confirmation states (not the instances it passed through). Two copies of one QSO become one the same way everywhere: the contents of the copy corrected later win as a whole (equal times: the larger contents hash); the upload and confirmation states only move forward (a confirmation is never undone); the instances are the union of both. Merging is the same whatever the order and merging twice changes nothing, so all copies end the same.

Who sends what

  • A client sends its server every QSO that has not passed through that server yet, and every QSO the two exchanged before whose hash has changed since.
  • A server sends a client the QSOs the two exchanged before whose hash has changed (a confirmation, a correction). After a SUBSCRIBE it also sends that client every QSO of its log inside the subscription that the two never exchanged and that did not pass through the client, then BACKLOG_DONE. With live it goes on doing so for every QSO it gets later, for as long as the connection lasts (the client subscribes again after each reconnect); once ends with BACKLOG_DONE; off ends the subscription.
  • The receiver finds its copy by the uid, else by call, date, time (HHMM), band and mode. A server adds a QSO it does not have; a client adds one only inside the subscription it sent. Neither adds a QSO deleted on it (result 3 in both cases). Otherwise the copies are merged; the ACK carries the receiver's hash and, when the merged copy differs from what was sent, the merged record, which the sender merges in turn.
  • Each side remembers, per QSO and per peer, the hash both last agreed on, and sends again only when its own copy differs from it. Deletes are never sent.
  • At most 16 PUTs may wait for their answer. A server takes 100 PUTs per second from each client (bursts of 200) and answers NACK 2 above that; after 50 records it cannot read it ends the connection.
  • A side sends PING when it has sent nothing for 15 s and ends the connection when it has heard nothing for 45 s. A client reconnects 1 s, 2 s, 4 s ... up to 60 s apart.

Screen layouts

The screenshots in this manual show the default layout: landscape, with the spectrogram on the left. In the Android app, Settings > APPLICATION > User interface lets you change it (the computer program has none of these settings: it has its own layouts, see The screen layouts and the layout button):

  • Orientation: Landscape, Portrait, or Follow the phone. In portrait the spectrogram is on top, the tab below it, and on a phone the bottom bar takes two rows.
  • The divider: drag the thin line between the spectrogram and the tab to give one of them more room. Each orientation remembers its own position.
  • Quadrants (tablets): the spectrogram, the stations, the world map and the QSO log all at once, with Settings opening at the right.
  • Features: Ham features (callsign, transmitting, the QSO log, syncing and events), SWL features (listening: the SWL tab, the SWL log and your SWL id) and Awards can each be turned off if you do not use them. On the phone Radio features, QSO log and World map can be turned off too; while one is off, an ENABLE button for it shows in Settings. Turning the Ham or radio features off also switches TX off.
  • App covers: lets qFT8 draw over the navigation bar, the camera area and the status bar, for a little more room.
↑ Back to Table of Contents

Bug reports and new versions

Reporting a problem

REPORT BUG, at the bottom of the Settings tab, opens a card where you describe what went wrong and, if you want an answer, leave your e-mail. Pressing SEND sends your description together with the app's log: settings, radio and audio details, and recent activity. Passwords, API keys, certificates and the logins of your QSO services are never included. You get a reference such as QFT8-7K3P9 to quote later. If the report server cannot be reached, qFT8 offers to send the report by e-mail instead.

"Send a report about this?"

When qFT8 notices that it stopped responding for a moment, or that decoding is taking too long on your device, it may show a small card that offers to send a report about it, with SEND, DON'T SEND and DON'T ASK AGAIN. Nothing is ever sent without your tap. The card appears at most once a day, and DON'T ASK AGAIN silences it until the next version. It also appears when the spectrogram keeps having trouble for minutes (it looks slow, pauses or skips), with a plain question whether to send a report; a healthy slow device never sees it. When your radio is reached through a qFT8 bridge, a report also carries the bridge's own log, fetched over the bridge link. After a crash, qFT8 asks at the next start whether to send a crash report.

Check for new versions on startup

With this box ticked (main Settings page, near the bottom) qFT8 looks for a newer version when it starts and shows a notice with a download button when there is one. It never updates by itself.

Anonymous performance summary

Send an anonymous daily performance summary (main Settings page, near the bottom, under Check for new versions on startup) is off unless you turn it on. When on, about once a day qFT8 sends a short summary of how fast it runs on your device: start-up time, screen smoothness, decoding times, audio and radio timing, and the device model and screen. It never contains your callsign, grid, log, settings or anything that identifies you. It helps make qFT8 faster on devices like yours.

After every 10 hours of use with it off, qFT8 may ask once, when it opens: Enable profiling reports? ENABLE ticks the box; NO THANKS leaves it off and qFT8 never asks again; closing the question without an answer asks again 10 hours later. Test versions do not ask, and qFT8 never asks while transmitting.

↑ Back to Table of Contents

Troubleshooting

On the computer (and with a phone's USB radio), a radio cable or USB-serial adapter that stops answering no longer freezes qFT8. When the port has not finished a command for 4 seconds the program shows radio link lost, TX goes OFF, new commands are dropped instead of piling up, and qFT8 reopens the port by itself a few times and again when the adapter is plugged back in. TX OFF always goes ahead of everything else waiting for the radio. Check the cable and the adapter, plug it in again, and press TX ON when the link is back: qFT8 never switches TX on by itself.

The phone or computer doesn't recognize the transceiver or it gets disconnected

This is almost always a hardware connectivity or radio interference issue. USB connections are sensitive to vibration, cable quality, and fluff phone raccoons dwelling in the USB port. On Android, another common cause is that USB OTG may be disabled by default in your device (in particular if you are able to receive signal from qFT8 but not transmit and CAT commands don't work even when the device is fully supported, shown in the device dropdown, autorecognized in AUTO mode, etc., this is very likely the cause).

Try:

The transceiver disappears when the phone is fully charged (Android)

This happens with USB OTG adapters that have a charging input, so that the phone can be charged while the transceiver is connected. With some of them, when the battery reaches 100% the phone stops the USB connection to the transceiver, and it stays away until the charger is unplugged. qFT8 then shows the transceiver as disconnected and nothing works: no audio, no CAT.

Try: Unplugging the charger from the adapter (the transceiver comes back), operating without charging, or using a different adapter or powered hub.

qFT8 bridge: "No bridge found on this network"

qFT8 asked the network and no bridge answered. The usual causes are that the bridge is not running, that the two devices are not on the same network (a guest Wi-Fi counts as another network), or that something between them blocks the question.

Try:

qFT8 bridge: "Wrong password", or the bridge refuses the connection

The password must be typed exactly as the bridge shows it. A password the bridge made has only lowercase letters and digits, and never the look-alikes i, l, o, 0 and 1. After several wrong tries in a row the bridge makes that device wait before the next one, up to a minute.

Try: Reading the password again on the bridge: on the bridge mode screen of qFT8, or by starting the bridge download with --show-password. If in doubt, make a new one (NEW PASSWORD, or --new-password) and type that.

qFT8 bridge: connected, but no radio or no audio

The link works, but the bridge cannot use the radio's port or its sound device. The box may read Connected to the bridge's name, followed by "but its sound device could not be opened".

Try:

qFT8 bridge: "The link to the bridge is losing transmit audio" or "cannot keep up"

The network between the two devices is too uneven: transmit audio arrives too late to be played. While the delay can still grow, qFT8 raises it and says the link is losing audio; when even the largest delay is not enough, it says the link cannot keep up and transmissions break up. This is a matter of the network, not of the radio.

Try: Moving closer to the Wi-Fi access point, connecting the bridge (or both devices) with a network cable, and pausing whatever else is loading the network.

Instead of receiving signal from the transceiver, qFT8 is getting audio from the microphone

On Android, this indicates that the phone is using its internal microphone because it doesn't recognize the transceiver as an external audio source. On the computer, check which input is chosen in DEVICE CONFIGURATION in the settings: pick the transceiver's audio device. The most common causes are:

Try: Using a different USB cable, a different adapter, or flipping the cable connections.

The radio's dial does not match the frequency qFT8 shows

The radio's own display and qFT8 differ by a few Hz up to about 100 Hz. This is usually the Tune spectrogram offset you set, and it is on purpose: qFT8 tunes the radio slightly lower and shifts the audio by the same amount, so signals at the very bottom of the spectrogram leave the radio's low-audio blind spot. Decodes, spots, the log and the frequency qFT8 shows all stay the app's real frequency.

Try: Nothing is wrong, so nothing needs fixing. The default is 0 Hz, so this happens only if you set an offset. To change it, or to set it back to 0, open Settings > DEVICE CONFIGURATION > Tuning (this radio) > Tune spectrogram offset (see Tune spectrogram offset).

Not receiving any signal at all; the waterfall is pitch black

If the waterfall remains entirely black both when the transceiver is connected or disconnected, qFT8 likely lacks the necessary permissions to access audio.

Try: On Android, go to your phone's Settings > Apps > qFT8 > Permissions and ensure that Microphone (or Audio recording) is allowed while using qFT8. Alternatively, fully uninstall and reinstall qFT8 and accept all permission prompts on the first launch. On macOS, open System Settings > Privacy & Security > Microphone and allow qFT8. On every computer, check the input chosen in DEVICE CONFIGURATION.

Signals are visible, but no messages are decoded

If you see vertical "wiggly lines" in the waterfall (FT8 signals) but no text appears in the Stations tab, perhaps your clock is not synchronized.

Try:

If no wiggly stripes appear at all in the waterfall, perhaps the band is closed or your antenna is disconnected/untuned.

Messages are decoded too late

The phone's (or an older computer's) processor may be too slow to decode messages on time.

Try: Make sure you switch to Fast decode in the settings, and feel free to move decoding time earlier (e.g. to 13000ms) to create more margin for decoding, at the expense of potentially missing some late messages every cycle.

Error "SWR exceeded threshold — transmission stopped" in the QMX transceiver

If qFT8 shows 0W while transmitting, there are several likely causes:

1. SWR Protection

If the QMX LCD display shows an "S" after the frequency, it means SWR protection kicked in. This means your antenna is not properly tuned for the current band, and the QMX has stopped transmitting to protect its circuitry.

Additionally, qFT8 has its own configurable SWR threshold setting in the app settings. When measured SWR exceeds this threshold, qFT8 will automatically stop transmission to protect your equipment. It also turns TX OFF: press TX ON again after fixing the antenna.

Note: qFT8 waits 1 second after the start of transmission before checking for 0W to avoid false positives while the QMX ramps up. If the QMX recovers and power rises above 1W, the problem indicator clears automatically.

2. Firmware doesn't support power measurement

If the QMX does not show that SWR protection is engaged, and it shows that transmission is happening properly, it may be that the firmware is old and does not support power measurement. Devices like the QDX also do not support power measurement. qFT8 does not know how to interpret 0W and it gets confused.

Try: If your QMX firmware is old, update it. If you are using a QDX, there is no way around this.

3. Audio signal not reaching the QMX

If the QMX does not show the "S" icon after the frequency, then it is likely that the transceiver is simply not receiving a suitable audio signal from qFT8. The volume may be too low (not enough signal) or too high (clipping/distortion causes the QMX to reject the signal).

Try: Check the signal indicator on your QMX. A single dot means no audio, two dots mean there's audio but it's not loud enough. Go to the FT8 Settings section and adjust the "Set device volume to [X] when using radio" setting to different values (e.g. 70%, 80%, 90%) to find the right level for your device.

4. SWR is low during tuner but SWR protection kicks in

This seems like SWR is spiking or peaking at high power for some instants during actual transmission, which triggers SWR protection. This is an indicator of a finnicky antenna (e.g. magloops), a bad cable, a bad connection, or an issue in the setup.

Try: adding common-mode current chokes (such as ferrite beads) should decrease common-mode current.

What is the qFT8 Android notification? (Android)

This notification allows qFT8 to continue processing audio and managing QSOs when you minimize the app or turn off the screen.

qFT8 stops working when the screen is off (Android)

Some Android manufacturers implement very aggressive battery optimizations that may kill background apps even if you granted the initial permissions.

Double check that you granted the permissions: Go to your phone's Settings > Apps > qFT8 > Battery and select "Unrestricted" (or "Don't optimize").

Buttons act weird or the screen is unresponsive during TX

This is caused by RF Interference (RFI). If your antenna is close to the phone or computer or the cable is poorly shielded, the radio energy can interfere with the touch screen, the mouse or the USB connection.

qFT8 looks different than the screenshots in this manual

The app's user interface is occasionally updated, so some minor visual elements may have changed since the screenshots were taken. However, if significant parts of the UI are completely missing or the colors look heavily altered (e.g. the yellow progress bar, the sequence selectors, etc.), your phone's system dark mode may be incorrectly overriding and messing up the application's color palette.

Try: If your system's dark mode is causing issues, you can try temporarily disabling it or adding qFT8 to its exclusion list to restore the correct design.

qFT8 says "NO RADIO" even though transceiver is connected

The issue is likely that you didn't grant the permissions to connect qFT8 to the transceiver. Sometimes this happens because you tap somewhere out of the permission dialog and the dialog closes.

Try: Disconnect and reconnect the transceiver, this should trigger the prompt again. For comfort, mark the option "Always open qFT8 when transceiver is connected" so you never hit this issue again.

qFT8 shows distance in miles and I want it in kilometers (or vice versa)

This comes from the operating system locale (i.e. language selection).

Try: Switching that configuration to the right country (e.g. English (United States) for miles, English (United Kingdom) for kilometers) will fix it.

qFT8 shows low transmission power (e.g. 0.1W) when transmitting at >10W in QMX

This is a known bug in the QMX firmware (up to at least 1.03.000). If you are using the 2x4 mods (e.g. in a QMX+) and your transmission power exceeds 9.9W, the radio's formatting wraps around. For example, 10.1W is reported by the transceiver to the app as 0.1W over the secondary CAT protocol.

Try: There is no workaround inside qFT8, as the app is directly displaying the value it receives. You can safely ignore this display error or reduce your power below 10W to keep the readings accurate until this bug is patched in the transceiver firmware.

Cannot export ADIF logs to the local storage using Share (Android)

The default Share method relies on the native Android share mechanism to export logs. Sometimes, your device's built-in file sharing menu does not offer a direct option to save to your local filesystem.

Try: Change the export Method to Local save in the settings. This uses the Android file picker to directly save the file to your local storage without relying on the sharing menu.

qFT8 fails to decode some messages

Try: Enable deep decode in the settings. Deep decode does recursive decoding and is able to decode more messages when the band is busy, at the expense of extra processing power. It also removes the harmonics of very strong stations (the unreadable copies that an overdriven signal leaves at higher audio frequencies) to find weaker stations under them. Keep an eye on the spectrogram: if deep decode time is too high in your device (e.g. greater than 1 second) and the app is not able to make decisions on time, disable deep decode.

qFT8 hangs or behaves strangely

If this happens only during transmission, it is likely extreme RFI as mentioned above. If it happens at other times, please scroll to the bottom of the Settings tab and press REPORT BUG (see Reporting a problem), or use the "Email me to report issues and bugs" link.

↑ Back to Table of Contents