One-station logging workflow: N1MM+ for contests, WSJT-X into Log4OM, and keeping ADIF, Cabrillo, LoTW and QRZ in sync
- Replies 2
- Views 34
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Tom 1 post
-
Mod_Chrissy 1 post
I'm putting together a logging setup that covers both contest weekends and everyday operating, and I'd like to compare notes on where the pieces tend to break. The idea is to use N1MM Logger+ for contests, WSJT-X for FT8/FT4 with its QSOs forwarded to Log4OM, and Log4OM as the long-term master log. The master log would push to LoTW, QRZ and Club Log. DXKeeper, HRD Logbook and Logger32 are all reasonable alternatives to that last piece, so feel free to say how they would handle the same job.
These are the points where I expect trouble:
1. Moving QSOs between programs. The contest log lives in N1MM+ and has to end up in the master log. ADIF export from N1MM+ and import into Log4OM works, but contest exchanges can land in odd places. Serial numbers, zones and state/province fields do not always map onto standard ADIF fields the way you would expect. Before importing a whole weekend, it is worth testing a small batch and checking where the exchange data ends up. Import settings that suppress duplicates are also important, so a re-import doesn't create doubles.
2. Cabrillo. Cabrillo is generated from the contest program, not from the master log. The usual order is to finish and clean the log in N1MM+, check the header fields (category, operator class, power, bands, club name, address), export the Cabrillo file, and read it in a text editor before submitting. Each sponsor's rules decide which categories are valid and how the file must be sent, whether by web upload or email, so the rules page matters more than the software defaults.
3. CAT and rotator control. Most rigs only give you one serial port for CAT, so N1MM+ and WSJT-X cannot both open it directly. The common ways around that are a virtual serial port splitter, OmniRig, or Hamlib's rigctld. Rotator control has the same limit: one program owns the port. Where the rig and rotor interfaces allow it, I'd like to hear which approach people consider least fragile.
4. Uploads. LoTW needs TQSL with a valid certificate, and the station location in TQSL has to match what you operated from (grid, DXCC entity, zones). QRZ Logbook and Club Log use API keys. Check which account level your QRZ access requires before building automation around it. Club Log's API access also depends on keys and application permissions.
So: what is the cleanest way to make sure each QSO exists once in the master log, with the right station callsign, operator and grid, no matter which program first logged it? And has anyone found a good way to keep contest-only data out of the uploads?
Link to comment
https://www.hamradiobase.com/forums/topic/11447-one-station-logging-workflow-n1mm-for-contests-wsjt-x-into-log4om-and-keeping-adif-cabrillo-lotw-and-qrz-in-sync/Share on other sites