Contest log to LoTW, QRZ and Club Log without duplicate or broken records: ADIF vs Cabrillo workflow check
- Replies 2
- Views 33
- 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 trying to design a logging workflow that covers weekend contests and everyday operating, and I'd like it checked for weak points. The idea is to run N1MM Logger+ for contests and WSJT-X for FT8/FT4 and digital contest modes. A general-purpose logbook (Log4OM, DXKeeper or HRD Logbook) would be the master log for LoTW, QRZ and Club Log uploads. Logger32 is also on the table if someone has a reason to prefer it.
Here is the flow I have in mind. During a contest, every QSO goes into N1MM+ and nothing else. Afterward I generate the Cabrillo file for the sponsor's log robot and export an ADIF file from the same N1MM database. That ADIF gets imported into the master logbook, which then pushes to LoTW (through TQSL), QRZ Logbook and Club Log. For WSJT-X, I'd either let it log to wsjtx_log.adi and import that periodically, or use UDP logging straight into the master logbook.
These are the points I'm unsure about:
1. ADIF round trip. Does the contest exchange survive the trip from N1MM+ into the master logbook? I'm thinking of fields like STX, SRX, STX_STRING, SRX_STRING and CONTEST_ID. I'd also like to know how FT8 and FT4 are represented, since I've seen MODE=FT8 in some files and MODE=MFSK with SUBMODE=FT4 in others, depending on the ADIF version.
2. Upload flags. If the master logbook imports records that already carry QSL_SENT or LOTW_QSL_SENT values, will it skip them or re-upload them? I don't want to flood LoTW or Club Log with duplicates.
3. CAT and rotator control. Only one program can own a serial port at a time. What's the cleanest way to share one radio between N1MM+, WSJT-X and a logbook? I'm weighing Omni-Rig, FLrig, a Hamlib rigctld instance, or a virtual COM port splitter. The same question applies to rotator control from the band map or from a callsign lookup.
4. Band map and dupe checking. How do you keep spots from RBN or a DX cluster feeding the band map without creating a mess, and what are the usual ways dupe checking goes wrong, such as band changes, mode groups and sprint-style rules?
5. Submission. Which mistakes get a Cabrillo file rejected or reclassified? I'm thinking of wrong category lines, frequency units, or callsign and time formatting.
Link to comment
https://www.hamradiobase.com/forums/topic/11239-contest-log-to-lotw-qrz-and-club-log-without-duplicate-or-broken-records-adif-vs-cabrillo-workflow-check/Share on other sites