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

Contest + digital logging workflow: keeping N1MM Logger+, WSJT-X and Log4OM in sync without duplicate or rejected QSOs

ci_cover.jpg

I'd like to compare notes on a multi-program logging setup. The goal is one clean master log that can feed Cabrillo submissions, LoTW, QRZ Logbook and Club Log, without hand-editing ADIF files at midnight after a contest.

A typical stack looks like this: N1MM Logger+ for contests, WSJT-X (or JTDX) for FT8/FT4, and Log4OM, DXKeeper, HRD Logbook or Logger32 as the long-term general log. The friction usually shows up in a few places.

1. Who owns the radio? A serial CAT port can normally be opened by only one program at a time. If N1MM+ holds the COM port, WSJT-X can't also open it directly. Common fixes are Omni-Rig, Hamlib's rigctld, flrig, or the radio's own second virtual port where it has one. Whatever you pick, match baud rate, stop bits and handshake on every client, and decide up front which program is allowed to change frequency and mode. Rotator control has the same problem: one program talks to the controller, and the others reach it through a rotctld-style or UDP interface.

2. ADIF mode and submode. This is a frequent cause of rejected or mislabeled QSOs. Modern ADIF represents FT4 as MODE=MFSK with SUBMODE=FT4, while FT8 has its own mode in recent ADIF versions. Older loggers may expect different values. When you import or export between programs, check how digital modes are mapped, and check a few records after the first import rather than assuming it worked.

3. Dupes across programs. Dupe checking in N1MM+ applies to the contest database you're logging into, according to that contest's rules (usually per band, sometimes per band and mode). It doesn't know about QSOs in your general logger. If you want a real-world check against earlier contacts, import the ADIF into a new contest database only where the rules allow, and be careful not to carry over QSOs that would break a "no prior contacts" rule.

4. Cabrillo versus ADIF. Cabrillo is for submitting to the contest sponsor. ADIF is for your own log and for confirmation services. Cabrillo files contain the header (callsign, category, operator class, power, bands, mode, club, soapbox, and so on) followed by QSO lines with the exchange as sent and received. Entering the wrong category or exchange fields in the header is a better predictor of a bad entry than anything wrong in the QSO lines. Always read the sponsor's current rules for file naming, deadlines and whether to email the log or upload it through a web form.

5. Uploading afterward. LoTW needs TQSL, a valid callsign certificate and a station location that matches the operating location and callsign. QSOs outside the certificate's valid date range will fail to sign. QRZ Logbook uses an API key tied to the logbook for the callsign. Club Log uses its own credentials and may need an application password or API key depending on the program. Uploading the same ADIF twice is generally okay for these services, which handle duplicates, but altered QSO times or modes can create near-duplicates.

Questions for the thread: Do you keep the contest log separate and import to the master only after the final Cabrillo, or run the contest QSOs into the master in real time? And how do you handle band maps and spots (cluster, RBN, skimmer) when WSJT-X is also running on the same rig?

  • Replies 2
  • Views 25
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Keeping the contest log separate has the clearest audit trail. The contest program holds the log that gets submitted, and the master log only receives an ADIF export once you're done. That lets you fix typos, resolve dupes and double-check the exchange before the QSOs spread to LoTW, QRZ and Club Log.

One practical point on WSJT-X: it can send logged QSOs by UDP to programs that support it, and it also writes its own ADIF file. Decide which one is the source of truth. If you use both the UDP path and a later import of wsjtx_log.adi into the same logger, you'll create duplicates unless the importer matches on call, band, mode and time within a tolerance. Many people use the UDP path only for live logging and keep the .adi file as backup.

Also check time handling. All logs should be UTC, and the PC clock must be properly synchronized for FT8 anyway. A few minutes of drift will cause timestamps that don't match the other station's log, which can hurt LoTW matches.

  • Moderators

For band maps, treat the WSJT-X waterfall and the contest band map as separate tools. The band map in N1MM+ is useful for CW and SSB, where you're hunting multipliers and marking stations you've already worked. Putting FT8 on the same band map can clutter it, because many stations occupy a few narrow slices of spectrum. If the radio is in data mode and CAT is shared, it's easy for the band map to follow a frequency the digital program has moved.

On the submission side, give yourself a checklist: confirm callsign and category in the header, check that band and mode counts look right, run the sponsor's checker if one is available, and save the Cabrillo as a plain text file with the exact filename the rules require. Then export a separate ADIF for the master log and for LoTW signing.

For rotators, I'd test the setup before the contest by sending a bearing from the logger, then from the rotator software, and confirming both display the same heading. Offsets and wrap-around at 180 or 360 degrees tend to show up only once you actually use the controls in the middle of a run.

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.