One clean log across N1MM Logger+, WSJT-X and Log4OM: CAT sharing, ADIF/Cabrillo, and LoTW/QRZ/Club Log uploads
- Replies 2
- Views 33
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Chrissy 1 post
-
Mod_Nancy 1 post
This thread is for comparing workflows when the same station uses more than one logger. A common setup is N1MM Logger+ for contests, WSJT-X for FT8/FT4, and Log4OM (or DXKeeper, HRD Logbook, Logger32) as the long-term logbook that feeds LoTW, QRZ and Club Log. It works, but the failure points are predictable: a serial port that only one program can open, ADIF fields that don't map cleanly, and duplicate QSOs after an import.
Here is the outline I'd start from, and I'd like corrections.
First, decide which program is the master log. A contest logger is optimised for fast entry, dupe checking and Cabrillo output, so it's usually the master for that contest only. The general-purpose logbook (Log4OM, DXKeeper, etc.) is better as the permanent record because it handles award tracking, QSL status and online-service sync. After each contest, export ADIF from N1MM+ and import it into the long-term log, rather than trying to keep both live-synced.
Second, CAT and rotator control. Most rigs expose one CAT port, and only one application can hold it at a time. The usual ways around that are a CAT hub or sharing layer (OmniRig, FLrig, Hamlib's rigctld, DXLab Commander, or HRD), or virtual serial port pairs. Rotators follow the same rule: one program owns the controller, and others talk to it through a rotator server such as rotctld or a utility like PstRotator. WSJT-X can talk to Hamlib, OmniRig, Commander or HRD, so pick one hub and point every program at it instead of fighting over COM3.
Third, the export chain. For a contest, generate the Cabrillo file from N1MM+ and check the header lines (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER, CATEGORY-MODE, CLUB, and so on) against that contest's current rules, because sponsors differ on accepted category values. For the permanent log, use ADIF. Before importing, confirm that STATION_CALLSIGN, OPERATOR, MY_GRIDSQUARE, MODE and SUBMODE are populated, since LoTW and Club Log rely on them.
Fourth, uploads. LoTW needs TQSL with a station location that matches the callsign, DXCC entity, grid and zones for that operation. LoTW generally ignores QSOs it has already received, but a wrong station location will still produce mismatched or unusable uploads. QRZ Logbook and Club Log both use API-style uploads and need credentials or keys set up in the logger. Test with a small batch before pushing a whole contest weekend.
Fifth, dupes. N1MM+ applies the contest's dupe rules, typically per band, or per band and mode. A general logbook's dupe checker is a different thing, and importing the same ADIF twice can create real duplicate records unless the import has duplicate detection enabled. Keep the original ADIF file and import into a test log first.
Questions for the thread: Which program do you let own CAT during a contest, and what do you use to share it? How do you get WSJT-X QSOs into a contest log without double-logging? And what's your routine for checking a Cabrillo file before upload?
Link to comment
https://www.hamradiobase.com/forums/topic/11411-one-clean-log-across-n1mm-logger-wsjt-x-and-log4om-cat-sharing-adifcabrillo-and-lotwqrzclub-log-uploads/Share on other sites