UDP Hub
WSJT-X and JTDX send information about their work (decoded stations, logged QSOs) over the network - using the UDP protocol - but only to one port. When several programs want this data at the same time (GridTracker, SP4THK HamClock, RigAndLog), you need a splitter. UDP Hub receives the data from WSJT-X and sends copies of it to all the programs you set up.
How it works
Default hub settings: it listens on port 2237 and sends to 2238 (GridTracker), 2239 (HamClock) and 2240 (RigAndLog).
Setup step by step
- Start UDP Hub. In RigAndLog: Configure LogBook and program (F11) → the WSJTX tab → Run UDP Hub now. To have it always start with RigAndLog, tick Run UDP Hub when the program starts there.
- In the hub click Set default values → Default values (or another ready set - see below).
- WSJT-X / JTDX: Settings → Reporting → UDP Server =
127.0.0.1, port =2237(no multicast). The hub shows these values in its window, next to the port field. - Set each receiving program to its port from the hub list: GridTracker to 2238, SP4THK HamClock to 2239 (it takes the “HamClock” output from the hub settings by itself), RigAndLog to 2240 (in RigAndLog: the WSJTX tab, the UDP port field, with Run UDP client to get data from WSJT-X/JTDX ticked).
- In the hub click Start. The window title changes to “RUNNING”, and a counter of received packets appears under the list.
Each program must have a different port. The hub does not start when the listening port is the same as one of the output ports, or when two outputs have the same number - it then shows an error next to the field.
The program window
| Element | What it is for |
|---|---|
| Incoming UDP Stream: Port | The port on which the hub receives data from WSJT-X (2237 by default). |
| IP address and Default IP address | Usually 127.0.0.1 - everything on the same computer. |
| Forward To: 5 rows | For each program: the Send to UDP Port tick, the port number, a name (just for you) and the Allow Reply choice. |
| Start / Stop | Starts and stops forwarding. |
| Sent | How many packets went to each program. |
| Run diagnostic | Checks whether the ports are free and who uses them. |
| Gear button (menu) | Starting with Windows, starting minimized to the tray, automatic hub start, dark text boxes, language, Help (also F1). |
Reply to WSJT-X
Some programs can also send commands to WSJT-X - e.g. you click a station in GridTracker, and WSJT-X calls it. The hub lets a reply through from one program only: choose Allow Reply for that program (or No reply when no program should control WSJT-X).
When several programs send data to the hub port at the same time (e.g. WSJT-X and JTDX), the hub warns: “WARNING: … senders on port … - replies go to the last one.” The reply goes to the one that sent last.
Ready settings (the “Set default values” button)
| Set | The hub listens on | Sends to | When |
|---|---|---|---|
| Default values | 2237 | 2238 GridTracker, 2239 HamClock, 2240 RigAndLog | The most common case - start with it. |
| Values with default GridTracker forwarding | 2238 | 2239 HamClock, 2240 RigAndLog | WSJT-X sends to GridTracker (2237), and GridTracker passes the data on (the Forwarding option) to 2238 - to the hub. |
Starting together with Windows
Menu (gear) → Set the Hub to run at startup and minimize to the system tray. - with one click it switches on the minimized start and the automatic hub start. Separately: Set run with Windows. When you close the window with the X button, you can choose: close the program or hide it to the tray.
Problems
“No data received. Waiting for incoming data...”
WSJT-X does not send to the hub port. Check in WSJT-X Settings → Reporting: UDP Server 127.0.0.1, the same port as in the hub (2237).
When the hub listens on 2238 (the “GridTracker forwarding” set), the data must come from GridTracker.
“Error starting services” after clicking Start
The hub listening port is used by another program (e.g. GridTracker or RigAndLog set to 2237). Click Run diagnostic → Check program port usage - you will see who holds it. More: Diagnostics.
One of the programs gets nothing
Check whether its row in the hub is ticked (Send to UDP Port) and whether exactly this port is set in that program. The Sent counter shows whether the hub sends anything at all.
Clicking a station in GridTracker does not call it in WSJT-X
Choose Allow Reply in the GridTracker row.