One-radio logging chain: N1MM Logger+ for contests, WSJT-X for digital, and a main log with LoTW, QRZ and Club Log uploads
- Replies 2
- Views 45
- 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 is a workflow discussion about keeping one clean master log when several programs touch the same radio. A common arrangement has N1MM Logger+ for contests, WSJT-X for FT8 and FT4, and a general-purpose logger such as Log4OM, DXKeeper, HRD Logbook or Logger32 as the permanent record. The same QSOs can end up in three places, and that is where the trouble starts: duplicate imports, wrong modes, wrong grids, and uploads that LoTW or Club Log reject.
Here is the chain I would sketch, with the weak points marked. Corrections are welcome.
1. CAT and rotator control. Only one program can normally own a serial port. If N1MM Logger+ and WSJT-X both need frequency and mode, you need a sharing layer. Options include Hamlib's rigctld, flrig, Omni-Rig, DXLab Commander, or a virtual serial port splitter. Which one works depends on the radio and driver. Rotator control has the same ownership problem. Decide which program talks to the rotator hardware and let the others send commands through it, rather than having several programs open the port.
2. Where each QSO is born. For a contest, N1MM Logger+ should be the source of truth for that contest. Its band map, dupe sheet, and exchange parsing exist to support that. For FT8 outside a contest, WSJT-X logs to its ADIF file, and many loggers can take QSOs live over UDP. If you work a digital contest through WSJT-X, check whether you want its UDP/N1MM broadcast feeding the contest logger, or whether you will import the ADIF afterward. Importing afterward is simpler, but you lose live dupe checking.
3. Moving data with ADIF. ADIF is the interchange format between loggers, but it is not perfectly uniform. Check what happens to these fields on import: MODE and SUBMODE (FT4 is handled differently from FT8 in some programs), STATION_CALLSIGN versus OPERATOR, MY_GRIDSTATE, MY_CQ_ZONE and ITU zone, and contest-specific fields like STX, SRX, and CONTEST_ID. Before bulk-importing a whole weekend, try a handful of QSOs and compare them field by field in the destination logger.
4. Cabrillo is for the contest sponsor, not your archive. It is a submission format, and the exact content depends on the contest rules. Generate it from the contest logger, not from the master log. Then check the header (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER, CATEGORY-MODE, CLUB, and so on) and the exchange columns. Digital QSOs are normally written with the Cabrillo mode code DG, but individual contests can differ, so read the rules. Most sponsors have a web upload, and some accept email. Keep the generated file along with the original N1MM database for a while in case the log checker has questions.
5. LoTW, QRZ and Club Log. LoTW needs TQSL and a station location that matches the operating location: DXCC entity, grid, and zones. If you operated from another place, create a separate station location rather than editing the home one. QRZ logbook uploads use an API key tied to the logbook, and access requirements may depend on the account level, so verify them on QRZ. Club Log is useful for DXCC tracking and matching, and it has its own upload and API options. Be careful about uploading the same QSOs from two programs. Pick one program as the uploader for each service and let the other ones stay quiet. Otherwise you get duplicates or confusing confirmation states.
6. Club-level logging. If a club station or multi-op group is involved, there is another layer: network settings between N1MM instances, operator callsigns, and who submits the final log. The entry should be assembled from one merged database, not from several partial exports.
What are people using as the master log, and where do you draw the line for imports? Do you let the contest logger upload to LoTW directly, or always route through the master log first?
Link to comment
https://www.hamradiobase.com/forums/topic/10859-one-radio-logging-chain-n1mm-logger-for-contests-wsjt-x-for-digital-and-a-main-log-with-lotw-qrz-and-club-log-uploads/Share on other sites