JTAlert with WSJT-X

JTAlert sits beside WSJT-X and listens on the same UDP reporting channel. It adds audio/visual alerts for wanted callsigns, grids, and countries, and can forward QSOs to LoTW, QRZ, Club Log, and other services.

Home: hamapps.com — JTAlert

What it is (and is not)

JTAlert is a companion, not your primary field log for POTA activations. WSJT-X writes wsjtx_log.adi; JTAlert can mirror contacts to online services. For park references, you still need correct MY_SIG_INFO in the export you upload to pota.app — JTAlert does not replace Polo or N3FJP for that job.

Use JTAlert when:

• You hunt from home and want “new DXCC” or “new grid” bells.
• You want automatic LoTW uploads for FT8 QSOs without manual TQSL steps.
• You run WSJT-X without GridTracker but still want structured alerts.

Skip JTAlert in the field if:

• You already run GridTracker alerts and do not need duplicate chimes.
• Phone battery and laptop CPU are tight — one UDP listener is enough.

Basic setup

1. Install JTAlert and WSJT-X (matching major versions when possible).
2. WSJT-X → Settings → Reporting → enable UDP Server on 127.0.0.1:2237.
3. Launch WSJT-X first, then JTAlert. JTAlert should show “connected.”
4. JTAlert → Settings: set your callsign to match WSJT-X exactly (including /P or portable suffix if you use one).

Rig control note

If N3FJP AC Log also runs, N3FJP’s digital setup docs recommend rig control = none in N3FJP when FLdigi or JTAlert owns CAT — otherwise two programs fight the serial port. See N3FJP digital setup.

Running JTAlert + GridTracker together

Both can listen to WSJT-X. Two common patterns (GridTracker groups.io discussion):

Option A — multicast: WSJT-X Reporting tab uses a multicast address. JTAlert auto-detects; GridTracker → Settings → General → enable Multitask.

Option B — forward: WSJT-X on 2237 → GridTracker receives and forwards on 2238 → JTAlert listens on 2238. Launch GridTracker before JTAlert.

Warning: Avoid uploading the same QSO twice to LoTW from both programs. Pick one upload path.

Pick one alert voice pack. Two programs shouting “CQ DX” at once is a feature nobody needs.

POTA-specific use

JTAlert has no special POTA mode. Practical approach:

• Hunters: enable alerts for callsigns on your “needed parks” list if you maintain one in JTAlert’s wanted setup; otherwise watch pota.app and GridTracker POTA layer.
• Activators: JTAlert is optional. Your job is WSJT-X logging + master ADIF with park tags. Consider JTAlert off during activations to save CPU.

For FT8 hunter etiquette (split TX, grid omission): Hunt and WSJT-X.

Habits / gotchas / checklist (JTAlert)

• Launch WSJT-X first, then JTAlert. Callsign matches including /P.
• UDP 2237, or multicast / forward-to-2238 if GridTracker is also running.
• One LoTW/QRZ upload path. JTAlert does not write MY_SIG_INFO.
• AC Log rig control = none if JTAlert/FLrig owns CAT.
• Field activation: consider JTAlert off. CPU and duplicate chimes are not a picnic-table feature.
• Alerts for needed parks are optional; pota.app + GridTracker POTA layer are the usual hunt tools.

Related

• WSJT-X · GridTracker · Software hub