FT HAM logo FT HAM

Complete User Guide

FT HAM User Guide

FT8 & FT4 Transceiver for iPhone and iPad

Version 1.2 — April 2026 — iOS 17+

Welcome

Welcome to FT HAM, your portable FT8 and FT4 station. This guide will help you install the app, configure your station, and make your first digital contact—all from your iPhone or iPad, no computer required.

FT8 and FT4 are weak-signal digital modes invented by Joe Taylor (K1JT) and Steve Franke (K9AN). They let you make contacts even when band conditions are challenging—signals as weak as −21 dB below the noise floor can be decoded, far below what the human ear can detect. Whether you are new to digital modes or an experienced operator looking for a mobile solution, this guide covers everything from basic setup to advanced contest and portable operation features. Let’s get on the air!

Target audience: licensed amateur radio operators with basic knowledge of radio operation.

1. Installation & Initial Setup

Download FT HAM, walk through the onboarding, and configure your station identity so the app can generate and decode messages correctly.

1.1 System Requirements

Before downloading, make sure your device meets the minimum requirements:

RequirementDetail
Operating SystemiOS 17.0 or later / iPadOS 17.0 or later
DeviceAny iPhone or iPad supported by iOS 17
Storage~30 MB (app only; log size grows with use)
InternetRequired for initial download only — all core features work offline
PermissionsMicrophone (required), Location (optional, for auto grid locator)

1.2 Download from the App Store

Search for FT8 Ham on the App Store, or visit the FT HAM website and tap the download badge. The app is free to download and includes all core operating features (decoding, transmitting, logging, waterfall, map) at no cost. Optional premium features are available for CAT control, PSK Reporter tools, and direct online log syncing.

After installation, you’ll find the app icon on your home screen. Tap it to launch.

[Figure 1: App Store listing for FT HAM]

1.3 First Launch — Terms & Onboarding

On first launch, FT HAM asks you to accept the Terms of Service and Privacy Policy. After accepting, a guided onboarding walkthrough introduces the app’s main features across 12 illustrated pages. Each page covers a major concept:

  1. Welcome — A brief overview of what FT HAM does: decode and encode FT8/FT4 signals on your iPhone or iPad, with no computer needed.
  2. Receiving (RX) — Explains how decoded messages appear in real time in the message list, showing callsigns, signal reports, grid locators, and timestamps.
  3. Waterfall — Introduces the spectrogram view where signals appear as bright horizontal lines. Demonstrates how to read frequency (horizontal axis) vs. time (vertical axis).
  4. Slide to Reply — Shows the swipe-left gesture on any received message to instantly prepare a reply. FT HAM automatically fills in the DX callsign, sets the correct frequency offset, and selects the right transmit cycle.
  5. View Modes — Demonstrates three layout options: Vertical (RX and TX side by side), Separated (toggle between RX-only and TX-only panes), and Condensed (single interleaved list, ideal for iPhone in portrait).
  6. Map — Shows the interactive map with worked grid squares, country overlays, and geodesic paths from your location to contacted stations.
  7. Transmitting (TX) — Explains that FT HAM generates precisely timed audio tones, which your radio converts to RF using VOX. No RF is generated by your device itself.
  8. Logbook — Describes automatic QSO logging and ADIF export for importing into other logging software or uploading to online services.
  9. Auto-Sequencing — Explains hands-free QSO handling: FT HAM selects the right message at each step of the exchange so you don’t have to.
  10. Station Setup — Points you to Configuration to enter your callsign and grid locator before you can transmit.
  11. Getting Started — A 5-point quick-start checklist: (1) set callsign, (2) select band, (3) connect audio, (4) tap Listen, (5) swipe to reply.
  12. Ready to Go! — Good DX and 73!

Swipe through all pages at your own pace. You can revisit the onboarding at any time from the Configuration tab—look for the “Show Onboarding” option at the bottom of the settings list.

[Figure 2: Onboarding welcome page showing the swipe-through tutorial]

1.4 Microphone Permission

iOS will prompt you to allow microphone access the first time you tap Listen (Start RX). You must grant this permission—FT HAM listens to audio from your transceiver to decode FT8/FT4 signals. Without microphone access, the app cannot receive or decode anything.

Privacy note: No audio data leaves your device. All decoding is performed locally on your iPhone or iPad. FT HAM does not record, store, or transmit raw audio.

If you accidentally denied the permission, open the iOS Settings app → scroll to FT8 Ham → toggle Microphone on. You may need to restart the app after changing this setting.

1.5 Location Permission (Optional)

If you enable Auto Locator from GPS (see below), FT HAM will request location permission. Set it to “While Using the App” in iOS Settings → FT8 Ham → Location. FT HAM uses your coordinates solely to compute your Maidenhead grid square. No location data is stored or sent anywhere.

GPS requires a clear view of the sky. Indoor reception may be slow or unavailable. If GPS is not available, you can always enter your grid locator manually.

1.6 Station Identity — Callsign & Grid Locator

Before you can transmit, you need to set two essential pieces of information:

  • Callsign — Your unique amateur radio identifier (e.g. EA4IQL, W1AW, VK3ABC). This is included in every FT8/FT4 message you send.
  • Grid Locator — A Maidenhead grid square that encodes your geographic position (e.g. IN80 for 4 characters, or IN80dk for 6 characters). This is exchanged during the QSO and enables the other station to compute the distance between you.

How to set your station identity:

1

Open the Configuration tab (gear icon, the last tab in the bottom tab bar).

2

Under Station Details, type your callsign. It will be automatically uppercased. The callsign must be a valid amateur radio callsign—FT HAM will not allow transmission without one.

3

Enter your 4-character or 6-character Maidenhead grid locator (e.g. IN80 or IN80dk). If you don’t know your grid, you can look it up on any Maidenhead grid map website, or simply enable the auto-locator feature below.

4

Optional: Enable Auto Locator from GPS to let FT HAM compute your grid locator automatically from your device’s GPS coordinates. This is especially useful for portable and mobile operation (POTA, SOTA, field days), since your grid updates automatically as you move. When enabled, the manual grid field is overridden by the GPS-computed grid.

Important: You must hold a valid amateur radio license to transmit. FT HAM generates audio that your transceiver converts to RF. Transmitting without a license is illegal in all countries. The app does not verify your license status—it is your responsibility to ensure compliance with your national regulations.
If you operate portable with a suffix (e.g. EA4IQL/P), you can enter the full callsign including the slash. Note that some callsign formats with slashes use a different encoding in FT8 that limits the information in each message.
[Figure 3: Station Details in the Configuration tab — callsign, grid locator, and auto-locator toggle]

2. User Interface & Navigation

FT HAM is organized into five main tabs accessible from the bottom tab bar. Each tab focuses on a different aspect of the operating experience. This section gives you a thorough tour of every screen.

2.1 Tab Bar Overview

The tab bar sits at the bottom of the screen and is always visible. Tap any icon to switch between the five main areas of the app:

Tab Icon Purpose
TX/RX Waveform Main operating screen — send and receive FT8/FT4 messages, control transmission, and manage QSO flow
Waterfall Spectrum Full-screen spectrogram — visualize all signals on the band, tap to set TX frequency
Map Globe Grid locator map — see where your contacts are on a world map with worked grids and paths
Logbook Book Your logged QSOs with search, country flags, and ADIF export capabilities
Configuration Gear All app settings — station identity, mode, band, audio, interface, QSO behavior, and more
[Figure 4: Tab bar and header bar showing band, mode (FT8/FT4), and TX/RX status]

2.2 Header Bar

The header bar at the top of the TX/RX screen displays critical real-time information:

  • Band indicator — The currently selected amateur band (e.g., 20m, 40m). Tap to quickly access band settings.
  • Mode indicator — Shows whether FT HAM is operating in FT8 or FT4 mode.
  • TX/RX status — Visual indicator showing whether the app is currently transmitting (TX), receiving (RX), or idle.
  • QSO state — Displays the current state of any active contact (e.g., “Calling CQ...”, “Sending SNR report...”, “QSO completed”).

2.3 TX/RX Tab — Message Display

The TX/RX tab is where you spend most of your time. Decoded messages appear in real time as each 15-second FT8 cycle (or 7.5-second FT4 cycle) completes. Each message row contains several data fields:

Field Description Example
Timestamp UTC time when the message was decoded, shown as HH:MM:SS 14:30:15
SNR Signal-to-Noise Ratio measured by your receiver, in dB. Negative values mean the signal is below the noise floor. -12
Freq Offset The audio frequency offset in Hz where this signal was detected within the 0–3000 Hz passband 1423
Time Offset Time offset in seconds relative to the slot boundary, showing how well-synchronized the sender’s clock is +0.3
Message Text The decoded FT8/FT4 message content — callsigns, signal reports, grid locators, or CQ calls CQ EA4IQL IN80
Country Flag Emoji flag automatically resolved from the sender’s callsign prefix 🇪🇸

View Modes

FT HAM offers three layout modes for the TX/RX tab, configurable in Configuration → Interface → View Mode:

View Mode Layout Best for
Vertical RX and TX message columns displayed side by side in two panels Standard operation; iPad landscape; seeing both streams at once
Separated Full-width single panel; toggle between RX-only and TX-only views using a segmented control Focused monitoring of either stream; useful when one list is very busy
Condensed Single compact list with all messages interleaved chronologically, color-coded by RX/TX iPhone portrait; quick overview; minimal screen space

Message Color Coding

Each row in the message list is color-coded to immediately convey its role in the exchange:

Swatch Color Meaning
Yellow Your own CQ transmissions
Purple / Violet Received CQ from another station
Blue Message directed to you (grid exchange phase)
Orange Message directed to you (RST / signal report phase)
Purple (dark) RR73 / RRR / 73 messages (any station)
Gray Unknown message type
System background Station-to-station exchange not involving you

Swipe to Reply

