Setting WSJT-X Std Msgs via UDP should set the DX Target

[smbutler-ire]

Setting WSJT-X Std Msgs, via UDP should set the DX Target

Selecting a callsign to initiate a connection with or responding to a request
sets the wsjt-x standard messages, these are also sent over UDP by WSJT-X
ideally it should trigger the setting of the DX Target in openhamclock, so the vcap for the connection can be viewed.
same as manually selecting a callsign from the pskreporter panel.

Similar Features in Other Software

GridTracker uses the Std Msgs via UDP to set the target and trigger the lookup.

EI8JFB
73!

[trevlarson-ORE]

Similarly, when changing bands in WSJT-X it sends a UDP message. OpenHamClock could use that message to clear the WSJT-X decodes & map lines from the old band, so only information for the new band is displayed. (Same thing that GridTracker does).

[navyitc]

I see the value/appeal of this, however; I would like some control on the specified DX location overriding this behavior as an option. Or, the ability to toggle between user-specified DX location and the UDP update changing DX location in real time.

73, Howard, WZ4K

[accius]

This is in Staging now and will ship in the next release. Three things landed:

1. WSJT-X Std Msgs → DX Target (@smbutler-ire's original request)

When you select a callsign in WSJT-X (setting the standard messages), the STATUS UDP message carries the dxCall and dxGrid fields. The server now resolves that to coordinates using a 4-step cascade: WSJT-X's own grid → grid cache from prior CQ/exchange decodes → HamQTH/QRZ callsign lookup cache → DXCC prefix estimation. The DX target updates automatically — propagation predictions, beam heading, and DX weather all follow in real time. Same behavior as clicking a call in PSKReporter or a DX cluster spot.

2. Band change → clear decodes (@trevlarson-ORE's suggestion)

When WSJT-X sends a STATUS with a different dial frequency band than the previous one, the client clears stale decodes and map lines from the old band. Fresh decodes from the new band fill in on the next poll cycle. Same thing GridTracker does.

3. DX Lock protection (@navyitc's concern)

Already covered — the existing 🔒 lock toggle in the DX panel prevents any auto-update from overriding your manually set DX target. When locked, WSJT-X callsign changes are silently ignored. Unlock to let it follow again.

Works with both local UDP and the remote relay agent. 73