One log chain for contests and daily operating: N1MM, WSJT-X, Log4OM, ADIF, Cabrillo and uploads
- Replies 2
- Views 30
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
This thread is about connecting the pieces so you aren't cleaning up the log by hand after every weekend. A common layout uses a contest logger (N1MM Logger+ or similar) for the contest, WSJT-X for FT8/FT4, and a general-purpose log (Log4OM, DXKeeper, HRD Logbook or Logger32) as the master record. The master record then feeds LoTW, QRZ and Club Log.
The questions I'd like to compare notes on:
1. Where do you draw the line between the contest database and the master log? Do you import the contest ADIF after the event, or log everything live into one program?
2. CAT is the usual point of failure. Only one program can own a serial port at a time. What do you use to share the radio between the logger, WSJT-X and a bandmap: virtual port pairs, rigctld, OmniRig, flrig, or the logger's own digital interface? Rotator control raises the same question, and so does the rotator protocol (GS-232 and so on).
3. Dupe rules differ by contest. Some count a dupe per band, some per band and mode, and ARRL Sweepstakes counts one contact per station regardless of band. How do you make sure the logger's dupe setting matches the rules, especially for digital modes?
4. Before you submit a Cabrillo file, what do you check? Header category fields, exchange columns, UTC times and callsign format are all common causes of a rejected or mis-scored log.
5. For uploads, do you push LoTW, QRZ and Club Log from the master log only, or also straight from the contest logger? Duplicate uploads and a wrong station location in TQSL are the traps I know about.
Which parts of your setup are solid and which are still fragile?
Link to comment
https://www.hamradiobase.com/forums/topic/11282-one-log-chain-for-contests-and-daily-operating-n1mm-wsjt-x-log4om-adif-cabrillo-and-uploads/Share on other sites