One master log or separate contest logs? Keeping N1MM+, WSJT-X, Log4OM and the online uploads from colliding
- Replies 2
- Views 56
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'm sketching a station logging setup and want to sanity-check the plumbing before it gets messy. The pieces: N1MM Logger+ for contests, WSJT-X for FT8/FT4 on non-contest days, and Log4OM (or possibly DXKeeper) as the long-term log that talks to LoTW, QRZ and Club Log. I'd like to avoid duplicate QSOs, wrong modes in LoTW, and a Cabrillo file that gets bounced for formatting.
The questions I keep running into:
1) CAT ownership. Only one program can open a serial port at a time. Is it better to let one program own the radio and share it (OmniRig, FLRig, rigctld, DXLab Commander), or use a virtual COM port splitter? WSJT-X, the logger and the rotator software all want frequency and mode.
2) Where should contest QSOs live? Should N1MM+ stay the only home for contest logs, with an ADIF export into the master log afterward? Or should everything be logged in one place?
3) What actually breaks when going from ADIF to Cabrillo to LoTW? I'm thinking of mode and submode mapping, the exchange fields, and station location mismatches.
4) Band map and dupe behavior. How much should I trust the band map's worked/dupe coloring versus the contest's own dupe rules, such as per band, per band-mode, or one QSO total?
If you have a checklist you follow before pressing upload, I'd like to see it.
Link to comment
https://www.hamradiobase.com/forums/topic/10876-one-master-log-or-separate-contest-logs-keeping-n1mm-wsjt-x-log4om-and-the-online-uploads-from-colliding/Share on other sites