Each received message row is interactive. Swipe left on any message to instantly prepare a reply. When you swipe on a CQ message, FT HAM:

  • Sets the DX callsign to the station that called CQ
  • Copies their grid locator if they included one
  • Sets your TX frequency offset to match theirs (unless “Hold TX Frequency” is enabled)
  • Selects the opposite even/odd cycle so you transmit when they are listening
  • Queues the appropriate reply message (your callsign + grid)

You can swipe on non-CQ messages too—for example, to jump into an existing exchange or to set your frequency offset to where another station is operating.

Message Filtering

Use the Show only involved toggle at the top of the message list to filter out messages not addressed to your callsign. When enabled, only CQ calls and messages that include your callsign are shown. This is very useful on busy bands where dozens of stations are active simultaneously.

The mini-waterfall strip at the bottom of the TX/RX tab gives you a quick visual of band activity without switching to the full Waterfall tab. Bright spots indicate decoded signals.
[Figure 5: TX/RX tab in Vertical view mode showing decoded messages with all data fields]

2.4 Controls Panel

Below the message lists, the control panel provides everything you need to manage your operating session:

UTC Clock

A real-time UTC clock updated every second. Since FT8 and FT4 require sub-second timing accuracy, this clock helps you verify that your device’s time is synchronized correctly. The clock should match your transceiver’s UTC display.

Status Bar

Displays the current QSO state in plain text. The possible states are:

StateMeaning
No contact startedIdle — not in a QSO
Calling CQ...Transmitting a CQ call and waiting for replies
Sending grid...Sending your grid locator to the DX station
Sending SNR report...Sending the signal report you measured for the DX station
Expecting SNR report...Waiting for the DX station to send their signal report
Sending R-Report...Acknowledging their report and sending yours
Expecting RRR / RR73...Waiting for the DX station’s confirmation
Sending RRR...Confirming receipt of their report
Sending 73...Sending the final farewell message
QSO completedThe contact is complete and has been logged
Timeout/Retry exceededThe exchange failed after the maximum number of retries

When a QSO is in progress, the locked DX callsign is also shown prominently.

Operating Buttons

  • Listen / Stop — Start or stop receiving. When you tap Listen, FT HAM opens the microphone input and begins decoding incoming audio. The waterfall also starts updating.
  • Start Auto TX / Stop TX — Enable automatic transmission, which begins playing TX audio at the next transmit slot. Tap Stop TX to immediately halt any ongoing or queued transmission.

Message Selector

The message selector shows the next message queued for transmission. In auto-sequencing mode, FT HAM selects the correct message automatically. In manual mode (auto-sequencing disabled), use the < and > buttons to cycle through the six standard FT8 message types:

  1. CQ [your-call] [grid] — CQ call
  2. [dx-call] [your-call] [grid] — Grid exchange (reply to CQ)
  3. [your-call] [dx-call] [report] — Signal report
  4. [dx-call] [your-call] R[report] — Roger + signal report
  5. [your-call] [dx-call] RRR — Received confirmation
  6. [your-call] [dx-call] 73 — Farewell

2.5 Waterfall Tab

The waterfall is a full-screen spectrogram that displays the entire 0–3000 Hz audio passband. Time flows vertically (newest at the top), and frequency runs horizontally. Signal activity appears as bright horizontal marks against the darker noise floor.

The waterfall updates once per FFT frame, providing a continuous real-time view of all activity on the band. You can easily spot bursts of FT8 activity, identify clear frequencies for your transmission, and monitor band conditions at a glance.

Waterfall Toolbar

The floating toolbar in the corner provides four toggles:

  • Frequency cursor — When enabled, tapping anywhere on the waterfall sets your TX frequency offset to that position. A vertical line appears at the selected frequency. This is the fastest way to pick a clear transmission slot.
  • Callsign overlays — Show or hide decoded callsign labels overlaid on the waterfall at the position where each signal was detected. This helps you identify who is transmitting at each frequency.
  • Timestamp marks — Show or hide UTC time marks on the left edge of each row, so you can see exactly when each transmission cycle occurred.
  • Vertical labels — Display decoded message frequency markers as vertical lines at the bottom of the waterfall, showing you where signals have been decoded.

Reading the Waterfall

A completely dark waterfall means no signals are being received—check your audio connection and input gain. A waterfall with consistent bright bands across the full width usually means the audio is overdriven (clipping); reduce gain. Ideal operation shows a relatively dark background with distinct, bright horizontal marks at specific frequencies where stations are transmitting.

Tap on a bright signal trace in the waterfall to set your TX offset to that frequency. This is especially useful when you want to reply to a station: swipe their message in the TX/RX tab, then verify the frequency visually on the waterfall.
[Figure 6: Waterfall view with callsign overlays, frequency cursor, and timestamp marks enabled]

2.6 Map Tab

The Map tab displays an interactive world map showing your amateur radio activity geographically. The map is powered by Apple MapKit and supports standard gestures (pinch to zoom, drag to pan, rotate).

Four toggle buttons in the top-right corner control what is displayed:

ToggleDefaultWhat it shows
Grid LinesOnMaidenhead grid square boundaries overlaid on the map. Each grid square is 1° latitude × 2° longitude. Worked squares are highlighted.
Country CirclesOnColored circles centered on each country you have contacted. The color and size can vary based on the number of QSOs.
GeodesicsOnGreat-circle paths drawn from your station’s location to each contacted station. These represent the actual path radio signals follow along the Earth’s surface.
AnnotationsOffCallsign labels attached to each map marker. Turn this on to see which callsign corresponds to which map pin.

Map Icon Legend

The map uses consistent visual elements across all display modes:

Icon Meaning
A locator you have already worked
A country you've heard in the last RX loop
Path between two stations contacting each other in the last RX loop
📍 Grid locator with callsign annotation
Your current location

The map updates automatically as you complete QSOs. It’s a great way to visualize your DX reach and discover which regions you’ve worked.

[Figure 7: Map view showing worked grid squares, geodesic lines, and country circles across multiple continents]

2.7 Logbook Tab

The Logbook shows all your completed QSOs in a scrollable list, newest first. Each entry displays:

  • Callsign — The other station’s call, displayed prominently
  • Country flag — Emoji flag resolved from the callsign prefix (e.g., 🇺🇸 for W/K/N calls, 🇯🇵 for JA calls)
  • Country name — The resolved DXCC entity name
  • Grid locator — The other station’s Maidenhead grid
  • Frequency — The actual frequency in Hz (dial + offset)
  • Band — The amateur band (20m, 40m, etc.)
  • Mode — FT8 or FT4
  • RST Sent / RST Received — The signal reports exchanged during the QSO (e.g., -12 / +05)
  • Timestamp — Date and time of the contact (UTC by default)
  • CQ Modifier — If you were using a CQ modifier (POTA, SOTA, etc.), it is stored with the entry
  • Activation reference — If applicable, the POTA/SOTA/WWFF/IOTA reference number

Toolbar Actions

  • Export — Generate an ADIF file for importing into logging software or online services. See Section 7.6 for detailed export options.
  • Clear — Remove all logged contacts from the logbook. A confirmation dialog appears before deletion.
  • Time display toggle — Switch between showing timestamps in UTC (default) or your device’s local time zone.
Clearing the logbook is irreversible. Always export your log to ADIF before clearing if you want to keep a backup.
[Figure 8: Logbook view with QSO entries showing callsign, flag, grid, SNR, and export button]

3. Audio Configuration & Transceiver Connection

FT HAM generates and receives audio. Connecting it to your transceiver properly is essential for reliable decoding and clean transmissions. This section covers every connection method, audio settings, and troubleshooting tips.

3.1 How Audio Works in FT HAM

FT HAM operates as an audio-based transceiver companion. It does not transmit RF directly. Instead, it acts as a bridge between digital signal processing and your radio equipment:

  • Receiving (RX): Audio from your transceiver enters your iOS device through the microphone (built-in, wired headset, or USB audio interface). FT HAM processes this audio through a Fast Fourier Transform (FFT), feeding the result to both the waterfall display and the FT8/FT4 decoder. Up to dozens of messages can be decoded simultaneously from a single 15-second audio window.
  • Transmitting (TX): FT HAM generates precisely timed audio tones conforming to the GFSK (Gaussian Frequency-Shift Keying) modulation used by FT8/FT4. These tones are played through your device’s speaker or audio output. Your transceiver picks up these tones and converts them to RF for transmission over the air.

The internal audio processing sample rate is 12,000 Hz. FT HAM automatically resamples from the hardware sample rate (typically 44,100 Hz or 48,000 Hz for USB audio interfaces) to this internal rate. This is handled entirely in software—you do not need to configure any sample rates.

3.2 Connection Methods

There are three main ways to connect your iOS device to your transceiver, listed from simplest to most reliable:

Method A: Acoustic Coupling (Simplest, Least Reliable)

Place your iPhone/iPad near your transceiver’s speaker. The device’s built-in microphone picks up the radio’s audio for decoding, and the device’s speaker plays TX audio back into the radio’s microphone. Set your radio to VOX mode so it keys automatically when it detects audio. This method requires no cables or adapters.

Pros: No equipment needed beyond your phone and radio. Good for quick testing and demonstration.

Cons: Ambient noise (conversations, fan noise, other electronics) corrupts the audio and prevents reliable decoding. Speaker/microphone levels are inconsistent. Feedback loops can occur. Not recommended for on-air operation.

Acoustic coupling is convenient for testing but unreliable for real QSOs due to ambient noise and inconsistent audio levels. Use a cable connection for on-air operation.

Method B: USB Audio Interface (Recommended)

