One master log across N1MM Logger+, WSJT-X and Log4OM: where ADIF, Cabrillo and uploads usually go wrong
- Replies 2
- Views 33
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Chrissy 1 post
I'd like to compare notes on structuring a logging workflow when several programs touch the same QSOs. A typical case is N1MM Logger+ for CW/SSB contests, WSJT-X for FT8/FT4 on the same rig, and a general-purpose logbook (Log4OM, DXKeeper, HRD Logbook or Logger32) as the long-term record that feeds LoTW, QRZ and Club Log.
These are the points where the chain tends to break, and I'd like to hear how people handle them.
1. Which program owns the master log? Pick one. The contest logger can own the log during the contest, then you export ADIF and import it into the long-term logbook afterward. The alternative is to have everything log live into one database. Mixing both without a rule leads to duplicate records, and those duplicates then get uploaded to LoTW, QRZ and Club Log.
2. ADIF round trips. ADIF is the interchange format, but each program adds its own APP_ fields and handles contest exchange fields differently. Check that the fields you care about survive an import: STX/SRX, SRX_STRING, CONTEST_ID, band, submode and grid. For digital modes, newer ADIF versions record FT8 as MODE=MFSK with SUBMODE=FT8, while older software expects MODE=FT8. If the mode comes through wrong, dupe checking and award tracking suffer.
3. Cabrillo is not an ADIF substitute. Cabrillo is a text format for submitting a contest log, and the QSO line layout depends on the contest. It's usually safest to generate it from the contest logger, which knows the exchange format, rather than converting ADIF with a generic tool. Then read the header (CATEGORY-OPERATOR, CATEGORY-POWER, CATEGORY-BAND, CLUB, and so on) before you send it, because the sponsor's robot will take those at face value.
4. CAT and rotator sharing. A serial port can normally be opened by only one program. If N1MM+ and WSJT-X both need the radio, you need a sharing layer such as flrig, Hamlib's rigctld, OmniRig or the commander component of a suite like DXLab. What is supported varies by program, so check each one's docs. The same goes for rotators, where a single controller or daemon should take commands from the logger's band map or bearing display.
5. Uploads. LoTW needs TQSL and a station location that matches where you actually operated (DXCC entity, grid, CQ and ITU zones). A wrong location setting gives you QSOs that never match. QRZ Logbook and Club Log uploads use credentials or API keys stored in the logger. Decide whether uploads happen live or in batches after you've cleaned up the log.
What order do you use for the post-contest cleanup: export Cabrillo first, or import and dedupe ADIF first? And what's your method for keeping WSJT-X contacts from being logged twice?
Link to comment
https://www.hamradiobase.com/forums/topic/10917-one-master-log-across-n1mm-logger-wsjt-x-and-log4om-where-adif-cabrillo-and-uploads-usually-go-wrong/Share on other sites