One-shot logging workflow: N1MM+ for contests, WSJT-X/Log4OM for digital, then ADIF to LoTW, QRZ and Club Log. Where does it break?
- Replies 2
- Views 13
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Lee 1 post
-
Mod_Chrissy 1 post
I'm planning a logging setup before the next contest season and want to sanity-check the data flow. The goal is one master log I trust, with as little retyping and cleanup as possible.
The plan has three parts:
Contests: N1MM Logger+ with CAT control of the rig, a rotator interface, and a band map fed by a telnet cluster and a CW skimmer. Cabrillo gets exported for the sponsor's log robot, and an ADIF export goes into the main log afterward.
Everyday digital: WSJT-X for FT8 and FT4, using the UDP server so Log4OM 2 picks up the logged QSOs automatically. Log4OM would be the master log.
Confirmations: Log4OM uploads to QRZ Logbook and Club Log, and LoTW goes through TQSL signing.
Here are the places I expect trouble, and I'd like to hear where people have seen them go wrong:
1. CAT port ownership. WSJT-X, N1MM+ and Log4OM all want the radio. I assume the answer is either one program owning the serial port with the others slaved to it, or a shared layer such as Hamlib's rigctld or Omni-Rig. What is the least fragile arrangement when you switch between a contest and a digital session?
2. Mode and submode mapping on ADIF export and import. FT8 and FT4 don't always arrive the same way. FT4 is generally carried as MFSK with an FT4 submode, and some programs mishandle that. I don't want LoTW or a contest scorer to see a mode it doesn't recognize.
3. Cabrillo versus ADIF. I understand Cabrillo is a sponsor-specific, fixed-column text format for scoring, while ADIF is the general-purpose log exchange format. Cabrillo is not a good way to move logs between programs, because it loses fields. Is that right?
4. Dupe rules. Dupe checking depends on the contest rules: per band, per band and mode, or once for the whole contest. How do you make sure the logger is configured for the right ruleset before the first QSO and not discovered halfway through?
5. LoTW upload timing. TQSL needs a station location with the right grid, CQ and ITU zones and DXCC entity, and the certificate has a valid QSO date range. I'd like to know what gets silently rejected when a QSO falls outside that range or the station location doesn't match.
Is this workflow sound, or is there a simpler path? I'm also interested in how DXKeeper, HRD Logbook or Logger32 users would handle the same chain.
Link to comment
https://www.hamradiobase.com/forums/topic/11812-one-shot-logging-workflow-n1mm-for-contests-wsjt-xlog4om-for-digital-then-adif-to-lotw-qrz-and-club-log-where-does-it-break/Share on other sites