Connect a USB audio interface to your iPhone/iPad via a Lightning-to-USB or USB-C adapter. The interface connects to your transceiver’s data or accessory port. Popular interfaces used by ham radio operators include:

  • Digirig Mobile — compact, affordable, purpose-built for digital modes. Includes audio isolation and optional serial/PTT lines.
  • SignaLink USB — widely used in the ham community. Provides built-in VOX and adjustable audio levels via knobs.
  • Generic USB soundcards — basic USB-C or USB-A audio dongles work for audio routing, though they lack isolation. Use with caution on HF where RF feedback is more likely.
  • Transceiver built-in USB audio — Some modern transceivers (e.g., Icom IC-705, Yaesu FT-991A) expose a USB audio interface when connected via USB-C. Connect directly to your iPhone/iPad via USB-C.

USB audio interfaces provide:

  • Clean, noise-free audio in both directions
  • Consistent, repeatable levels without ambient interference
  • Audio isolation (transformers) to prevent ground loops and RF feedback
  • Some interfaces include built-in VOX or PTT control
When purchasing a USB audio interface for use with FT HAM on iOS, verify that it is class-compliant (no special drivers required) and works with USB OTG on iPad/iPhone. Most budget USB-C audio adapters are class-compliant and work immediately.

Method C: USB-C to 3.5 mm Jack Cable (Popular & Affordable)

Modern iPhones and iPads feature a USB-C port. The most popular and affordable wired connection method uses an Apple USB-C to 3.5 mm Headphone Jack Adapter (or a compatible MFi-certified adapter) combined with a standard 3.5 mm audio cable to your transceiver. This gives you a clean, bidirectional audio path for both receiving and transmitting via VOX.

What you need

ItemDescription
USB-C to 3.5 mm adapterApple USB-C to 3.5 mm Headphone Jack Adapter (model MU7E2) or any compatible USB-C DAC dongle. Must be bidirectional (supports both audio out and microphone in).
3.5 mm TRRS splitter (optional)A TRRS-to-dual-TRS splitter that separates the adapter’s single 3.5 mm jack into a headphone output and a microphone input. Needed if your radio uses separate speaker/mic connectors.
Audio cable(s)3.5 mm TRS or TRRS cables to connect from the adapter (or splitter) to your radio’s speaker/headphone output and microphone/DATA input.
Attenuator pad (recommended)A simple inline 20–30 dB attenuator between the radio’s headphone out and the adapter’s mic input prevents clipping. Many USB-C adapters clip easily with full-level headphone output.

TRRS pinout (Apple / CTIA standard)

Apple USB-C adapters follow the CTIA/AHJ wiring standard:

  • Tip — Left audio out (to radio’s DATA IN / microphone)
  • Ring 1 — Right audio out (usually same signal, mono is fine)
  • Ring 2 — Ground
  • Sleeve — Microphone in (from radio’s headphone / speaker out)

Step-by-step setup

1

Plug the USB-C to 3.5 mm adapter into your iPhone or iPad.

2

Connect the adapter’s 3.5 mm jack to your TRRS splitter. If your radio has a combined DATA connector (e.g., 6-pin mini-DIN), you may need a purpose-built cable instead of a splitter.

3

RX path: Connect the splitter’s microphone input (pink plug or labeled MIC) to your radio’s headphone or speaker output using a 3.5 mm cable. This carries the radio’s received audio into FT HAM for decoding.

4

TX path: Connect the splitter’s headphone output (green plug or labeled HEADPHONE) to your radio’s microphone input, DATA IN, or AUX IN. This carries FT HAM’s generated audio tones into the radio for transmission.

5

Enable VOX on your transceiver (see Section 3.3 below). VOX detects the audio tones from FT HAM and automatically keys the transmitter. No manual PTT is required.

6

Set your radio’s headphone volume to low/medium (30–50%). Then adjust FT HAM’s Input Gain slider (Configuration → Input Gain) until the waterfall shows clear signal traces without the clipping indicator appearing. A good starting point is 0.5× to 1.0×.

7

Test TX: Start a CQ call and verify that your radio keys (TX light comes on) when FT HAM plays audio, and returns to RX when the slot ends. If the radio doesn’t key, increase the device volume or lower your VOX threshold.

If you have an older iPhone or iPad with a Lightning port, use the Apple Lightning to 3.5 mm Headphone Jack Adapter (model MMX62). The rest of the setup is identical.
Important: Not all USB-C to 3.5 mm adapters support microphone input. Cheap adapters may be output-only (no mic). The official Apple adapter and most MFi-certified adapters support bidirectional audio. If the waterfall remains blank when connected, your adapter may not support mic input—check the adapter specifications.
[Figure 3B: USB-C to 3.5 mm cable connection diagram showing iPhone → adapter → splitter → radio speaker out + radio mic in]

Method D: Direct Audio Cable (Custom Wiring)

For permanent installations or radios with dedicated DATA connectors (e.g., Yaesu 6-pin mini-DIN, Icom 13-pin DIN, Kenwood 13-pin DIN), you can build or purchase a custom cable that connects the USB-C adapter directly to the radio’s data port. This eliminates the splitter and provides a cleaner setup.

Many ham radio vendors sell pre-made cables for specific radio models. Search for your transceiver model + “digital modes cable” or “DATA cable.”

RF safety: When connecting your iOS device to a transmitter, always use appropriate RF isolation (audio transformers or a dedicated digital-mode interface). Direct wiring without isolation can damage your device, cause RF feedback into the audio chain, or produce distorted transmissions. If you hear a “motorboating” sound on TX, RF is getting into the audio path. This is especially important on HF bands where RF levels near the antenna can be high.

3.3 VOX Setup on Your Transceiver

Since FT HAM generates audio tones for transmission, your transceiver needs a way to know when to switch from receive to transmit. The simplest method is VOX (Voice-Operated Switch):

  • Enable VOX on your transceiver (consult your radio’s manual for the menu location).
  • Set the VOX gain so that FT HAM’s TX audio reliably triggers the transmitter. Too high and it won’t key; too low and ambient noise may key it accidentally.
  • Set the VOX delay (anti-VOX or hang time) to about 0.5–1.0 seconds. Too short and the transmitter may drop out between tones; too long and it may stay keyed into the next receive slot.
  • Verify that the radio returns to receive quickly enough for FT HAM to decode the next incoming slot.
Test your VOX settings by starting a CQ transmission and watching whether the radio keys and unkeys cleanly at slot boundaries. On the waterfall, your own transmission should appear as a crisp horizontal line at your set frequency offset.

3.4 Input Gain

Adjust the software input gain in Configuration → Input Gain using the slider. The range is 0.1× to 2.0× (default: 1.0×). This multiplier amplifies or attenuates the audio signal in software before it reaches the decoder.

Proper gain setting is critical for reliable decoding:

  • Too low (waterfall appears mostly dark, few or no decodes): Increase the gain, or increase the volume on your transceiver’s headphone/line output.
  • Too high (waterfall appears completely bright, clipping warning shown): Decrease the gain, or reduce the volume on your transceiver. Audio clipping distorts the waveform and prevents the decoder from extracting signal information.
  • Just right: The waterfall has a dark background with distinct bright marks where signals are present. The recommended gain range for most setups is 0.5× to 1.5×.

FT HAM continuously monitors the audio input for clipping (signal amplitude exceeding 99% of the maximum level). When clipping is detected, a warning indicator appears. Sustained clipping will prevent reliable decoding of any signals.

[Figure 9: Input gain slider in Configuration showing the 0.1× to 2.0× range]

3.5 Supported Audio Devices

FT HAM configures the iOS audio session for simultaneous playback and recording. The following audio input/output devices are supported:

Device TypeRX (Input)TX (Output)Notes
Built-in microphone & speaker✅✅Good for acoustic coupling testing only
Wired headset (Lightning / USB-C / 3.5mm)✅✅Microphone on the headset cable is used for RX input
USB audio interface (class-compliant)✅✅Recommended for on-air operation. Connect via Lightning/USB-C adapter.
Bluetooth HFP audio✅✅Works but introduces latency (~50–200 ms). May cause timing issues with FT8 slot synchronization.
Bluetooth A2DP (output only)❌✅A2DP is output-only — cannot be used for RX input
Bluetooth audio introduces variable latency that can interfere with FT8/FT4 slot timing. For reliable on-air operation, use a wired connection (USB audio interface or direct cable).

3.6 CAT Control via Network

CAT (Computer Aided Transceiver) allows FT HAM to control your radio remotely over a network connection — setting frequency, switching bands, and toggling PTT (transmit/receive) without touching the radio. This is especially useful for remote operation (controlling a station over the internet) or for hands-free band switching from your iPhone or iPad. Note: CAT Control is a premium feature.

How CAT works in FT HAM

FT HAM uses the rigctld protocol (from the open-source Hamlib project) to communicate with your transceiver over TCP/IP. This means you need a computer or device running rigctld (or a compatible server) connected to your radio, and FT HAM connects to it over your local network or the internet.

The signal chain looks like this:

FT HAM (iPhone/iPad)  ←→  TCP/IP network  ←→  rigctld (computer)  ←→  serial/USB  ←→  Transceiver

Requirements

ComponentDetails
ComputerAny machine running rigctld — Windows, macOS, Linux, or even a Raspberry Pi. Must be connected to the transceiver via serial (RS-232), USB-serial, or CI-V cable.
Hamlib / rigctldFree, open-source software. Download from hamlib.github.io. Also bundled with many ham radio programs (WSJT-X, flrig, etc.).
NetworkBoth devices (iPhone/iPad and computer) must be on the same network, or the rigctld port must be forwarded / VPN-accessible for internet operation.
TransceiverMust support CAT control (most modern HF transceivers do — check your radio’s manual for the CAT/CI-V port).

Setting up rigctld on your computer

1

Install Hamlib. On macOS, you can install it with Homebrew: brew install hamlib. On Windows, download the pre-built binaries. On Linux, use your package manager (e.g., apt install libhamlib-utils).

2

Identify your radio model. Run rigctld --list to see all supported radios and find your model number. For example, Icom IC-7300 is model 3073, Yaesu FT-991A is 1035.

3

