Part of our The Icom IC-7300 Mark II: The Complete Guide.
GridTracker doesn’t talk to the Mark II directly, it sits alongside WSJT-X and reads what that program is doing, but the chain is simple to set up once you know the pieces involved.
The chain: radio, WSJT-X, GridTracker
The Mark II connects to your computer over its single USB-C cable for audio and CAT. WSJT-X needs both working to decode correctly and log against the right band. GridTracker then reads WSJT-X’s log output in real time, it doesn’t talk to the radio at all, it just watches what WSJT-X reports.
Setting up WSJT-X to feed GridTracker
Enable UDP broadcasting of status and logged QSOs in WSJT-X’s settings, GridTracker listens for this on the local network. Point GridTracker at the same UDP port WSJT-X is broadcasting on, usually the default unless you’ve changed it. Once both are running, a logged contact in WSJT-X should populate in GridTracker within a second or two.
What GridTracker actually adds
Beyond mapping contacts as you make them, GridTracker can push logged contacts out to QRZ, LoTW, and other services automatically once you’ve entered credentials. That’s the real payoff, contacts get distributed without a manual upload step after the session ends.
Getting it right the first time
- Confirm WSJT-X’s UDP broadcasting is enabled before troubleshooting GridTracker itself.
- Match the UDP port between the two programs exactly.
- Enter your QSL service credentials once in GridTracker so uploads happen automatically.
- Check your first few contacts appear correctly before trusting it unattended for a full session.
Once this chain is working, FT8 on the Mark II becomes almost entirely about making contacts, not managing the paperwork afterward.
New to this software stack? Start with What Is WSJT-X? and What Is GridTracker? for the basics.