Repository navigation
v1.5.2
Fixed
- FT4 (and FST4/Q65/...) QSOs posted twice to Wavelog/CQ Radio/HTTP outputs, while FT8 posted correctly. WSJT-X sends both a
QSOLogged(binary) and aLoggedADIF(text) UDP message per logged QSO, and the router deduplicates the pair by matching call+date+mode+frequency. That worked for FT8 (both messages agree the mode isFT8), but WSJT-X's own ADIF text wraps FT4/FST4/Q65/etc. asMODE=MFSK SUBMODE=FT4(older ADIF-spec compatibility) while the binary message just reportsFT4directly - so the dedup key sawFT4vsMFSK, didn't match, and let the second message through as a "new" QSO.- The dedup key now prefers
SUBMODEoverMODEwhen present, so both encodings resolve to the same value.
- The dedup key now prefers
Download
Grab QSOrouter.exe below - no install, no Python needed. QSOrouter.json.example is a sanitized demo config (no real API keys, standard 127.0.0.1/placeholder addresses) - copy it to QSOrouter.json next to the exe as a starting point.
Full changelog: v1.5.0...v1.5.2
Note: this project was renamed from WsjtxLogRouter to QSOrouter; see README.