One log, many tools: keeping N1MM+, WSJT-X, Log4OM and the LoTW/QRZ/Club Log uploads from fighting each other
- Replies 2
- Views 33
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Dan 1 post
Most logging problems seem to come from having too many programs that each believe they own the log, the radio, or the COM port. This thread is for comparing how to split those jobs. Below is a layout to react to, followed by the points where it tends to break.
Contest log versus general log. Treat the contest program as a per-event database. N1MM Logger+ keeps one database per contest, with its own dupe sheet, multiplier tracking and exchange parsing. At the end you generate the Cabrillo file for the sponsor and export ADIF for your permanent log. The permanent log, whether Log4OM, DXKeeper, HRD Logbook or Logger32, takes that ADIF import. Treat the contest program as the source of truth for the contest, and the main logger as the source of truth for everything else.
WSJT-X in the middle. WSJT-X writes its own wsjtx_log.adi and also broadcasts decoded and logged-QSO messages over UDP. The default is 127.0.0.1 port 2237. The trap is that two programs cannot always listen on the same unicast port. If you want a logger plus something like a decode viewer or alert tool, use a multicast address in the UDP server settings, or put a relay in the chain. Also make sure the logger is not set to receive from WSJT-X while you also import wsjtx_log.adi by hand, or you will log every FT8 QSO twice.
CAT and rotator control. A serial port can usually be opened by only one program. If the logger, WSJT-X and a rotator or band-decoder utility all want frequency and mode, pick one owner. Options are the logger itself, a CAT manager (Commander in the DXLab suite, HRD, or Omni-Rig/Hamlib's rigctld), or a virtual serial port splitter. Every extra layer adds a place for baud rate, stop bit or PTT mismatches. Rotator control is similar: use one program that talks to the controller, and have the logger send bearings to it rather than opening the port too.
Uploads. LoTW uploads go through TQSL, so the station location (callsign, grid, DXCC entity, CQ and ITU zones) must match the certificate and where you operated. A wrong location in a signed batch is the classic way to produce QSOs that never match. QRZ Logbook and Club Log both take ADIF and have their own API or key mechanisms for automatic uploads. Be deliberate about whether the contest program, the main logger, or both are doing automatic uploads. Pick one path per service.
Fields that matter in ADIF. Check that STATION_CALLSIGN, OPERATOR, MY_GRIDSQUARE, MODE/SUBMODE, BAND and the QSO date and time in UTC survive the export and re-import. Digital submodes are the usual casualty, because programs map them differently. FT4, for example, has been handled as a MODE or as a SUBMODE depending on the software and ADIF version in use.
Before you submit a contest log. Confirm that the Cabrillo header matches the sponsor's current rules. That means the CONTEST name, category lines, claimed score and operator or club fields. Check that the exchange columns look right in a few QSO: lines, and that time and frequency are in the units the sponsor expects. Then use the sponsor's upload page or log robot, and keep the confirmation.
Where does your workflow split differently? In particular: who owns CAT, where do you do dupe checking when running both a contest program and a main logger, and do you let anything auto-upload during a contest?
Link to comment
https://www.hamradiobase.com/forums/topic/11138-one-log-many-tools-keeping-n1mm-wsjt-x-log4om-and-the-lotwqrzclub-log-uploads-from-fighting-each-other/Share on other sites