Start rigctld. Run the command with your radio model and serial port. For example:

rigctld -m 3073 -r /dev/ttyUSB0 -s 19200 -T 0.0.0.0 -t 4532

This starts the server listening on all network interfaces (0.0.0.0) on port 4532 (the default rigctld port). Replace -m 3073 with your radio’s model number, -r /dev/ttyUSB0 with your serial port (on macOS: /dev/cu.usbserial-XXXX; on Windows: COM3), and -s 19200 with your radio’s CAT baud rate.

4

Verify the connection. From another terminal on the same machine, run rigctl -m 2 -r localhost:4532 f to read the current frequency. If it returns a frequency in Hz (e.g., 14074000), rigctld is running and connected to your radio.

5

Note the computer’s IP address. Find it with ifconfig (macOS/Linux) or ipconfig (Windows). You’ll need it to configure FT HAM. Example: 192.168.1.42.

As an alternative to raw rigctld, you can use flrig (a graphical rig controller that includes a built-in rigctld server), or any software that exposes the Hamlib TCP protocol on a network port.

Configuring CAT in FT HAM

1

Go to Configuration → CAT Control.

2

Enable the CAT Control toggle.

3

Enter the Host (IP address of the computer running rigctld, e.g. 192.168.1.42). For a local connection on the same device, use 127.0.0.1.

4

Enter the Port (default: 4532).

5

Configure the CAT features:

  • PTT via CAT — When enabled, FT HAM sends PTT on/off commands to the radio through rigctld instead of relying on VOX. This is more reliable because it keys the transmitter precisely at slot boundaries without VOX delay. Recommended when available.
  • Sync Frequency — When enabled, FT HAM sends frequency change commands to the radio when you switch bands. This means you can change bands from FT HAM and the radio follows automatically.
  • Apply Audio Offset — When enabled, FT HAM sends the dial frequency plus the audio offset to the radio, which can be useful for some rig configurations.
6

Use the Test Connection button to verify that FT HAM can reach rigctld. A successful test shows the current frequency read from your radio.

Remote Operation via Internet

For controlling your station from anywhere over the internet, you need to make the rigctld port accessible remotely. There are two recommended approaches:

  • VPN is the recommended method. Set up a VPN (WireGuard, Tailscale, or your router’s built-in VPN) so your iPhone/iPad is on the same virtual network as your station computer. Then connect to the rigctld server using the VPN IP address. This provides encryption and security without exposing ports to the public internet.
  • Port forwarding (less secure): Forward port 4532 on your router to the computer running rigctld. Then use your public IP address (or a dynamic DNS hostname) as the host in FT HAM. Use this only on trusted networks, as the rigctld protocol has no authentication or encryption.
Security: The rigctld protocol has no built-in authentication or encryption. Anyone who can connect to the port can control your radio. Never expose rigctld directly to the public internet. Always use a VPN or SSH tunnel for remote access.

For remote operation, you also need to route audio between your device and the radio. This can be done by streaming audio over the internet using applications like Mumble, or by running FT HAM’s audio through a remote audio pipeline. The exact setup depends on your station configuration.

[Figure 9B: CAT Control settings showing host, port, PTT, frequency sync, and test connection button]

4. Your First QSO in FT8 — Step by Step

This section walks you through making your first FT8 contact from start to finish, covering both answering a CQ call and calling CQ yourself. FT8 contacts follow a structured exchange of short messages in precisely timed 15-second windows.

4.1 Prerequisites Checklist

Before you begin, verify each of the following:

  • ✅ Your callsign and grid locator are set in Configuration → Station Details
  • ✅ Mode is set to FT8 (Configuration → Mode and Frequency)
  • ✅ A band is selected (start with 20m during daytime or 40m in the evening — these are the most active bands for FT8)
  • ✅ Your transceiver is tuned to the correct dial frequency for the selected band (e.g., 14.074 MHz for 20m FT8 — see the frequency table below)
  • ✅ Audio connection between your device and transceiver is working (you should see activity on the waterfall when the band is active)
  • ✅ Microphone permission is granted in iOS Settings
  • ✅ Your transceiver is set to VOX mode with appropriate sensitivity and delay settings
  • ✅ Your transceiver’s mode is set to USB (Upper Sideband) — FT8/FT4 are always transmitted in USB, even on bands below 10 MHz where SSB traditionally uses LSB
  • ✅ Auto Sequencing is enabled (Configuration → QSO Settings — it is on by default)
  • ✅ Your device’s clock is synchronized (iOS Settings → General → Date & Time → Set Automatically)
USB mode is mandatory. Unlike voice SSB operation where you switch between USB and LSB depending on the band, FT8 and FT4 always use USB on all bands. Set your radio to USB (or DATA-USB / DIG-U if your radio has a dedicated digital mode).

4.2 Answering a CQ — Step-by-Step Walkthrough

The easiest way to make your first contact is to answer someone else’s CQ call. Here’s the complete process:

1

Select band and mode. Go to Configuration → Mode and Frequency. Select FT8 and choose your band (e.g., 20m). The expected dial frequency (14.074 MHz) is shown on screen. Tune your radio to match.

2

Set the frequency offset. The offset determines where within the 0–3000 Hz audio passband your signal will be placed. The default is 1500 Hz, which places you in the middle of the band. You can adjust this with the slider in Configuration, by typing a precise value, or later by tapping on the waterfall. For your first QSO, leave it at the default—FT HAM will adjust it automatically when you swipe to reply.

3

Start receiving. Go to the TX/RX tab and tap Listen. The waterfall will begin scrolling and decoded messages will appear in the RX list. Wait for at least 2–3 full 15-second cycles (30–45 seconds) to get a good picture of band activity. If the band is active, you should see multiple messages decoded each cycle.

4

Find a CQ call. Look for messages that start with CQ. For example:

CQ EA4IQL IN80

This means station EA4IQL in grid IN80 is calling CQ—they are looking for someone to contact. A CQ message is an open invitation: anyone can reply. Choose a station with a reasonably strong signal report (e.g., -10 or better) for your first attempt, as this increases the chance of a successful exchange.

5

Reply to the CQ. Swipe left on the CQ message in the RX list. FT HAM automatically:

  • Sets the DX callsign to the station calling CQ
  • Copies their grid locator
  • Matches your TX frequency offset to theirs
  • Selects the correct even/odd cycle (the opposite of when they transmitted)
  • Prepares your reply message: [their-call] [your-call] [your-grid]
6

Start transmitting. Tap Start Auto TX. FT HAM will transmit your reply at the next available slot boundary. Your radio should key via VOX when it detects the audio tones.

7

Let auto-sequencing handle the exchange. With Auto Sequencing enabled, FT HAM automatically advances through the standard FT8 message exchange. The complete 5-step exchange looks like this:

Scenario: You answer EA4IQL’s CQ

THEM
CQ EA4IQL IN80 They call CQ with their callsign and grid
YOU
EA4IQL EA1ABC IN73 You reply with both callsigns and your grid
THEM
EA1ABC EA4IQL +05 They send you a signal report (+05 dB SNR)
YOU
EA4IQL EA1ABC R-12 You acknowledge (R) and send your report (-12 dB)
THEM
EA1ABC EA4IQL RR73 They confirm (RR) and send 73 — QSO complete!
8

QSO logged. When the exchange completes, FT HAM logs the contact automatically (if Auto QSO Logging is enabled) or shows a confirmation prompt. The QSO appears in your Logbook with all details: callsign, grid, band, mode, signal reports, frequency, and timestamp. The map also updates with the new contact.

If the other station doesn’t reply to your first attempt, FT HAM retransmits the same message up to Max Retry Slots times (default: 3). If there’s still no reply, the QSO times out and returns to idle. This is normal—the other station may have answered someone else, or propagation may not support the path. Try another CQ call.

4.3 Understanding Even and Odd Cycles

FT8 divides time into 15-second slots synchronized to UTC. Slots alternate between even (starting at :00, :30 seconds past each minute) and odd (starting at :15, :45 seconds). In a typical minute, there are four slots: even, odd, even, odd.

During a QSO, one station transmits on even slots and the other on odd slots. This allows both stations to alternate between transmitting and listening. The key rules are:

  • The station calling CQ chooses a slot (usually even).
  • The station answering transmits on the opposite slot.
  • Both maintain their slot assignment throughout the entire QSO exchange.

FT HAM manages this automatically. When you swipe to reply to a CQ, it detects which slot they used and places your reply on the opposite slot. You can override this in the control panel (Force Even / Force Odd) but this is rarely necessary.

Timing is critical. FT8 transmissions must start within approximately 0.5 seconds of the slot boundary. FT HAM synchronizes to your device’s clock, which iOS keeps accurate via NTP (Network Time Protocol). If your device clock is more than ~2 seconds off, decoding will fail. Ensure Settings → General → Date & Time → Set Automatically is enabled on your iPhone/iPad.

4.4 Calling CQ Yourself

Instead of answering someone else’s CQ, you can call CQ yourself. This is useful when you want to attract calls, activate a park or summit, or operate on a specific frequency:

1

Make sure your callsign, locator, band, and mode are set correctly.

2

Choose a clear frequency. Check the waterfall for an open slot—a frequency with no bright signal traces. Tap the waterfall at that position, or manually set the offset in Configuration. Choosing a clear frequency avoids interference with other stations.

3

In the Message Selector, use the < / > buttons to select the CQ message (message index 0). It will read something like CQ EA1ABC IN73. If you have a CQ modifier set (e.g., POTA), it will show as CQ POTA EA1ABC IN73.

4

Tap Start Auto TX. FT HAM will transmit your CQ at the next slot boundary and listen for replies on the alternate slot.

5

Wait for replies. Other stations will see your CQ and swipe to reply. Their response will appear in your RX list. If Auto Sequencing is enabled, FT HAM automatically locks onto the first station that replies and completes the QSO exchange.

6

