Keeping N1MM Logger+, WSJT-X and a master log in sync: ADIF, Cabrillo, LoTW/QRZ/Club Log uploads and CAT sharing
- Replies 2
- Views 75
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Many stations end up with three logs: a contest logger (N1MM Logger+ is the usual choice), WSJT-X writing its own wsjtx_log.adi, and a long-term "master" log in Log4OM, DXKeeper, HRD Logbook or Logger32. Each one has a different idea of what a QSO record should contain, and the problems tend to show up at the worst times: a contest log that won't convert cleanly, duplicate QSOs after a re-import, or a CAT port that only one program can open.
This thread is for comparing workflows. Here are the main friction points, and I'd like to hear which approaches hold up.
1. Who owns the radio? Only one program should normally own the serial or USB CAT port. Common setups are to let the main logger or a rig-control program (flrig, OmniRig, Hamlib rigctld, or the vendor's own tool) be the master, and have the other programs connect to that instead of opening the COM port directly. The same applies to rotator control. Decide which program talks to the rotator interface, and let the others use a shared service such as rotctld or PstRotator, or leave rotator control out of them. Band map click-to-tune and band/mode following only work properly if every program agrees on the VFO and split state.
2. WSJT-X into the logger. WSJT-X can log automatically to its ADIF file, and it can broadcast logged contacts over UDP. N1MM Logger+ and Log4OM can both take that feed, though they use different settings. The question is whether a contact is logged once or several times, for instance in WSJT-X's file, the contest logger and the master log. Having one "primary" destination and treating the others as import-only copies cuts down on duplicates.
3. ADIF round trips. ADIF is flexible, but programs differ in how they write or read mode/submode (FT4 is one example that has historically been handled differently depending on ADIF version and software), frequency units, band, and custom fields like contest exchange or APP_ tags. Always back up before a big import, and run a test import with a small date range. Check that TIME_ON is UTC, that BAND and FREQ agree, and that your own grid, CQ zone and ITU zone are right if they're written to the record.
4. Cabrillo is not a log backup. Cabrillo is a contest submission format, and every contest defines its own exchange and category rules. It's good for sending to a sponsor, but it's lossy for your own records. Keep the native contest database and an ADIF export. Before submission, check the header fields (CALLSIGN, CATEGORY-*, CLAIMED-SCORE, operator and club info if needed), the band/mode mapping, and whether the exchange columns match the rules. Then follow the sponsor's upload or email instructions and look for a confirmation or log-receipt page.
5. Confirmations and uploads. LoTW needs TQSL, a valid certificate for the callsign, and a station location that matches the QSO (callsign, grid, DXCC entity and zones). A wrong station location is a common reason for uploads that are signed but never match. QRZ Logbook and Club Log use their own credentials or API keys, and their duplicate handling differs. If you use real-time upload from the logger and also do bulk ADIF uploads, you can create confusing results.
6. Dupe checking and band maps. Contest dupe rules (per band, per mode, or per band-mode) are set in the contest definition, but a master log's "worked before" check is a different concept. Spots on a band map will only be flagged as dupes if the band map uses the contest log's rules. Do you rely on cluster or Reverse Beacon Network spots in contests, and are they marked correctly for needed multipliers?
So what does your workflow look like: one primary logger and periodic ADIF imports into the master log, or live UDP/ADIF feeds into several programs? What do you do about CAT arbitration and about preventing duplicates?
Link to comment
https://www.hamradiobase.com/forums/topic/10947-keeping-n1mm-logger-wsjt-x-and-a-master-log-in-sync-adif-cabrillo-lotwqrzclub-log-uploads-and-cat-sharing/Share on other sites