ADIFInjector
Portable Windows desktop utility for operators using WSJT-X or MSHV who want to send QSOs to their logger already complete with the satellite ADIF fields that really matter: SAT_NAME, PROP_MODE, FREQ_RX, BAND_RX.
The problem is a very practical one: the digital program does its job, but some ADIF fields that matter in satellite work never reach the logger. The result is an incomplete log that has to be corrected by hand, QSO after QSO.
I wrote ADIFInjector to remove that annoyance: it sits between WSJT-X / MSHV and the logger, intercepts the ADIF record, automatically adds the missing fields or a custom payload, and forwards everything as if nothing had happened. Nothing much changes while operating; the difference is in the log you end up with.
Starting with v0.2.0, ADIFInjector no longer acts only as a bridge to the local logger: it can also automatically forward QSOs to ClubLog and eQSL.cc, as well as prepare them in a monthly ADIF file for import into QRZ.com. It is still small and simple to use, but it has become more than a mere “satellite field fixer”: it is now a small operational hub that stays out of the way and simply gets on with the job.
Current release: v0.2.0 — integrated online services, a new dedicated window, reorganized menu and cleaner configuration.
Practical use?
In two words: stop fixing satellite QSOs manually in your logger and, if you want, let the bridge forward them to selected online services as well.
Read more ↓- Current release: v0.2.0
- Distribution: portable ZIP (EXE + files + languages)
- OS: Windows 10/11 x64
- Supported sources: WSJT-X / MSHV
- Output to logger: TCP, UDP or local ADIF file
- Integrated online services: ClubLog, eQSL.cc, ADIF4QRZ
What it is really for
Anyone operating FT8 or FT4 via satellite knows the annoyance:
the QSO ends up in the logger, yes, but not always with the ADIF fields that truly describe how it was made.
SAT_NAME, PROP_MODE, FREQ_RX, BAND_RX may be missing, along with other data that for SAT work
are anything but secondary.
Correcting every single contact by hand is not impossible, but it is tedious, repetitive and easy to get wrong, especially when you are making multiple QSOs in a row or simply want to operate without breaking the rhythm.
That is exactly why I wrote ADIFInjector: it receives the QSO from WSJT-X or MSHV on the configured port, enriches it with the desired payload and forwards it to the selected logger. The workflow remains simple, but the final log is much cleaner. And if the satellite payload is not enough, Free Payload allows you to add any ADIF field you may find useful, provided it is written in proper ADIF syntax. Starting with v0.2.0, the bridge can also automatically forward QSOs to ClubLog and eQSL.cc or prepare them in a monthly file for QRZ.com, without complicating the main workflow and without interrupting its work toward the local logger.
So what does it actually do?
The goal is not to change the way you do radio, but to remove a manual correction that nobody really wants to do.
Highlights
Transparent bridge
WSJT-X and MSHV do not need to “know” anything about the bridge: just change the destination port and ADIFInjector takes care of the rest.
Automatic satellite payload
Satellite name, propagation mode, RX frequency, RX band and optional comment are added automatically, QSO after QSO.
Free ADIF Payload
For more advanced cases, you can inject an arbitrary ADIF string with standard or custom fields, provided the syntax is correct.
Integrated online services
Real-time upload to ClubLog and eQSL.cc, plus monthly ADIF saving for QRZ.com: one operational flow, several useful destinations.
Easier to configure
A reorganized menu, a dedicated Online Services window and cleaner configuration tabs make v0.2.0 easier even at first startup.
Small, sober, ready to use
Standalone EXE, Dark/Light themes, multilingual support, optional autostart and a compact interface that can stay quietly on the desktop.
Online Services
Starting with v0.2.0, you can decide whether to stop at the local logger or extend the flow to selected online services as well. The idea remains simple: the bridge keeps doing its local job as usual, but it can also take care automatically of a few steps that would otherwise require time or manual imports.
ClubLog
Real-time upload via HTTPS POST. In case of invalid credentials causing a 403 error, ADIFInjector suspends further attempts for the current session, avoiding unnecessary issues on the ClubLog side.
eQSL.cc
Real-time upload via HTTPS POST, with native support for satellite fields such as SAT_NAME and PROP_MODE.
QRZ.com
No direct upload: QSOs are saved to a dedicated monthly ADIF file, ready for manual import into QRZ.com whenever you need it.
The services are independent from one another and fully asynchronous: if one fails, the bridge keeps working normally toward the logger and the other enabled services.
Logger compatibility
| Adapter | Logger / destination | Protocol | Typical port |
|---|---|---|---|
n3fjp_tcp |
ACLog (N3FJP) | TCP | 1100 |
logged_adif_udp |
Log4OM / Logger32 | UDP type 12 | 2237 |
wsjt_udp |
Logger32 / DXKeeper | UDP type 5 | 2237 |
raw_adif_udp |
EasyLog | Raw ADIF UDP | configurable |
adif_file |
Local .adi file | File | — |
EasyLog note: the SAT_NAME field may not be mapped by the logger due to one of its own internal limitations.
ADIFInjector still forwards the expected payload correctly.
Suggested listening ports
This is not a technical requirement, but a very practical convention: using an ADIFInjector port number that mirrors the logger’s own port makes configuration more intuitive and easier to remember.
| Logger | Logger port | ADIFInjector port |
|---|---|---|
| ACLog N3FJP | TCP 1100 | 11000 (default) |
| Log4OM / Logger32 | UDP 2237 | 22370 |
| EasyLog | UDP 2333 | 23330 |
It is not a rigid rule, just a very handy practical convention: use the logger port with an extra zero at the end as the ADIFInjector listening port.
Quick setup
- Open WSJT-X or MSHV and set ADIFInjector’s listening port as the UDP destination.
- Under Options → Configuration, choose the logger adapter and set host, logger port and listening port.
- In the Payload tab, enter the satellite data to be added automatically to your QSOs.
- If you want maximum control, use the Free Payload ADIF tab to define an arbitrary string.
- Press Start: the bridge begins listening and gets to work.
- Optional: open Options → Online Services and enable ClubLog, eQSL.cc or ADIF4QRZ.
Before: WSJT-X → Logger
After: WSJT-X → ADIFInjector → LoggerPractical example with ACLog
WSJT-X / MSHV → 127.0.0.1:11000
ADIFInjector listens on 11000
ADIFInjector forwards to ACLog on 127.0.0.1:1100This makes the flow immediately clear: the digital software talks to the bridge, and the bridge talks to the logger.
The practical suggestion is to start with the local flow — WSJT-X / MSHV → ADIFInjector → logger — and only afterwards, if you care about them, enable the online services as well. This keeps first startup simple and straightforward.
Visual mini manual
Download ADIFInjector
The current release is distributed as a portable ZIP package for Windows. No installer, no complicated setup: just extract it, configure it and try it.
Before downloading, you may also want to take a quick look at the PDF guides.
In the future, if there is enough interest, I may consider releasing versions for macOS (Intel/ARM) and Debian Linux (LMDE ❤️), naturally only if there is real interest from users.
If it helps, buy me a coffee ☕
The program is free and openly downloadable. If it is useful to you and you would like to encourage me to keep it moving forward (improvements, new features), you can buy me a coffee via PayPal. No obligation, no pressure.
💙 Buy me a coffee (PayPal)If it fits well with the way you work, great. If your needs are different, it may simply not be the right program for you.
Mini FAQ
The status indicator stays yellow
It simply means ADIFInjector is listening but has not yet received a QSO from WSJT-X or MSHV. As soon as the first contact is logged, the status indicator turns green.
The logger does not receive QSOs
Check that the logger host and port set in Configuration match the actual values used by the logger itself, and that the logger is already running before you press Start.
EasyLog does not show SAT_NAME
This is a limitation of the logger, not of ADIFInjector. The other satellite fields are still forwarded correctly.
Changelog
v0.2.0 — Build 20260417
- Cloud Push: logged QSOs can now be sent automatically to ClubLog and eQSL.cc, or saved to a dedicated monthly ADIF file for import into QRZ.com.
- New Online Services window: a dedicated section now gathers remote service configuration in a cleaner and more readable way, with distinct, easy-to-understand panels.
-
Reorganized menu: the program now adopts a cleaner layout, consistent with other IK3ITB software,
following the pattern
File | Options | Language | ?. - More compact and rational configuration: the Logger and Payload tabs have been redesigned with a tidier layout, making first startup and later adjustments easier.
v0.1.3 — Build 20260417
- Runtime Dark / Light theme, with immediate switching and preference saved in configuration.
- Windows-consistent menu behavior, leaving menu rendering to the operating system to avoid visual inconsistencies.
- Theme menu translations added and aligned across the distributed language files.
v0.1.2 — Build 20260410
- First public end-user release.
- Complete WSJT-X / MSHV → Logger bridge.
- Satellite payload injection:
SAT_NAME,PROP_MODE,FREQ_RX,BAND_RX, optional comment. - Free ADIF Payload for arbitrary strings.
- Passthru mode.
- Adapters for ACLog, Log4OM, Logger32, DXKeeper, EasyLog and local ADIF file.