One master log or several? Handling N1MM Logger+, WSJT-X and Log4OM without a mess at upload time
- Replies 2
- Views 17
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Opening a discussion on log management. Many stations end up with several programs writing QSOs: N1MM Logger+ for contests, WSJT-X for FT8 and FT4, and a general logger such as Log4OM, DXKeeper, HRD Logbook or Logger32 for everyday use. Each one has its own database, and the trouble shows up later, when you export for LoTW, QRZ, Club Log or a contest sponsor.
Here are the points where this usually goes wrong, so we can compare approaches.
1. Where should the master log live? One option is to treat the general logger as the permanent record. Contest logs from N1MM+ and WSJT-X's own ADIF file are then imported into it after each session. The other option is to keep each program's database as its own record and merge only for uploads. The first option makes dupe checks against your whole history easier. The second keeps the contest database clean, which matters because N1MM+ expects each contest to be its own self-contained log.
2. ADIF round trips. ADIF is the common format, but programs do not always handle it the same way. Check how modes and submodes are mapped. FT8 is a mode in current ADIF, while FT4 is normally MFSK with the submode FT4. Older software or older import filters may expect something else. Look at how the import treats fields such as STX/SRX, contest ID, grid squares, TX power and comments. Also watch for duplicate imports. Importing the same ADIF twice into a general logger without a dupe filter on import (call, band, mode, date and time) can fill the log with repeated entries, and those repeats then go to LoTW or QRZ.
3. Cabrillo is not just ADIF with a different extension. Cabrillo is a text format with a header (CONTEST, CALLSIGN, CATEGORY-* and so on) and QSO: lines whose exchange layout depends on the contest. The sponsor's rules decide what is valid. Generate it from the contest program, which knows the exchange layout, rather than converting from a general ADIF. Always open the file in a text editor before submitting. Check the callsign, category, power class, claimed score, and that the QSO time and frequency columns look sane. Then read the sponsor's page for the upload method, since some use a web robot and others use email.
4. CAT and rotator sharing. A serial port can generally be opened by only one program at a time. If WSJT-X and your logger both need frequency and mode, you need a rig control layer (for example Hamlib's rigctld, Omni-Rig on Windows, or FLRig) or a virtual serial port splitter. A stray DTR/RTS setting can also key the transmitter, so check PTT behavior on a dummy load first. Rotator control has the same issue: decide which program owns the rotator port and have the others talk to it over a network interface or a rotator control program.
5. UDP and WSJT-X. WSJT-X can send decoded and logged-QSO messages over UDP, and the default is localhost port 2237. Only one program can bind that port unless you configure multicast. If you run a logger and a helper application together, check this setting before wondering why one of them has no data.
6. Band maps and dupe checking. Spots from a cluster or Skimmer-style feed are only as useful as their worked/dupe status. Check that the band map colors a station as worked only for the right band and mode category. In a contest, check that the dupe rules in the software match the contest rules. Some contests count a repeat contact per band, some per band and mode group, and some have extra rules.
7. Upload hygiene. For LoTW, TQSL has to be set up with the correct callsign certificate, station location and grid or zone data. A wrong location can cause mismatches later. For QRZ and Club Log, use the logbook API key or the app password the site provides rather than your main login, and check what your account type requires. Keep a note of the last uploaded date or QSO so you do not upload the whole log every time.
Do you keep one master log and import into it, or do you keep separate logs and merge selectively? And what is your sanity check before you submit a Cabrillo file?
Link to comment
https://www.hamradiobase.com/forums/topic/11707-one-master-log-or-several-handling-n1mm-logger-wsjt-x-and-log4om-without-a-mess-at-upload-time/Share on other sites