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 log workflow: N1MM+ for the run, WSJT-X on the side, then clean ADIF/Cabrillo and uploads to LoTW, QRZ and Club Log

ci_cover.jpg

Looking for a sanity check on a logging workflow that covers a weekend contest and the day-to-day log in one chain without creating a mess. The plan is below. Please poke holes in it, and add how DXKeeper, HRD, Logger32 or Log4OM users would handle the same steps.

Contest side. N1MM Logger+ is the contest logger. It handles the entry window, dupe checking, the band map fed by a cluster or skimmer, rig control, and rotator control. After the contest it generates the Cabrillo file for submission and exports ADIF for the main log.

Everyday side. WSJT-X handles FT8 and FT4 and is the source for those QSOs. A general-purpose logger such as Log4OM, DXKeeper or HRD Logbook is the master log. That logger pushes to LoTW (through TQSL), QRZ Logbook and Club Log.

The questions that matter most:

1. Rig control. N1MM+, WSJT-X and a rotator program all want the radio at once, and a serial port can only be opened by one program. What is the cleanest way to share CAT: a rigctld or flrig-type server, OmniRig, or a virtual port splitter?

2. Which direction does data flow? One option is WSJT-X to the master logger over UDP, and N1MM+ to the master logger by ADIF after the event. Another is everything into N1MM+. The first seems to leave fewer places for the same QSO to be entered twice.

3. After a contest, should the ADIF go into the master log before or after the Cabrillo has been submitted? And what is the right way to avoid pushing a few thousand QSOs to LoTW or QRZ with the wrong station location or a half-checked mode field?

4. Dupe handling across the whole chain. The contest logger's dupes are defined by that contest's rules. A general logger's dupe logic is usually call plus band plus mode within a time window. Those are different definitions, and they will disagree.

  • Replies 2
  • Views 11
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On CAT sharing: the underlying problem is that most radios expose one control channel, and the operating system only lets one program hold that serial port. The usual fix is to put a single program in charge of the port and let everything else talk to it. That can be rigctld from Hamlib, flrig, or OmniRig. A virtual serial port pair or splitter is the other route. A server like rigctld or flrig is generally more predictable than splitting ports, because it queues commands instead of having two programs fight over timing. Whichever you pick, check that each program you run actually supports it. Support varies by program and version, so read each one's documentation instead of assuming.

With WSJT-X it helps to separate three things in your head. CAT (frequency, mode, PTT), audio (the sound card path), and the UDP messages it broadcasts to loggers. UDP is how a logger like Log4OM can pick up the decoded callsigns and the logged QSO without parsing wsjtx_log.adi. If both WSJT-X and N1MM+ are open on the same machine, double-check that only one of them is configured to log FT8, or you will end up with duplicates that no dupe check can sort out, because they are legitimately the same QSO entered twice.

Clock accuracy deserves a line item of its own. FT8 and FT4 rely on tight time sync, and every log you upload is in UTC. If the PC clock drifts, you get failed decodes, and you also get QSO times that will not match the other station's log. Keep the computer synced to a time source before and during the event.

For rotators, the logger usually just sends a bearing computed from the callsign's prefix, a looked-up grid, or a click on the band map. The rotator controller program then does the work. It is the same sharing problem as CAT, so give the rotator its own port and its own program instead of routing it through the rig path.

  • Moderators

On the back end, treat the contest ADIF and the Cabrillo as two separate outputs with different purposes. Cabrillo is the entry to the sponsor: a text header (callsign, contest name, category fields like operator, band, power and mode, plus name and address) followed by one QSO line per contact. QSO lines carry frequency in kHz, mode, UTC date and time, your call and sent exchange, and the other station's call and received exchange. Because the contest logger builds it from that contest's rules, open the finished file in a text editor and read the header and the first and last QSO lines before uploading. Wrong category lines and mangled exchange columns are far easier to catch there than after the robot rejects the entry. Submission is normally through the sponsor's web upload or a log-checking robot, and each contest's rules page says which. Follow the deadline and file naming given there.

ADIF is for your own records and for the services. It is a tagged format where each field declares its length, so something like a callsign is written as the field name, the character count, then the value. Contest-related fields such as the contest ID and the sent and received exchange strings travel with the QSO. Mode handling is a common trouble spot. Digital modes can be written as a main mode plus a submode, and different programs and different ADIF versions do not always map FT4 and similar modes the same way. After an import, spot-check a handful of digital QSOs in the master log before trusting them.

Before any bulk import, make a backup of the master log database. Then import into a copy, turn on the logger's skip-duplicates option, and compare the QSO count before and after. Your point about differing dupe definitions is real: the contest logger's dupes follow the contest rules, while the general logger matches on call, band, mode and a time window. Don't assume the two counts will agree.

For the uploads: LoTW goes through TQSL, which signs the data with your callsign certificate. The Station Location in TQSL has to describe where the radio actually was (grid, CQ and ITU zones, DXCC entity), and QSO dates have to fall within the certificate's valid range. Upload a small batch first and read what TQSL reports. QRZ Logbook uses an API key for the specific logbook and generally flags QSOs it already has as duplicates, so read the result summary after the upload. Club Log accepts ADIF uploads and can also take QSOs in real time from a logger that supports it, so enable only one of those routes to avoid pushing the same QSOs twice. DXKeeper has built-in upload functions for several of these services. Log4OM and HRD offer similar upload options, and the exact steps vary by version.

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.