After the QSO completes, FT HAM returns to CQ mode and begins calling again, looking for the next contact. This cycle continues until you tap Stop TX.

Scenario: You call CQ and K5XYZ replies

YOU
CQ EA1ABC IN73 You call CQ with your callsign and grid
THEM
EA1ABC K5XYZ EM12 K5XYZ replies with their callsign and grid
YOU
K5XYZ EA1ABC -08 You send them a signal report (-08 dB)
THEM
EA1ABC K5XYZ R-15 They acknowledge and send their report
YOU
K5XYZ EA1ABC RR73 You confirm and sign off — QSO complete!
You can add a CQ modifier to target specific regions or activities. For example, CQ DX EA1ABC IN73 targets long-distance stations, and CQ POTA EA1ABC IN73 signals that you are activating a park. Configure this in Configuration → CQ Modifier. See Section 7.2 for a full list of modifiers.

4.5 What Happens When a QSO Times Out

Not every QSO attempt succeeds. If the other station doesn’t respond after the configured number of Max Retry Slots (default: 3), FT HAM marks the exchange as a timeout and returns to idle state. Common reasons for timeouts:

  • QRM (interference): Another station is transmitting on the same frequency, masking your signal.
  • Propagation failure: The band may not support the path between you and the other station. A signal report of -20 or worse indicates marginal conditions.
  • QSB (fading): The signal may have been strong when you started but faded before the exchange could complete.
  • Pileup: The other station may have answered a different caller.
  • Clock error: If either station’s clock is significantly off, messages won’t align with slot boundaries and will fail to decode.

Timeouts are a normal part of FT8 operation, especially on challenging bands or during marginal conditions. Simply try another station or wait for better propagation.

4.6 Common FT8 Dial Frequencies

Tune your transceiver to the standard dial frequency for each band. FT HAM shows the expected dial frequency when you select a band, but your radio must be tuned to match. Remember: your radio should always be set to USB mode.

BandFT8 Dial FrequencyTypical Activity
160m1.840 MHzNighttime only; limited activity, long-path DX
80m3.573 MHzEvening/nighttime; regional and continental contacts
40m7.074 MHzEvening/nighttime best; very active, good for beginners
30m10.136 MHzUsually active; WARC band, less crowded than 20m
20m14.074 MHzDaytime; most active FT8 band worldwide. Start here.
17m18.100 MHzDaytime; WARC band, good for DX
15m21.074 MHzDaytime during moderate/high solar activity
12m24.915 MHzDaytime during high solar activity; excellent DX
10m28.074 MHzDaytime during high solar activity; sporadic E openings
6m50.313 MHzSporadic E and tropo openings; seasonal
Which band to start with? During daytime, try 20m (14.074 MHz) — it is the most active band and provides worldwide contacts. In the evening and at night, switch to 40m (7.074 MHz) for regional and continental QSOs. Check the waterfall: if you see lots of bright traces, the band is active.
[Figure 10: Band and mode selector in Configuration with dial frequency displayed]

5. FT4 vs FT8 — Differences & When to Use Each

FT8 and FT4 are both weak-signal digital modes created by Joe Taylor (K1JT) and Steve Franke (K9AN). They share the same structured QSO exchange and message types, but differ in timing, sensitivity, and typical use cases. FT HAM supports both modes and switching between them is instant.

5.1 Technical Comparison

Feature FT8 FT4
Transmission slot duration 15 seconds 7.5 seconds
Slots per minute 4 (even/odd pairs) 8 (even/odd pairs)
Time for a complete QSO ~75 seconds (5 slots) ~37.5 seconds (5 slots)
Minimum decodable SNR -21 dB -17.5 dB
Occupied bandwidth per signal ~50 Hz ~80 Hz
Modulation type 8-GFSK (8 tones) 4-GFSK (4 tones)
Forward Error Correction LDPC (174,91) LDPC (174,91)
Typical use General operation, DX hunting Contests, rapid QSOs
Worldwide activity level Very high — the default digital mode Moderate — growing, especially contests

5.2 When to Use FT8

FT8 is the better choice in most situations:

  • Weak-signal DX: FT8’s ~3.5 dB sensitivity advantage over FT4 means it can decode signals that FT4 cannot. On marginal paths (e.g., low-power to distant continents), FT8 is more likely to succeed.
  • General daily operation: FT8 has far more activity worldwide, so you will find more stations to work, especially on less popular bands.
  • New operators: The 15-second slot gives you more time to observe and react. Recommended for your first contacts.
  • Challenging conditions: During solar minimum, on higher bands with marginal propagation, or when running low power (QRP), FT8’s extra sensitivity matters.

5.3 When to Use FT4

FT4 excels in specific scenarios:

  • Contests: FT4 was specifically designed for contesting. Its 7.5-second slots allow twice the QSO rate compared to FT8. Many digital contests (e.g., ARRL Digital Contest, WW Digi DX Contest) include FT4 categories.
  • Band openings: When a band opens briefly (e.g., sporadic E on 6m or 10m), FT4’s faster cycle lets you work more stations before the opening closes.
  • POTA/SOTA activations: If you are activating a park or summit and want to log contacts quickly, FT4’s faster turnaround helps you work through a pileup more efficiently.
  • Strong signals: When signals are strong (above ~-10 dB), FT4’s reduced sensitivity is not a limitation, and the speed advantage is pure benefit.
In FT HAM, switching between FT8 and FT4 is instant: go to Configuration → Mode and Frequency and tap the mode picker. The waterfall, timing engine, decoder, and expected dial frequency all adjust automatically. Your CQ modifier, callsign, and other settings carry over.

5.4 Standard Dial Frequencies — FT8 vs FT4

FT8 and FT4 use different dial frequencies within each band. This separation prevents the two modes from interfering with each other. Make sure your transceiver is tuned to the correct frequency for the selected mode:

Band FT8 Dial Freq FT4 Dial Freq
160m1.840 MHz1.840 MHz
80m3.573 MHz3.575 MHz
40m7.074 MHz7.0475 MHz
30m10.136 MHz10.140 MHz
20m14.074 MHz14.080 MHz
17m18.100 MHz18.104 MHz
15m21.074 MHz21.140 MHz
12m24.915 MHz24.919 MHz
10m28.074 MHz28.180 MHz
6m50.313 MHz50.318 MHz
Don’t mix them up! If you’re in FT4 mode but your radio is tuned to the FT8 frequency (or vice versa), you will decode the wrong mode’s signals and your transmissions will land in the wrong sub-band. FT HAM shows the expected dial frequency for the selected band and mode in Configuration.

5.5 Band Activity by Time of Day

HF propagation depends on time of day, season, and solar activity. Here is a general guide to help you choose the right band:

Time PeriodBest FT8 BandsNotes
Sunrise ± 1 hour40m, 30m, 20mGrey-line propagation; excellent for DX on 40m and 30m
Morning (local)20m, 17m, 15mHigher bands open as the ionosphere builds; 20m is always a safe bet
Midday20m, 15m, 12m, 10mPeak F2-layer ionization; higher bands may open during high solar activity
Afternoon20m, 17mHigher bands begin closing; 20m remains reliable until sunset
Sunset ± 1 hour20m, 40mGrey-line again; transition to nighttime bands
Evening40m, 80mLower bands dominate as the ionosphere weakens
Night80m, 160m, 40m40m provides continental/intercontinental distances; 80m and 160m for shorter paths
Solar activity matters. During solar maximum (e.g., Solar Cycle 25 peak around 2024–2025), bands like 10m, 12m, and 15m are frequently open with excellent worldwide propagation. During solar minimum, these bands may be largely silent and you should focus on 20m and below.

6. Troubleshooting & FAQ

Solutions to common issues, diagnostic steps, and answers to frequently asked questions about FT HAM operation.

6.1 Common Issues

6.2 General FAQ

7. Advanced Settings

Fine-tune FT HAM’s behavior for different operating scenarios. All settings are accessed from the Configuration tab (gear icon). This section documents every available option.

7.1 Transmission Controls

Hold TX Frequency

When enabled, FT HAM keeps your transmit frequency offset fixed even when replying to a station on a different frequency. This is useful in pileup situations where a DX station may be listening on a specific frequency and you want to stay there. When disabled (default), the app automatically matches the DX station’s frequency offset when you swipe to reply.

When to use: Enable Hold TX when answering a DX station that is calling “CQ UP” or when you want to maintain a specific clear frequency in a crowded band segment. Disable it (default) for normal QSOs.

Even/Odd Cycle Override

Manually force transmission on even slots (0s/30s past the minute) or odd slots (15s/45s). By default, FT HAM selects the correct cycle automatically based on the QSO context—the station answering always transmits on the opposite slot from the station calling CQ.

When to use: Override this only if auto-detection places you on the wrong cycle (rare), or if you want to deliberately synchronize with a specific station. In normal operation, leave the automatic mode.

Message Selector (Manual Mode)

When auto-sequencing is disabled, use the < and > buttons next to the message display to manually cycle through the six standard message types:

IndexMessage TypeExamplePurpose
0CQCQ EA1ABC IN73Call CQ to invite contacts
1GridEA4IQL EA1ABC IN73Reply to CQ with your grid
2Signal ReportEA1ABC EA4IQL -08Send signal report
3R + ReportEA4IQL EA1ABC R-12Acknowledge + your report
4RRREA1ABC EA4IQL RRRConfirm report received
573EA4IQL EA1ABC 73Sign off with best regards

Manual mode gives you full control over which message is sent in each slot. This is useful for advanced operators who want to handle non-standard situations, such as resending a report the other station missed without advancing to the next step.

7.2 CQ Modifiers

CQ modifiers add a keyword to your CQ call that tells other stations what kind of contact you are looking for. The modifier replaces the space after CQ with a directed tag. Access them in Configuration → CQ Modifier.

Geographic Modifiers

Target stations from a specific region or continent:

