Contest + digital logging workflow: keeping N1MM Logger+, WSJT-X and Log4OM in sync without duplicate or rejected QSOs
- Replies 2
- Views 25
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Chad 1 post
-
Mod_Chrissy 1 post
I'd like to compare notes on a multi-program logging setup. The goal is one clean master log that can feed Cabrillo submissions, LoTW, QRZ Logbook and Club Log, without hand-editing ADIF files at midnight after a contest.
A typical stack looks like this: N1MM Logger+ for contests, WSJT-X (or JTDX) for FT8/FT4, and Log4OM, DXKeeper, HRD Logbook or Logger32 as the long-term general log. The friction usually shows up in a few places.
1. Who owns the radio? A serial CAT port can normally be opened by only one program at a time. If N1MM+ holds the COM port, WSJT-X can't also open it directly. Common fixes are Omni-Rig, Hamlib's rigctld, flrig, or the radio's own second virtual port where it has one. Whatever you pick, match baud rate, stop bits and handshake on every client, and decide up front which program is allowed to change frequency and mode. Rotator control has the same problem: one program talks to the controller, and the others reach it through a rotctld-style or UDP interface.
2. ADIF mode and submode. This is a frequent cause of rejected or mislabeled QSOs. Modern ADIF represents FT4 as MODE=MFSK with SUBMODE=FT4, while FT8 has its own mode in recent ADIF versions. Older loggers may expect different values. When you import or export between programs, check how digital modes are mapped, and check a few records after the first import rather than assuming it worked.
3. Dupes across programs. Dupe checking in N1MM+ applies to the contest database you're logging into, according to that contest's rules (usually per band, sometimes per band and mode). It doesn't know about QSOs in your general logger. If you want a real-world check against earlier contacts, import the ADIF into a new contest database only where the rules allow, and be careful not to carry over QSOs that would break a "no prior contacts" rule.
4. Cabrillo versus ADIF. Cabrillo is for submitting to the contest sponsor. ADIF is for your own log and for confirmation services. Cabrillo files contain the header (callsign, category, operator class, power, bands, mode, club, soapbox, and so on) followed by QSO lines with the exchange as sent and received. Entering the wrong category or exchange fields in the header is a better predictor of a bad entry than anything wrong in the QSO lines. Always read the sponsor's current rules for file naming, deadlines and whether to email the log or upload it through a web form.
5. Uploading afterward. LoTW needs TQSL, a valid callsign certificate and a station location that matches the operating location and callsign. QSOs outside the certificate's valid date range will fail to sign. QRZ Logbook uses an API key tied to the logbook for the callsign. Club Log uses its own credentials and may need an application password or API key depending on the program. Uploading the same ADIF twice is generally okay for these services, which handle duplicates, but altered QSO times or modes can create near-duplicates.
Questions for the thread: Do you keep the contest log separate and import to the master only after the final Cabrillo, or run the contest QSOs into the master in real time? And how do you handle band maps and spots (cluster, RBN, skimmer) when WSJT-X is also running on the same rig?
Link to comment
https://www.hamradiobase.com/forums/topic/11595-contest-digital-logging-workflow-keeping-n1mm-logger-wsjt-x-and-log4om-in-sync-without-duplicate-or-rejected-qsos/Share on other sites