One master log or several? Keeping N1MM+, WSJT-X and Log4OM in sync for contests, LoTW, QRZ and Club Log
- Replies 2
- Views 27
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Tom 1 post
-
Mod_Chrissy 1 post
Here's a setup question that comes up whenever someone runs both contest and everyday operating on one station: where should the master log live, and how do QSOs get from one program to another without duplicates or mangled fields?
Take a common arrangement. N1MM+ handles the serious CW and SSB contests. WSJT-X handles FT8 and FT4 on non-contest days, and sometimes in digital contests. Log4OM or DXKeeper is the long-term log that feeds LoTW, QRZ Logbook and Club Log. Meanwhile CAT control, the rotator and the band map all want to share the same radio and the same serial or network resources.
These are the friction points worth sorting out before the next contest weekend:
1. ADIF round trips. ADIF is the common currency, but programs are not equally strict about it. Contest-specific exchange data (STX/SRX, STX_STRING/SRX_STRING, CONTEST_ID, ARRL_SECT, and so on) may be dropped or remapped on import. Mode and submode handling also differs. FT8 is its own MODE in current ADIF versions, while FT4 is carried as MFSK with SUBMODE FT4. An older program may reject or misclassify these. Before trusting any import, load a small test file and check what happened to mode, band, frequency, and the date and time fields.
2. Cabrillo is not a log format for storage. It's a submission format, and each sponsor defines its own exchange layout. Generate it from the contest program with the correct contest selected, not from a general-purpose logger's ADIF. Check the header (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER, and so on) against the rules, and read the QSO lines. Frequency should be in kHz on HF, and the mode code should be CW, PH, FM, RY or DG as appropriate.
3. Upload order. LoTW needs TQSL to sign the file, and the station location (callsign, grid, DXCC entity, zones) has to match the QSOs. QSO dates must also fall inside the certificate's valid range. QRZ Logbook uses a per-logbook API key. Club Log uses account credentials plus an application password or key. If the logging program uploads automatically on every QSO and you also do a bulk ADIF upload later, you can end up with duplicate or conflicting records. Pick one path per service.
4. Shared UDP and CAT. WSJT-X can broadcast logged-QSO and status messages over UDP. If JTAlert, GridTracker, N1MM+ and Log4OM all want that stream, a single unicast port can be claimed by only one listener. Multicast is the usual workaround. Similarly, only one program should open the radio's COM port directly. Everything else should go through a CAT sharing tool, such as Commander in the DXLab suite, OmniRig, Hamlib's rigctld, or the logger's own radio server.
So the question for everyone: do you keep one authoritative log and import into it after each event, or do you let each program upload on its own? And what has the best track record for you with dupes, band maps and rotator control when the pileups start?
Link to comment
https://www.hamradiobase.com/forums/topic/11534-one-master-log-or-several-keeping-n1mm-wsjt-x-and-log4om-in-sync-for-contests-lotw-qrz-and-club-log/Share on other sites