ModifierMeaningCQ Message Example
DXLooking for long-distance contacts (not your own continent)CQ DX EA1ABC IN73
EULooking for European stationsCQ EU EA1ABC IN73
NALooking for North American stationsCQ NA EA1ABC IN73
SALooking for South American stationsCQ SA EA1ABC IN73
AFLooking for African stationsCQ AF EA1ABC IN73
ASLooking for Asian stationsCQ AS EA1ABC IN73
OCLooking for Oceanian stationsCQ OC EA1ABC IN73
ANTLooking for Antarctic stationsCQ ANT EA1ABC IN73
DX is the most commonly used geographic modifier. When you call CQ DX, nearby stations on the same continent generally understand that you are not looking for them and will not reply. This is a convention, not enforced by the protocol.

Activation Modifiers

Signal that you are activating a location for a specific program. When you select an activation modifier, FT HAM also shows a reference field where you can enter the program-specific park/summit/island/flora reference number. This reference is stored with your logged QSOs and included in the ADIF export.

ModifierProgramReference FormatReference Example
POTAParks on the AirXX-NNNNK-1234, EA-0102
SOTASummits on the AirXX/YY-NNNEA4/MD-001, W7W/KG-049
WWFFWorld Wide Flora & FaunaXXFF-NNNNEAFF-0123, KFF-4567
IOTAIslands on the AirXX-NNNEU-005, NA-043

The reference number you enter appears in the MY_SIG_INFO field of the ADIF export, which is the standard field recognized by POTA, SOTA, WWFF, and IOTA for crediting activations and hunter contacts.

Important for activators: Make sure your reference number is entered correctly before starting your activation. All QSOs logged while the modifier and reference are set will include this information in the ADIF export. You can verify the reference in the Logbook by checking the details of your logged QSOs.

Custom Modifier (OTHER)

Select OTHER to enter any custom text as your CQ modifier. This is useful for special events, contests, or non-standard programs. For example: CQ TEST EA1ABC IN73 for contest operation, or CQ FIELD EA1ABC IN73 for ARRL Field Day.

7.3 Auto-Sequencing Options

Auto Sequencing (default: on)

When enabled, FT HAM automatically selects the next appropriate message in the QSO exchange after receiving a response. The standard sequence is: CQ → Grid → Report → R+Report → RRR/RR73 → 73. Each received message triggers the next outgoing message without user intervention.

When to disable: Turn this off if you want full manual control over message selection, for example when experimenting, training, or handling non-standard situations.

Auto CQ Reply (default: off)

When enabled, FT HAM automatically replies to the first CQ call it decodes from another station, without waiting for you to swipe. This effectively makes the app a fully automatic QSO machine: it listens for CQs, replies, completes the exchange, logs the QSO, and starts listening again.

When to use: Contest-like operation where you want maximum QSO rate with minimal interaction. Use with caution—you may end up working stations you didn’t intend to.

Auto CQ Reply — Only New Band/Mode (default: off)

When combined with Auto CQ Reply, FT HAM only replies to stations you haven’t already worked on the current band and mode. This prevents duplicate QSOs and is essential for award hunting (e.g., working all states, all DXCC entities).

Max Retry Slots (default: 3)

Controls how many times FT HAM repeats the current message if no response is received. After this many consecutive unanswered transmissions, the QSO is marked as a timeout and FT HAM returns to idle state.

ValueTimeout Duration (FT8)Best For
2~30 secondsFast operation on strong signals
3 (default)~45 secondsNormal operation
5~75 secondsWeak-signal DX with QSB fading
8–10~2–2.5 minutesVery difficult paths (e.g., moonbounce-like conditions)

Include Grid in CQ (default: on)

When enabled, your CQ messages include your Maidenhead grid locator: CQ EA1ABC IN73. This allows stations hearing your CQ to see your approximate location before deciding to reply.

When disabled, CQ messages are shorter: CQ EA1ABC. Some operators disable this for brevity, but including the grid is recommended because it gives replying stations useful propagation information.

7.4 QSO Logging Options

Auto QSO Logging (default: on)

When enabled, completed QSOs are automatically added to the logbook as soon as the final message (RR73 or 73) is received. When disabled, a confirmation dialog appears after each QSO, letting you review the details before saving or discarding.

Tip: Leave this on for operating efficiency. You can always delete unwanted QSOs from the logbook later.

Decode Self TX Messages (default: off)

When enabled, your own transmitted messages also appear in the RX message list, decoded from the generated audio. This is useful for verifying that your messages look correct and that the encoder is working properly. In normal operation, leave this off to keep the RX list clean.

7.5 Frequency Offset

The frequency offset (0–3000 Hz) determines where within the FT8/FT4 audio passband your signal is placed. Your actual transmitted RF frequency equals:

RF frequency = Dial frequency + Audio offset

For example: dial 14.074000 MHz + offset 1500 Hz = RF signal at 14.075500 MHz.

You can set the offset three ways:

  • Slider in Configuration → Mode and Frequency — drag for quick approximate positioning
  • Text field for precise numeric entry (displayed in kHz with decimal precision)
  • Tap the waterfall to visually select a clear frequency — the offset jumps to wherever you tap, and a cursor line shows the current position
Finding a clear frequency: Look at the waterfall for gaps between bright signal traces. Tap in a gap to place your transmit frequency there. An overlap with another station’s signal will cause mutual interference (QRM) and both signals may fail to decode.

7.6 ADIF Export Options

FT HAM stores your log internally and exports in ADIF 3.1.4 format. When you tap Export in the Logbook tab, you choose which contacts to include:

Export ScopeDescriptionBest For
AllExport your complete logbookFull backup, initial upload to LoTW/QRZ
Date RangeExport QSOs between custom start and end datesExpedition logs, contest submissions
Recent (7 days)Export only the last 7 days of contactsQuick weekly sync
Since Last ExportExport only QSOs made since your last successful exportIncremental updates—avoids duplicate uploads

The exported file is named FT_HAM_Log_[date_time].adif and can be shared via AirDrop, email, iCloud Drive, Files, or any other iOS share target.

ADIF Fields Included

Each ADIF record contains the following fields:

ADIF FieldContent
CALLDX station’s callsign
GRIDSQUAREDX station’s Maidenhead locator
QSO_DATE / TIME_ONDate and time (UTC) the QSO started
FREQFrequency in MHz (dial + offset)
MODEFT8 or FT4
BANDBand designation (e.g., 20m)
RST_SENTSignal report you sent (e.g., -08)
RST_RCVDSignal report you received (e.g., +05)
STATION_CALLSIGNYour callsign (the operator)
MY_GRIDSQUAREYour Maidenhead locator
MY_SIGActivation program (e.g., POTA, SOTA)
MY_SIG_INFOActivation reference (e.g., K-1234)
COUNTRYDX station’s country (auto-detected from callsign prefix)
[Figure 11: ADIF export options in the Logbook tab]

7.7 Interface Preferences

View Mode

Choose between Vertical, TX/RX Separated, or Condensed layouts for the TX/RX tab. Each emphasizes different information—see Section 2.3 for detailed descriptions and use cases.

Map Display Toggles

In the Map tab, toggle visibility of display elements to customize the map:

ToggleDefaultEffect
Grid linesOnShow/hide Maidenhead grid square boundaries
Country circlesOnShow/hide circles around contacted countries
Geodesic pathsOnShow/hide great-circle path lines from your location to each contact
Callsign labelsOffShow/hide callsign text annotations on the map pins

Auto RX at Start (default: off)

When enabled, FT HAM starts listening automatically when you open the app, without needing to tap Listen. Useful for stations that operate frequently and want to start decoding immediately upon launch.

8. Online Integrations & Log Sync

FT HAM integrates with online ham radio services in three ways: live reporting (PSK Reporter), direct premium log syncing (QRZ/LoTW/eQSL), and universal ADIF export for every other workflow.

8.1 PSK Reporter (Premium)

PSK Reporter is a free, crowd-sourced, real-time propagation monitoring network run by Philip Gladstone (N1DQ). When enabled in FT HAM Premium, every FT8/FT4 signal you decode is automatically reported to the PSK Reporter server. Thousands of stations worldwide contribute reports, creating a continuously updated global map of who is hearing whom on the HF and VHF bands.

Why this matters for you: PSK Reporter lets you see the actual reach of your station in near real-time, without making a single QSO. You can spot openings to new continents, troubleshoot antenna problems, compare antennas objectively, and confirm that your transmissions are actually reaching distant stations before committing to a QSO attempt.

Enabling PSK Reporter in FT HAM

1

Go to Configuration (gear icon, last tab in the tab bar).

2

Scroll down to the Behavior section and locate the PSK Reporter toggle. If you have not yet unlocked Premium, the toggle will appear dimmed and disabled. Unlocking Premium via the in-app purchase activates it.

3

Enable the PSK Reporter switch. No account, API key, or registration is required. FT HAM immediately begins collecting decoded reception reports in the background.

4

Reports are automatically batched and sent in bulk every 5 minutes. This minimizes network traffic and battery impact while keeping the propagation map reasonably current. You do not need to take any further action.

5

Check your reports: Open a browser and go to pskreporter.info/pskmap.html. In the “Receiver” field, type your callsign and click the map. You will see a map with lines reaching from your location to every station you have decoded recently. The longer the lines, the better the propagation.

6

Check who is hearing you: In the PSK Reporter map, set your callsign in the “Sender” field to see which stations have decoded your transmissions. This only works when you are actively transmitting, so call CQ or reply to stations while a browser tab with PSK Reporter is open on a second device.

What each PSK Reporter report contains

Each reception report is a lightweight record sent to the PSK Reporter server. No audio, raw signal data, personal information, or location coordinates are transmitted.

