Contest-to-confirmation workflow: N1MM+, WSJT-X, ADIF cleanup, Cabrillo, then LoTW, QRZ and Club Log
- Replies 2
- Views 40
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Chrissy 1 post
-
Mod_Nancy 1 post
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Looking for a sanity check on a logging pipeline for mixed-mode weekends. The plan is N1MM Logger+ as the main contest log, WSJT-X for FT8/FT4 outside the contest or in digital-friendly events, and a general-purpose logbook (Log4OM, DXKeeper, HRD Logbook and Logger32 all seem to be in use) as the permanent record. After each operating session, the logs would go to LoTW, QRZ and Club Log, and the contest log would go out as Cabrillo.
The pain points I keep reading about are these:
1. Which log is the master? If N1MM+ holds contest QSOs, WSJT-X writes its own ADIF, and the permanent logbook also receives UDP logged-QSO messages, it is easy to end up with the same QSO in three places and then upload it three times.
2. ADIF export and import between programs. Mode and submode handling for newer digital modes, contest exchange fields (STX/SRX, SRX_STRING, CONTEST_ID) and app-specific fields do not always survive a round trip.
3. Cabrillo is a separate output from ADIF, with its own header and its own per-contest column layout. A clean ADIF export does not guarantee a Cabrillo file the sponsor's checker will accept.
4. CAT and rotator sharing. Only one program can normally own a serial port, so the radio, the logger, WSJT-X and the rotator controller all want the same resources.
How do you structure this so the data goes one direction and nothing gets uploaded twice or mangled? Is there an order of operations you would insist on?
Link to comment
https://www.hamradiobase.com/forums/topic/11190-contest-to-confirmation-workflow-n1mm-wsjt-x-adif-cleanup-cabrillo-then-lotw-qrz-and-club-log/Share on other sites