WSJT-X for field activations

WSJT-X runs FT8, FT4, and related weak-signal modes. For POTA it is a contact engine when propagation or power is marginal — not a replacement for spotting and park references in your log.

Fake it till you make it: do not spend the first activation making WSJT-X into a POTA logger. Run FT8, log QSOs in WSJT-X, keep Polo (or N3FJP) as the master for SSB/CW, then split the files and merge in ADIF Doctor at close-out. Stamp MY_SIG_INFO, explode 2-fers, export the POTA pack, then Recap from Full ADIF.

Sources: POTA digital modes guide · WSJT-X home

Split logs, then Doctor (activation close-out)

WSJT-X’s wsjtx_log.adi is a sitting file, not a pota.app upload. Polo’s POTA export is a different sitting file. Uploading both without merging is how you get dupes, missing parks, and a Recap map with no grids.

  1. Stop WSJT-X. Keep the renamed archive (20250831-us1412-wsjtx.adi) plus Polo Full (grids) and Polo POTA (privacy strip).
  2. Drop Full + WSJT ADIF on ADIF Doctor → merge (physical de-dupe). Stamp call / park / grid if empty.
  3. Explode comma 2-fers if Doctor says so.
  4. Download the POTA pack (no grids) for pota.app. Download Full for Recap / LoTW / AC Log.
  5. Recap → Open Recap with Full (or paste Full). Never feed Recap the POTA export.

Phone-only FT8 (no Polo rows) still needs park tags. Doctor can stamp MY_SIG_INFO on the WSJT file. Confirm a test QSO in a text editor (MY_SIG_INFO, <EOR>) before you trust the first upload.

Before you leave home

  1. Install and update WSJT-X. Back up wsjtx_log.adi.
  2. Fresh log for the activation: stop WSJT-X, rename wsjtx_log.adi to something like 20250831-us1412-wsjtx.adi, restart. WSJT-X creates a clean log so “worked before” reflects this outing only.
  3. Configurations: WSJT-X → File → Save new configuration per vehicle/rig (POTA-truck, POTA-summit). Store rig CAT, audio device, and grid per profile.
  4. Settings → General: callsign, My Grid = this activation’s 6-character Maidenhead (from your field sheet), not home.
  5. Tx macros: add CQ POTA YOURCALL FN31ab (adjust grid) for the Tx #5 slot or custom macros.

Rig and audio

Test at home: one QSO on each band you plan to use. Confirm frequency readout matches the VFO.

Time sync in the field

FT8 fails silently when the clock drifts.

MethodNotes
GPS + PPS dongleBest for no-cell sites; BktTimeSync or vendor tool
Internet via phone hotspotQuick check: decode others before you TX
WSJT-X “Sync PC clock to GPS”When GPS hardware is present

If nobody decodes and you decode nobody, fix time before chasing RFI gremlins.

Activating with FT8

Frequency and clearance

Listen on the waterfall. Pick a clear slice. Do not transmit on top of an existing QSO.

POTA official guidance: use split behavior — activator on one frequency, hunters on another slot in the waterfall. In WSJT-X, Hold Tx Freq lets you park your TX on an open offset while decoding CQers elsewhere. Fake It / Rig (above) keeps that TX audio clean. Do not confuse the two: Fake It is the radio; Hold Tx Freq is the waterfall.

Do not put K-1234 in the comment in 2026. Current US references are US-####. The comment field is still free text — US-1412 or POTA US-1412. Spot the dial frequency (e.g. 14.074), not 14.074 plus the audio offset.

Calling CQ

  1. Set mode FT8 (or FT4 for faster pileups — harsher on timing).
  2. Enter your park reference in the free-text / comment field — WSJT-X has no dedicated POTA field. Example: US-1412 (not a stale K- number).
  3. Optional Tx macro: CQ POTA YOURCALL US-1412
  4. Enable TX, watch the waterfall fill.
  5. Spot on pota.app with exact dial frequency and mode FT8. Refresh the spot every ~30 minutes or after QSY.

Warning: Do not spot a frequency you are not on. Do not use terrestrial repeaters. WSJT-X does not exempt you from QRL? and band plans.

Working hunters

P2P on FT8

When both stations are in the field, park references belong in the exchange or comment field. Log their reference in SIG_INFO / Polo’s their-park field on that QSO. See ADIF parks.

Hunting with FT8

From the POTA hunter guide:

UDP and downstream loggers

Settings → Reporting → UDP Server:

GridTracker, JTAlert, and tools like Potatui ingest this stream. See GridTracker and JT Alert.

For Polo-centric workflows, many activators still hand-enter or import from WSJT-X ADIF at end of day — verify MY_SIG_INFO before upload.

End of activation

Follow Split logs, then Doctor. Short version:

  1. Export / archive the WSJT ADIF.
  2. Merge into Polo Full (or stamp the WSJT file) in ADIF Doctor.
  3. Upload the POTA pack to pota.app if activating.
  4. Recap from Full. Hunters: LoTW/QRZ if you chase awards — POTA hunter credit is activator-log-based.

Troubleshooting

SymptomLikely cause
No decodesClock wrong, wrong band, antenna/system failure
Everyone “SNR -999”Audio level — adjust RX/TX sliders and radio gain
RBN spots you on wrong freqDial frequency vs suppressed carrier — spot what hunters should tune
Laptop fan noise on RXUSB ground loop — ferrites, separate audio interface

Habits / gotchas / checklist (WSJT-X)

Notes & edits