Data FieldContentExample
Sender callsignThe callsign of the station whose signal was decodedK5XYZ
Receiver callsignYour callsign (the station running FT HAM)EA4IQL
Receiver locatorYour Maidenhead grid locator (4 characters from your station settings)IN80
FrequencyExact frequency in Hz (dial frequency + audio offset)14075500
ModeFT8 or FT4FT8
SNRSignal-to-noise ratio in dB as measured by the FT8/FT4 decoder-12

Practical uses of PSK Reporter with FT HAM

Use caseHow to do it
Real-time band checkStart listening on a band. After a few cycles, check PSK Reporter as receiver to see if that band is actually open to your target region.
Antenna comparisonListen for 30 minutes with antenna A, then switch to antenna B and listen another 30 minutes. Compare the PSK Reporter coverage maps to see which antenna hears more stations in which directions.
TX reach verificationCall CQ a few times, then check PSK Reporter as sender. If no one is hearing you in a specific direction, signals may not be reaching there. Check your antenna, power level, and band choice.
Grey-line spottingDuring sunrise and sunset, watch PSK Reporter in real time to spot rare paths opening on 40m and 80m.
New entity alertingPSK Reporter shows entity flags. If you see a flag from a rare DXCC entity you haven’t worked, switch to that band immediately and look for their CQ call in FT HAM.
Antenna testing tip: PSK Reporter is the best free tool for objective antenna comparison under real propagation conditions. Unlike SWR or gain measurements, it tells you what stations in the real world are actually hearing from your location.
PSK Reporter requires an internet connection to submit reports. If you are operating completely offline (no Wi-Fi, no cellular), reports are held in memory and sent automatically as soon as connectivity is restored. No reports are lost.

8.2 Direct Log Sync (Premium): QRZ, LoTW, eQSL

FT HAM Premium includes direct QSO synchronization with three online logbook services. Once configured, new contacts upload automatically the moment they are logged — no manual exporting needed. All settings are under Configuration → Log Syncing. All credentials are stored in the iOS Keychain, never in plain app storage.

ServiceCredentials neededConfirmation polling
QRZ LogbookQRZ API keyYes — configurable interval
LoTW.p12 certificate + certificate password; LoTW account callsign + passwordYes — configurable interval
eQSL.cceQSL callsign + eQSL passwordNo — check manually at eqsl.cc

8.2a — QRZ Logbook

QRZ.com is the world’s largest amateur radio database. The QRZ Logbook is a free online log tied to your QRZ callsign page. When you upload a QSO, it appears on your public profile and can be checked for confirmations. An XML Data subscription is not required for logbook uploads — only a free QRZ.com account.

Step 1: Get your QRZ Logbook API key

1

Log into your account at qrz.com. If you don’t have one, register for free.

2

Navigate to Logbook (top menu) → Logbook Settings → scroll to the API Keys section near the bottom.

3

Click Generate API Key. QRZ will create a long alphanumeric string (example: ABC1-D2EF-3GH4-5678). This key authorises FT HAM to upload QSOs on your behalf.

4

Copy the key to your clipboard. If you are on a Mac/PC browsing QRZ, use AirDrop or iCloud Clipboard to transfer it to your iPhone/iPad, or simply email it to yourself and open the email on your device.

Step 2: Configure QRZ Logbook in FT HAM

1

In FT HAM, go to Configuration → scroll down to Log Syncing → tap QRZ Logbook.

2

Tap Add QRZ API Key. A secure entry sheet appears.

3

Paste your API key into the secure field. The field masks what you type, just like a password. Tap Save. FT HAM validates the key with QRZ and stores it in your device’s Keychain.

4

Once a valid key is stored, a green "API key stored in Keychain" indicator appears. The auto-upload toggle and confirmation interval picker become active.

5

Enable Auto-upload on QSO log. From this point on, every completed QSO is automatically uploaded to your QRZ Logbook immediately after logging.

6

Set your preferred Confirmation check interval. Available options: 1 h, 3 h, 6 h (default), 12 h, 24 h. FT HAM will periodically query QRZ to see whether the other station has also logged the QSO, marking it as confirmed. A shorter interval gives you faster feedback; a longer interval reduces API traffic.

Understanding the QRZ sync status indicators

IndicatorMeaning
✓ ReadyAPI key is valid and QRZ is reachable. Everything is working normally.
Syncing…An upload or confirmation check is in progress right now.
⚠ error messageThe last sync attempt failed. Typical causes: wrong API key, QRZ service outage, or no internet connection.
N QSO(s) pending uploadN QSOs are in the retry queue. They will upload automatically when connectivity is restored or the error is resolved.
If you change your QRZ API key (e.g., you rotated it for security), tap Remove in the QRZ settings and add the new key again. Old pending uploads will retry with the new key.
Do not share your QRZ API key. It grants full read/write access to your QRZ Logbook. If you believe a key has been compromised, revoke it on qrz.com and generate a new one.

8.2b — LoTW (Logbook of The World)

Logbook of The World (LoTW) is operated by ARRL (the American Radio Relay League) and is the premier QSO confirmation service for award chasing (DXCC, WAS, VUCC, etc.). LoTW uses a digital certificate (PKI) to cryptographically sign each log upload, proving that you are the licensed holder of your callsign. This signature is what makes LoTW confirmations trustworthy for award credit.

The certificate chain requires two steps to set up: (1) obtaining a Logbook of The World certificate via ARRL’s TQSL program, and (2) importing that certificate into FT HAM as a .p12 file. This is a one-time process.

Step 1: Get a LoTW certificate (TQSL)

If you have never used LoTW before, you need to request a certificate from ARRL. This is a manual process that takes 1–5 days as ARRL verifies you hold the callsign.

1

Download TQSL (Trusted QSL) from lotw.arrl.org and install it on a Windows, macOS, or Linux computer. TQSL is the official certificate manager for LoTW — it is free.

2

In TQSL, go to Callsign Certificates → Request New Callsign Certificate. Enter your callsign, name, address, and email. ARRL will send you an email with a certificate activation link.

3

Once you receive the confirmation email, click the link or follow the instructions to activate your certificate in TQSL. Your certificate now appears in TQSL under Callsign Certificates.

4

If you have used LoTW before and already have a certificate in TQSL, skip to the next step.

Step 2: Export your certificate as a .p12 file

1

In TQSL, select your callsign certificate and go to Callsign Certificates → Save Callsign Certificate (the exact menu path may be Export or Backup in some TQSL versions).

2

Save the file in .p12 format (also sometimes shown as .pfx — they are the same format). TQSL will ask you to set a password to protect the exported certificate. Choose a strong password and remember it — you will need it when importing into FT HAM.

3

Transfer the .p12 file to your iPhone/iPad. Options:

  • AirDrop: On your Mac, right-click the .p12 file → Share → AirDrop → select your iPhone/iPad. Accept on iOS. The file lands in the Files app.
  • iCloud Drive: Copy the .p12 file to iCloud Drive in a folder on your Mac. Open the Files app on your iPhone/iPad → navigate to iCloud Drive → your file appears there.
  • Email to yourself: Attach the .p12 to an email and open the attachment on your iPhone/iPad. Tap “Save to Files” to keep it accessible.

Step 3: Import the certificate into FT HAM

1

In FT HAM, go to Configuration → Log Syncing → LoTW.

2

Tap Import .p12 Certificate. The Files picker opens. Navigate to where you saved the .p12 file (iCloud Drive, On My iPhone, etc.) and select it.

3

FT HAM shows an alert asking for the certificate password. Enter the password you set in TQSL when you exported the .p12. Tap Import. FT HAM decrypts the certificate and stores it securely in the iOS Keychain. The .p12 file on your device is no longer needed and can be deleted.

4

A green "Certificate stored in Keychain" indicator confirms successful import.

Step 4: Add your LoTW account credentials

The certificate handles signing uploads. FT HAM also needs your LoTW account login to submit the signed log and to check confirmations.

1

In the LoTW settings section, tap Add LoTW Account Credentials.

2

Enter your LoTW callsign and your LoTW website password (the password you use to log into lotw.arrl.org). These are stored securely in the Keychain.

3

A green "Account credentials stored in Keychain" indicator confirms the credentials are saved. The confirmation interval picker becomes active; set your preferred polling interval (1 h, 3 h, 6 h, 12 h, or 24 h).

Step 5: Enable auto-upload

1

Enable Auto-upload on QSO log. FT HAM will now cryptographically sign each new QSO with your callsign certificate and upload it to LoTW automatically after logging.

How LoTW QSO signing works in FT HAM

When a QSO is uploaded to LoTW, FT HAM performs the signing step that TQSL normally does on a desktop:

  1. The QSO details (callsign, date/time, band, mode, frequency) are formatted as a signed ADIF record.
  2. The record is cryptographically signed using the private key stored inside your .p12 certificate, proving that the upload comes from the holder of that callsign’s certificate.
  3. The signed data is submitted to the LoTW server via HTTPS.
  4. When the other station uploads their side of the QSO and the details match (callsign, date/time within ±30 seconds, band, mode), LoTW marks both QSOs as confirmed, which can count toward DXCC and other ARRL awards.
Award credit timing: LoTW confirmations are not instant. The other station must also upload their log for a match to occur. Check your LoTW account on the web periodically, or wait for FT HAM’s automatic confirmation polling to catch new matches.
Certificate expiry: LoTW callsign certificates expire (typically after 1 year, or whenever your license renewal date requires). When your certificate expires, you will need to renew it through TQSL and re-export/re-import the .p12 into FT HAM. FT HAM will show an upload error when the certificate has expired.

8.2c — eQSL.cc

eQSL.cc is an electronic QSL card exchange network. When you upload a QSO, the other station receives a digital QSL card. eQSL confirmations count toward several award programs (eQSL’s own awards, WAS eQSL, etc.) and are a popular alternative or supplement to LoTW. Unlike LoTW, eQSL does not require a certificate — only a free account login.

Step 1: Create an eQSL account (if needed)

1

If you don’t already have an eQSL account, visit eqsl.cc from a browser and create a free account. Your eQSL username is your callsign.

