One station, several loggers: how do you keep N1MM+, WSJT-X, Log4OM and the LoTW/QRZ/Club Log uploads from becoming a mess?
- Replies 2
- Views 49
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Dan 1 post
Many stations end up with a split setup. N1MM+ for the weekend contests, WSJT-X for FT8/FT4, and something like Log4OM, DXKeeper, HRD Logbook or Logger32 as the "main" log for awards and confirmations. Each program is good at its own job, but the trouble starts when the same QSOs have to move between them and then out to LoTW, QRZ, Club Log and a contest sponsor.
Here is a workflow that tends to hold up, with a few places where it commonly breaks. Please poke holes in it.
1. Pick one master log. Whichever program it is, treat it as the single place where QSOs are merged, and treat everything else as a source or a sink. The usual failure is two programs both uploading to LoTW or QRZ, so one has to deal with duplicates and the other has stale data. Decide which program does each upload and turn the others off.
2. Contest QSOs go from N1MM+ to the master log by ADIF. After the contest, finish all dupe and edit work inside N1MM+ first, then export ADIF and import that file into the master log. Export the Cabrillo from the same cleaned-up database. If you fix a callsign in the master log but not in N1MM+, the Cabrillo you submit will not match what you confirm.
Before importing, check that CONTEST_ID, STX/SRX (serial numbers) and any exchange fields map to something sensible. Many loggers import them as user-defined or APP_ fields, which is fine, but you want to know that before 3,000 QSOs go in.
3. WSJT-X via UDP, not by hand. WSJT-X writes wsjtx_log.adi and sends a logged-QSO message over UDP. Log4OM, JTAlert, GridTracker and some others can listen for it. That gives you live logging, with dupe and worked-before colouring where the client supports it, instead of a batch import at the end of the night. Make sure the UDP port and multicast or unicast settings agree between programs. Two programs listening on the same unicast port is a classic reason one of them logs nothing.
Also note how FT4 is represented. Different programs have represented it as its own mode or as an MFSK submode, depending on the ADIF version and their own mapping. If LoTW or another service rejects or misclassifies those QSOs, check the MODE and SUBMODE fields in the exported file before blaming the service.
4. CAT and rotator: one owner per COM port. This causes more weekend-morning panic than anything else. A serial CAT port can generally be opened by only one program at a time. If WSJT-X and N1MM+ both need rig control, you need something in between: a rig control server (flrig, Hamlib rigctld, OmniRig, depending on what the programs support), a virtual serial port splitter, or a radio with two independent CAT ports. The same applies to rotator control. Let one program own the rotator interface, and have the others send it commands or just read azimuth.
When switching from contesting to digital, check the radio's data mode, audio routing and the split/transmit-VFO behaviour. A logger that reads the wrong VFO will happily log the wrong frequency, and then the band in your ADIF is wrong too.
5. Uploads. LoTW needs TQSL, a valid callsign certificate and a station location whose grid, CQ zone and ITU zone are correct for where you actually operated. A QSO signed with the wrong station location can fail to match. QRZ Logbook uploads use the API key for the specific logbook, and Club Log needs your account credentials or an app password for third-party uploads. For all three, check whether your logger can upload each QSO as it is logged or only in batches, and make sure the same QSOs are not being pushed from two places.
6. Contest log submission. Cabrillo is a plain text format, but sponsors are picky about the header: CATEGORY-OPERATOR, CATEGORY-POWER, CATEGORY-BAND, CLUB, and the exchange fields in each QSO: line. Open the file in a text editor before submitting. Check the callsign, the categories, the QSO count and a few sample lines. Then read that contest's rules for the filename, deadline and upload method, since those differ. Club Log is useful for DXCC and your own records but is not a substitute for the sponsor's submission.
Questions for the thread: Which program do you use as the master log and why? What do you do about the FT4/MFSK mapping and about duplicate uploads? And does anyone have a clean way to share CAT between a contest logger and WSJT-X?
Link to comment
https://www.hamradiobase.com/forums/topic/11058-one-station-several-loggers-how-do-you-keep-n1mm-wsjt-x-log4om-and-the-lotwqrzclub-log-uploads-from-becoming-a-mess/Share on other sites