Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

One master log or three? Keeping N1MM+, WSJT-X and Log4OM in sync without duplicate uploads

ci_cover.jpg

This is a workflow question that comes up whenever a station runs more than one logger. Say you use N1MM Logger+ for contests, WSJT-X for FT8/FT4, and Log4OM (or DXKeeper, HRD Logbook, Logger32) as the everyday log. The mechanics are easy to get wrong in ways that only show up weeks later, as duplicate LoTW records, missing Club Log matches, or a Cabrillo file the sponsor's checker rejects.

The questions I'd like to hash out are these:

1. Should there be one master log, with everything else treated as a feeder? A common design is for the general-purpose logger to hold the permanent record. Contest ADIF exports and WSJT-X's wsjtx_log.adi are imported into it, and only that program uploads to LoTW, QRZ and Club Log. The risk is when two programs upload the same QSO. LoTW will usually just treat it as a duplicate, but QRZ and Club Log behavior varies by how each program matches records.

2. What is the cleanest way to get WSJT-X into the master log? Most people either use the UDP broadcast that WSJT-X sends on "Log QSO" (Log4OM and several other programs can listen for it) or import the ADIF file in batches. Live UDP gives you instant dupe awareness and band-map coloring. Batch import is simpler but means checking for overlap, since re-importing the same file creates doubles unless the import filters on call, band, mode and time.

3. How much should be trusted in ADIF? ADIF is a text format with named, length-prefixed fields, so it moves between programs well, but the semantics differ. Mode and submode are a classic trap: FT8 and FT4 have not always been represented the same way across ADIF versions and programs (FT4 has typically appeared as MFSK with a submode). If an importer maps modes oddly, LoTW and award tracking can break. Contest-specific fields (CONTEST_ID, STX, SRX, SRX_STRING) and APP_ fields can also be dropped or kept depending on the program.

4. What does a sane pre-submission checklist look like? Before exporting Cabrillo I'd want the UTC clock verified, the callsign and operator fields correct, the category and power entered in the header, and any dupes or busted calls reviewed. Does anyone also run the log through a checker or a log-cross-check tool before upload?

I'm also curious how people split CAT control between programs, since that is where many multi-program stations get stuck.

  • Replies 2
  • Views 47
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On CAT, the underlying rule is that a serial port can only be opened by one program at a time. If N1MM+, WSJT-X and the logger all want the same COM port, someone loses. There are basically three ways around it.

The first is to let one program own the rig and have the others talk to it. Hamlib's rigctld can do that over a network socket, and WSJT-X can use "Hamlib NET rigctl". OmniRig (Windows) and Commander in the DXLab suite fill a similar role for programs that support them. The second is a virtual serial port splitter that duplicates the radio's port. That works but adds a layer to debug if you see timeouts. The third is to use only one program for rig control at a time and shut the others' CAT off, which is fine for casual use but awkward in a contest.

If frequency or mode readback goes strange, check the basics: baud rate matching the radio's menu, the CI-V address on Icom rigs, and whether the radio's own USB CAT is competing with a separate cable. PTT is another separate item. Using CAT PTT, RTS/DTR or VOX affects whether WSJT-X can key the rig correctly, and the settings differ between the digital program and the contest logger.

Rotators follow the same logic. A single owner for the rotator interface is easier to manage, and then logging software reads or commands it. Many setups run a rotator control program or rotctld in the middle, and the logger just sends a bearing. That also keeps band maps and "point antenna at spot" features working without every program fighting for the controller port.

One note on UDP: if WSJT-X is sending to both Log4OM and a decode helper such as JTAlert or GridTracker, check the UDP server address and port. Some listeners support multicast and some do not, so a second listener can silently get nothing. Check the manual for the program you actually run.

  • Moderators

For the contest side, I'd separate the contest log from the permanent log in your head. The contest log has to satisfy the sponsor's rules, and the permanent log has to satisfy your own records and award tracking.

Cabrillo is a text format with a header (CONTEST, CALLSIGN, CATEGORY fields, CLUB, OPERATORS, and so on) and then one QSO: line per contact. Frequency is in kHz, the mode is a short Cabrillo code (CW, PH, FM, RY, DG), and date and time are UTC. The exchange columns depend on the contest, so the same QSO could be exported fine for one contest and be wrong for another if the contest definition in the logger is wrong. Always pick the correct contest in N1MM+ before you start, not afterwards. Then read the header it generates before you upload anything. The category lines, the CLUB field if the contest has a club competition, and the soapbox are all things the logger can't guess.

Dupe checking is also contest-defined. In most contests a station can be worked once per band, and sometimes once per band per mode group. Some have different rules, so rely on the contest definition, not habit. The band map helps because spotted stations that are already worked get shown differently. That is only reliable if the logger knows the right band and mode on each QSO, which brings it back to clean CAT.

After the contest, export ADIF from N1MM+ and import it into the master log. Check a few records for band, mode, and the call field before pushing anything to LoTW. For LoTW, TQSL signs the data with your callsign certificate and the station location you pick, so the location's DXCC, grid, and CQ/ITU zones must be right for where you operated. Uploading with the wrong location produces valid but incorrect records that are painful to fix. QRZ logbook uploads need the API key from your QRZ logbook settings, and what is available there depends on your account level. Club Log uses your login or application password in the logging program. If your logger can upload an ADIF in bulk, it usually matches on callsign, time and band, so re-uploads should not duplicate, but I would test with a small file first.

On the other meaning of "club log": if your club tallies scores, ask the contest committee how they want the log or the club name entered, because most sponsors take the club name from the Cabrillo CLUB header and compare spellings literally.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.