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, several programs: keeping N1MM+, WSJT-X and Log4OM from fighting each other (ADIF, Cabrillo, LoTW, QRZ, Club Log)

ci_cover.jpg

A common station setup has three or four programs touching the same QSOs. N1MM Logger+ handles contests. WSJT-X handles FT8 and FT4. Log4OM, DXKeeper, HRD Logbook or Logger32 holds the long-term log. Meanwhile LoTW, QRZ and Club Log all want uploads. Each piece works on its own, but together they can produce duplicate QSOs, mismatched modes and rigs that stop answering CAT commands.

Here is the pipeline as I understand it. Please correct anything that's wrong.

1. Contest QSOs are logged in N1MM+ with the contest's own exchange fields. At the end, you export Cabrillo for submission and ADIF for the permanent log.

2. WSJT-X writes wsjtx_log.adi and can also send logged QSOs over UDP. Some loggers listen to that broadcast directly, and others just import the ADIF file.

3. One program is the master log. Everything else feeds it, and confirmations and uploads to LoTW, QRZ and Club Log are done only from there.

The questions I'd like to discuss are these:

  • Which program should be the master log, and should contest QSOs go in as one batch after the contest or be merged continuously?
  • How do you stop two programs from uploading the same QSO to the same service?
  • What is the cleanest way to share one radio's CAT port between a logger, a digital-mode program and a rotator controller?
  • What do you check before sending a Cabrillo file, so the log isn't flagged for formatting problems?

Please say which software you're using, since the answers depend on it.

  • Replies 2
  • Views 30
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the master log: pick one program as the only place that talks to the online services, then keep it that way. Uploading the same QSO to LoTW, QRZ or Club Log from two programs is how duplicates and confusing status flags appear. QRZ and Club Log generally tolerate re-uploads of the same QSO. LoTW is different, because every upload is a signed file from TQSL, so it's worth keeping a note of which program handled which date range.

For ADIF, the biggest trouble spots are mode and contest fields.

  • FT4 is not a top-level mode in current ADIF. It's MODE=MFSK with SUBMODE=FT4. FT8 is its own mode. Older software or old export templates can mangle this, so check a few FT4 QSOs after any import.
  • LoTW groups FT8, FT4 and similar modes under DATA when matching. A mode mismatch in your own log can look like a missing confirmation.
  • Contest exchanges live in fields like STX, SRX, SRX_STRING and CONTEST_ID. Some programs keep them and some drop them on import. If you want the exchange kept for later, test with a small file first.
  • Always check that date and time are UTC, and that band and frequency agree. A QSO with a wrong band is a common cause of rejected or unmatched uploads.

For LoTW, the TQSL station location (callsign, grid, DXCC entity, CQ and ITU zones) must match where you actually operated. If you operate from more than one place, you need separate station locations, and the logger must select the right one. For QRZ, the Logbook API needs the key for that specific logbook, and it's separate from the lookup login. For Club Log, use an application password rather than your main password if the program supports it.

When you import a contest ADIF into the master log, run any duplicate check the program offers first, and keep a backup of the log before the import. That is much easier than untangling an import afterwards.

  • Moderators

For CAT sharing, the main rule is that only one program can open a serial port at a time. There are three common ways to get around it.

  • A rig-control server such as FLRig or Hamlib's rigctld. The logger, WSJT-X and anything else connect to it over a network socket instead of opening the COM port directly. WSJT-X can use Hamlib's NET rigctl option, and many loggers can use Hamlib or FLRig as well. Check your version's documentation.
  • A virtual serial port splitter. It works, but it adds a layer that can fail, and it can add latency.
  • A hub program, such as DXLab Commander in the DXLab Suite, which owns the radio and shares frequency and mode with the other DXLab applications and, through its interfaces, with others.

Rotator control follows the same pattern. Hamlib's rotctld or a dedicated rotator program owns the controller, and the logger sends a bearing to it. Most loggers can turn the antenna toward a station you've called or clicked on the band map. That's useful, but test it before the contest.

For contest day, a few points:

  • Dupes. Check what the contest counts as a dupe. Many contests work a station once per band per mode. Others, such as ARRL Sweepstakes, allow one contact per station regardless of band. Make sure the contest selected in N1MM+ matches the rules you're operating under. Don't let the logger's dupe sheet make this decision for you.
  • Band map spots. Cluster and Reverse Beacon Network spots on the band map may count as assistance in some categories. Single-op unassisted usually means no spots at all, so check the category before you connect the cluster.
  • Multi-computer networks. Clocks must agree, and every station must use the same contest, the same operator and station names, and the correct band and mode flags. A wrong PC clock produces bad timestamps in the merged log.
  • Cabrillo. Before you submit, read the generated file in a text editor. Check the CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER and CATEGORY-MODE lines against what you actually did. Make sure each QSO line has the right frequency, mode, UTC date and time, and exchange fields. Most programs let you edit the header and re-export, so fix it there.
  • Submission. Most sponsors take either a web upload or an email to a log robot. Read the rules for the deadline, the file naming and the confirmation message. Keep the confirmation and your original files until the results are published.

Also, don't upload contest QSOs to LoTW or Club Log until you've finished cleaning the log. Removing dupes and fixing mistakes is easier before the QSOs go out.

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.