WSJT-X with LocalMate
Run your own WSJT-X against an RHR station, or send the console's FT8 decodes and contacts to JTAlert, GridTracker and loggers.
Updated 12 Nov 2026
On this page
The console decodes FT8, FT4 and Q65 at the station with nothing to install; see FT8 in the console. LocalMate adds two options for people who prefer their own software. They use the WSJT-X UDP protocol that JTAlert, GridTracker and most loggers already understand.
| Tab in Tools → Integrations | Use it when | Direction |
|---|---|---|
| WSJT-X Server | You run the WSJT-X application yourself. | WSJT-X → console |
| WSJT-X Client | You operate FT8 in the console and want other software to see the decodes and contacts. | console → your software |
Only one of the two can be on. Turning one on turns the other off.
Both need LocalMate running and connected.
WSJT-X Server: running your own WSJT-X
For rig control and audio, WSJT-X talks to the radio over TCI, so set up TCI first. The WSJT-X Server integration then listens for the messages WSJT-X broadcasts over UDP and does two things with them: keeps WSJT-X's grid square set to the station you are on, and, if you choose, copies the contacts you log in WSJT-X into your RHR logbook.
- In WSJT-X, open Settings → Reporting. Under UDP Server, set the server to
127.0.0.1and the port to2237, and enable the outgoing messages. - For automatic grid squares, also open Settings → General and check AutoGrid.
- In the console, open Tools → Integrations → WSJT-X Server.
- Check WSJT-X UDP Server. It is on by default.
- Leave Server Port at 2237 unless you changed it in WSJT-X; click Update after editing it.
- Check AutoGrid to set WSJT-X's grid to the station's location whenever you connect.
- Check Logging to import contacts logged in WSJT-X into the logbook selected in the console's Log Entry panel.
Each station has its own grid square, so a contact you make from Maine and one from Croatia carry the right location without you editing WSJT-X between them.
WSJT-X Client: feeding JTAlert, GridTracker and loggers
When you operate FT8 inside the console, this integration broadcasts each decode, the console's status and every logged contact over UDP, exactly as WSJT-X would. Software that listens for WSJT-X picks them up without knowing RHR is involved.
- Open Tools → Integrations → WSJT-X Client.
- Check Send to UDP server.
- Set Destination Host to the computer running the software, usually
127.0.0.1for this one. - Set Destination Port to the port the software listens on. WSJT-X's default, which most programs copy, is 2237. Click Update.
- In JTAlert, GridTracker or your logger, point it at the same port and start it.
Only one program can listen on a UDP port. If you run two, use a program such as GridTracker that can forward messages onward, or give each its own port and switch Destination Port when you change programs.
Which one do I want?
- You like WSJT-X's own window, its wide-graph and its sequencing: WSJT-X Server, with TCI.
- You like the console's FT8 panel and want alerts, maps or an external log: WSJT-X Client.
Related articles
-
LocalMate & integrations
TCI radio control
Control the radio you are operating from WSJT-X, JTDX and other TCI software through LocalMate.
-
LocalMate & integrations
LocalMate
The small helper app that connects ham radio software on your computer to the console.
-
FT8, FT4 & Q65
FT8 in the console
Decode FT8 at the station and work it from the console, with no software, audio cables or virtual sound cards.
-
Logbook
Logging from the console
The Log Entry panel, its keyboard flow, and the Log tab for quick edits.
Still stuck?
Tell us what you were trying to do and what happened, and we'll help.