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 412.9 km/s
Aurora 1
Updated 14:00 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 separate contest logs? Keeping N1MM+, WSJT-X, Log4OM and the online uploads from colliding

ci_cover.jpg

I'm sketching a station logging setup and want to sanity-check the plumbing before it gets messy. The pieces: N1MM Logger+ for contests, WSJT-X for FT8/FT4 on non-contest days, and Log4OM (or possibly DXKeeper) as the long-term log that talks to LoTW, QRZ and Club Log. I'd like to avoid duplicate QSOs, wrong modes in LoTW, and a Cabrillo file that gets bounced for formatting.

The questions I keep running into:

1) CAT ownership. Only one program can open a serial port at a time. Is it better to let one program own the radio and share it (OmniRig, FLRig, rigctld, DXLab Commander), or use a virtual COM port splitter? WSJT-X, the logger and the rotator software all want frequency and mode.

2) Where should contest QSOs live? Should N1MM+ stay the only home for contest logs, with an ADIF export into the master log afterward? Or should everything be logged in one place?

3) What actually breaks when going from ADIF to Cabrillo to LoTW? I'm thinking of mode and submode mapping, the exchange fields, and station location mismatches.

4) Band map and dupe behavior. How much should I trust the band map's worked/dupe coloring versus the contest's own dupe rules, such as per band, per band-mode, or one QSO total?

If you have a checklist you follow before pressing upload, I'd like to see it.

  • Replies 2
  • Views 56
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On CAT, pick one owner for the radio and make everything else a client. With a single physical serial port, the usual choices are a rig-sharing layer such as OmniRig, FLRig or Hamlib's rigctld, or a logger like DXLab's Commander that other DXLab apps share. A virtual COM splitter can work, but it adds one more thing to break at 0000Z when you're busy. Many modern radios also expose separate USB CAT and audio devices, which makes this easier. Whichever route you take, keep the baud rate, the data/stop bits and the radio's CI-V or CAT settings consistent between programs. Most 'frequency randomly jumps' reports trace back to two programs polling or writing at once.

On where the logs live, I'd keep contest logs in the contest logger. N1MM+ builds its dupe sheet, multiplier tracking, score summary and Cabrillo header around its own database, and the contest definition holds the exchange fields. Importing contest QSOs straight into a general-purpose log works for archiving, but you lose the contest-specific fields unless the ADIF carries them. After the contest, export ADIF from N1MM+ and import it into your master log. Check that CONTEST_ID, STX/SRX or the exchange strings, and the frequency survived. Then confirm that the import's duplicate detection doesn't throw away QSOs that are legitimate repeats on a different band or mode.

For Cabrillo, the file is plain text, so open it before submitting. Check the CALLSIGN, CATEGORY lines, the operator list and the claimed score against what the sponsor expects. Sponsors differ on which categories and overlays they accept, so read that contest's rules rather than assuming last year's header is still right.

  • Moderators

For uploads, I'd keep the order simple: finish the contest log, run any dupe or callsign checks, and submit the Cabrillo. Only then push to LoTW, QRZ and Club Log from the master log. Uploading while the log is still being corrected means you have to fix the same QSO in several places.

A few details to watch with each service:

LoTW needs a TQSL certificate and a station location that matches where you operated. That means DXCC entity, grid, and CQ and ITU zones. If those are wrong, the QSOs still get signed and uploaded but won't confirm the way you expect. Matching also depends on band and a mode group (CW, phone or data), plus a time window. That makes clock accuracy and honest UTC times matter, and WSJT-X users need a properly synced PC clock for decoding anyway.

QRZ's logbook upload uses a logbook API key, not your password. Club Log uses its own application password and API setup. Either way, read what your logger does when you re-send a QSO that's already there. Some tools mark QSOs as 'sent' and skip them, while others will happily resend a whole ADIF.

For mode mapping, look at what the logger writes for FT4, FT8 and MFSK-family modes. ADIF has MODE and SUBMODE fields, and tools differ in how they populate them. Spot-check a few exported records before trusting a bulk import.

On dupes, treat the band map as a helper rather than the rule. Its worked/new-multiplier colors are only as good as the contest definition and the current mode setting. If a contest counts one QSO per band, or per band per mode, check that the logger's dupe setting matches. For rotators, keep the controller (PstRotator, HRD Rotator or whatever you use) separate, and let the logger send only the bearing. That way a rotator program crash won't take the log down with it.

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.