2

Make note of your eQSL callsign and password. These are what you will enter in FT HAM.

Step 2: Configure eQSL in FT HAM

1

In FT HAM, go to Configuration → Log Syncing → eQSL.

2

Tap Add eQSL Credentials. A sheet appears with two fields:

  • Callsign — your eQSL.cc username (your callsign, uppercase)
  • eQSL Password — your eQSL.cc login password
3

Fill in both fields and tap Save. FT HAM stores them in the iOS Keychain. The green "Credentials stored in Keychain" indicator confirms success.

4

Enable Auto-upload on QSO log. FT HAM will upload each new QSO to eQSL immediately after it is logged.

Checking eQSL confirmations

eQSL does not provide an API for automated confirmation polling, so FT HAM cannot check confirmations automatically. To see your received eQSL cards, log in at eqsl.cc in a browser and navigate to Inbox → Unacknowledged Incoming eQSLs. When a station you worked also uploads their QSO, their eQSL card appears here.

eQSL has two membership levels: regular and Authenticity Guaranteed (AG). AG members have been validated by eQSL and their cards count toward the most prestigious awards. If award credit matters to you, check whether the other station is AG before counting the confirmation.

8.2d — How the Sync Engine Works

FT HAM includes a LogSyncManager that coordinates uploads across all three services. Understanding how it works helps you diagnose issues and manage your log efficiently.

Upload flow (per QSO)

  1. A QSO is completed and logged (either automatically or confirmed by you).
  2. The QSO is added to the pending queue for each enabled service (QRZ, LoTW, eQSL).
  3. FT HAM immediately attempts to upload the QSO to each service. If successful, the QSO is removed from the pending queue for that service.
  4. If an upload fails (network error, service timeout, invalid credentials), the QSO stays in the pending queue. FT HAM automatically retries pending uploads in the background whenever the app is active and an internet connection is available.
  5. The pending count displayed in each service’s settings section shows how many QSOs are waiting to be uploaded.

Confirmation polling

For QRZ and LoTW, FT HAM runs a background timer. Every N hours (your configured interval), it queries each service for updated confirmation status on your recent QSOs. New confirmations are noted in the service’s response. eQSL has no confirmation API — check eqsl.cc manually.

Credentials security

ServiceWhat is stored in KeychainWhat is never stored
QRZ LogbookQRZ API keyYour QRZ password
LoTWCertificate private key (from .p12), LoTW account callsign and passwordThe original .p12 file (can be deleted once imported)
eQSL.cceQSL callsign and password—

The iOS Keychain encrypts all stored secrets using hardware-backed AES encryption. Data stored in the Keychain is isolated per app and cannot be read by other apps or extracted via iTunes/Finder backup (unless the backup itself is encrypted and you own the encryption key).

Troubleshooting sync errors

Best practice: Configure all three services (QRZ, LoTW, eQSL) for maximum coverage of your log, and keep the ADIF export as a periodic backup. In the unlikely event of a service outage or credential issue, your local logbook is always intact and you can export ADIF to upload manually.

8.3 Using Your ADIF Export with Third-Party Services

FT HAM exports contacts in ADIF 3.1.4, accepted by virtually every ham radio service and logging program. ADIF remains the universal path for services that are not configured for direct premium sync.

To upload your contacts to any of these services:

1

Export your log from FT HAM. Go to the Logbook tab → tap Export → select the scope (All, Since Last Export, etc.) → share the generated .adif file via AirDrop, email, iCloud Drive, or Files.

2

Upload the .adif file to the service of your choice using its own website or companion software. Each service has its own import/upload page.

Popular services that accept ADIF

ServiceNotes
Logbook of The World (LoTW)Operated by ARRL. Requires signing the ADIF with TQSL before upload. Free.
QRZ.comImport via the Logbook section on qrz.com. Some features require an XML Subscription.
Club LogFree DX analysis and DXCC tracking. Upload at clublog.org.
eQSL.ccElectronic QSL card exchange. Upload your ADIF on the eQSL website.
Best practice: Use FT HAM’s “Since Last Export” scope when exporting regularly. This avoids duplicate uploads and keeps your external logs synchronized incrementally.
Pro tip: Some desktop logging apps (e.g., Log4OM, MacLoggerDX) can import ADIF and then automatically upload to LoTW, QRZ, Club Log, and eQSL in one step. If you regularly transfer your FT HAM log to a desktop app, you can centralize all uploads there.

9. Glossary

Key terms used throughout this guide and in amateur radio digital mode operation.

Term Definition
73 Ham radio shorthand for “best regards.” Used as a courteous sign-off at the end of a contact. In FT8, the 73 message signals that the QSO exchange is complete.
ADIF Amateur Data Interchange Format — a standard file format (.adif) for exchanging log data between ham radio software and online services. FT HAM exports logs in ADIF 3.1.4 format.
Auto Sequencing An FT HAM feature that automatically advances through the standard FT8/FT4 message exchange without manual intervention. Each decoded reply triggers the next outgoing message.
Band A range of radio frequencies allocated for amateur use. Named by approximate wavelength (e.g., “20m” refers to the 14 MHz band, where the radio wavelength is approximately 20 meters).
Callsign A unique identifier assigned by a national authority to a licensed amateur radio operator (e.g., EA4IQL is Spanish, W1AW is American). Required for legal transmission.
CAT Computer Aided Transceiver — a protocol for controlling a radio transceiver from a computer or mobile device over a serial or network connection. Used in FT HAM to set frequency, switch bands, and toggle PTT remotely via the rigctld protocol.
CQ “Calling any station.” A general-purpose call inviting any station to respond and start a QSO. The term comes from the French sécurité.
CQ Modifier A keyword added after CQ to indicate the type of contact desired (e.g., CQ DX for long distance, CQ POTA for Parks on the Air).
Dial Frequency The frequency displayed on your transceiver’s dial. In FT8/FT4, the actual signal frequency is the dial frequency plus an audio offset (0–3000 Hz).
DX Long-distance communication, or a distant station. In FT8, “CQ DX” signals that you are looking for stations on other continents.
FT4 A weak-signal digital mode with 7.5-second transmission slots, designed for faster QSOs and contesting. Uses 4-GFSK modulation.
FT8 A weak-signal digital mode with 15-second transmission slots, created in 2017 by K1JT and K9AN. Uses 8-GFSK modulation and can decode signals as weak as -21 dB SNR. The most widely used amateur digital mode.
GFSK Gaussian Frequency-Shift Keying — the modulation scheme used by FT8 (8 tones) and FT4 (4 tones) to encode data into audio tones.
Grid Locator A Maidenhead grid square that encodes a geographic position into a compact 4- or 6-character code (e.g., IN80 = Madrid area). Used in FT8/FT4 exchanges to share your approximate location.
IOTA Islands on the Air — an award program for contacting or activating islands. References use the format XX-NNN (e.g., EU-005).
LDPC Low-Density Parity-Check code — a forward error correction code used in FT8 and FT4 that enables reliable decoding of very weak signals.
Offset The audio frequency (in Hz) within the 0–3000 Hz passband where your FT8/FT4 signal is placed, relative to the dial frequency. Also called “DF” (delta frequency) or “audio frequency.”
POTA Parks on the Air — an award program for activating and contacting stations in designated parks. References use the format XX-NNNN (e.g., K-1234).
PSK Reporter A real-time, crowd-sourced propagation monitoring network. Software like FT HAM automatically uploads decoded reception reports, contributing to a global map of who is hearing whom. Visit pskreporter.info to view the map.
PTT Push-To-Talk — the mechanism that switches a transceiver between receive and transmit. In FT HAM, PTT is triggered by VOX (the radio detects outgoing audio tones and keys automatically).
QRM Man-made interference from other stations transmitting on or near the same frequency.
QRP Low-power operation, typically 5 watts or less on HF. FT8’s sensitivity makes QRP contacts feasible even on intercontinental paths under favorable conditions.
QSB Signal fading — fluctuations in signal strength caused by changes in ionospheric propagation.
QSO A completed two-way contact between two amateur radio stations. In FT8, a QSO consists of a structured 5-message exchange.
RR73 An FT8 message meaning “roger, best regards” — sent by the station that called CQ to confirm that the QSO is complete.
RRR An FT8 message meaning “roger roger roger” — confirms the signal report was received.
rigctld A network daemon from the Hamlib project that exposes transceiver control (CAT) over TCP/IP. FT HAM connects to rigctld to remotely set frequency, switch bands, and toggle PTT.
SNR Signal-to-Noise Ratio, measured in decibels (dB) in a 2500 Hz reference bandwidth. Indicates how strong a signal is relative to background noise. FT8 can decode down to -21 dB.
SOTA Summits on the Air — an award program for activating mountain summits. References use the format XX/YY-NNN (e.g., EA4/MD-001).
USB Upper Sideband — the modulation mode that must be used on your transceiver for FT8 and FT4, regardless of band. Some radios call it DATA-USB or DIG-U.
UTC Coordinated Universal Time — the global time standard used in amateur radio. FT8/FT4 timing is always referenced to UTC. iOS synchronizes your device to UTC via NTP.
VOX Voice-Operated Switch — a transceiver feature that automatically keys the transmitter when audio is detected at the microphone input. FT HAM relies on VOX to trigger transmission when it plays FT8/FT4 audio tones.
Waterfall A spectrogram display showing radio signals as colored bands scrolling over time. Horizontal axis = frequency (0–3000 Hz offset), vertical axis = time. Bright areas indicate signal activity at that frequency.
WWFF World Wide Flora & Fauna — an international award program for activating nature areas. References use the format XXFF-NNNN (e.g., EAFF-0123).

FT HAM User Guide — Version 1.2 — April 2026
ftham.turrion.dev  ·  How FT8/FT4 works in FT HAM  ·  Privacy  ·  Terms

73 de EA4IQL