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 to LoTW, QRZ and Club Log without duplicate or broken records: ADIF vs Cabrillo workflow check

ci_cover.jpg

I'm trying to design a logging workflow that covers weekend contests and everyday operating, and I'd like it checked for weak points. The idea is to run N1MM Logger+ for contests and WSJT-X for FT8/FT4 and digital contest modes. A general-purpose logbook (Log4OM, DXKeeper or HRD Logbook) would be the master log for LoTW, QRZ and Club Log uploads. Logger32 is also on the table if someone has a reason to prefer it.

Here is the flow I have in mind. During a contest, every QSO goes into N1MM+ and nothing else. Afterward I generate the Cabrillo file for the sponsor's log robot and export an ADIF file from the same N1MM database. That ADIF gets imported into the master logbook, which then pushes to LoTW (through TQSL), QRZ Logbook and Club Log. For WSJT-X, I'd either let it log to wsjtx_log.adi and import that periodically, or use UDP logging straight into the master logbook.

These are the points I'm unsure about:

1. ADIF round trip. Does the contest exchange survive the trip from N1MM+ into the master logbook? I'm thinking of fields like STX, SRX, STX_STRING, SRX_STRING and CONTEST_ID. I'd also like to know how FT8 and FT4 are represented, since I've seen MODE=FT8 in some files and MODE=MFSK with SUBMODE=FT4 in others, depending on the ADIF version.

2. Upload flags. If the master logbook imports records that already carry QSL_SENT or LOTW_QSL_SENT values, will it skip them or re-upload them? I don't want to flood LoTW or Club Log with duplicates.

3. CAT and rotator control. Only one program can own a serial port at a time. What's the cleanest way to share one radio between N1MM+, WSJT-X and a logbook? I'm weighing Omni-Rig, FLrig, a Hamlib rigctld instance, or a virtual COM port splitter. The same question applies to rotator control from the band map or from a callsign lookup.

4. Band map and dupe checking. How do you keep spots from RBN or a DX cluster feeding the band map without creating a mess, and what are the usual ways dupe checking goes wrong, such as band changes, mode groups and sprint-style rules?

5. Submission. Which mistakes get a Cabrillo file rejected or reclassified? I'm thinking of wrong category lines, frequency units, or callsign and time formatting.

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the ADIF round trip: ADIF is a loose container, and each program decides which optional fields it writes and reads. N1MM+ writes its contest exchange into standard fields where they exist (STX, SRX and the string variants) and CONTEST_ID where the contest has an ADIF identifier. Some of its own data goes into APP_N1MM_ fields, which other programs will usually ignore. Import one contest file into a scratch logbook first and check that call, band, mode, time, RST and exchange all arrive. If the master logbook drops something you care about, keep the original N1MM+ database and the Cabrillo as your contest record. The master logbook only needs enough data for confirmations.

Mode naming is a common source of trouble, so check what your logger writes against what each destination expects. Older ADIF versions put FT4 under MFSK as a submode. Newer ones list FT8 and FT4 as modes. LoTW, Club Log and QRZ each have their own rules for mode mapping, and TQSL reads modes through its own configuration, so an out-of-date TQSL or a stale config can reject or misclassify digital QSOs. Keep TQSL current, and do a small test upload before the big file.

On the upload flags, behavior varies by program and by import option, so don't assume. Many loggers have an "import and mark as already sent" choice, or a way to ignore incoming QSL status. If you import an N1MM+ export once, with no upload flags set, and let the master logbook upload everything that is not yet marked sent, you get a clean single pass. Duplicate uploads to Club Log and QRZ are generally recognized as duplicates, but don't lean on that for anything you can avoid.

For LoTW, the signing side matters too. The QSO has to match a TQSL Station Location with the right callsign, DXCC entity, grid and zones for where you were operating. A portable or contest-site QSO uploaded under your home location will not match correctly.

  • Administrators

For CAT, the rule is one owner per port, and everything else connects through a sharing layer. With a Hamlib rigctld, FLrig or Omni-Rig setup, the logger and WSJT-X both talk to the sharing layer and neither opens the COM port directly. WSJT-X can use Hamlib, and also supports Omni-Rig, DX Lab Commander and HRD as rig control options. N1MM+ can use its own radio interface or Omni-Rig. It is usually easier to pick one method and use it for both than to mix several. Set baud rate, stop bits and handshake to match the radio's menu. If the radio has a built-in USB audio codec, check the Windows sound devices too, because a changed default device or an input level change will stop decodes or push the wrong power into the rig.

For FT8 specifically, clock accuracy decides whether you decode or not. Keep the PC clock synced with an NTP tool, and keep the logger's UTC settings consistent, otherwise the time_on values in the log will disagree with what the other station logs. LoTW matches on date and time within a window, so a clock that's several minutes off can cost you confirmations.

For WSJT-X in a contest, the UDP route is worth setting up if your logger supports it. N1MM+ and Log4OM both have ways of accepting WSJT-X UDP traffic. This is easy to get wrong with two programs listening on the same port, so check which one is meant to own the UDP port and whether the other needs a different setting or a forwarder. If you instead import wsjtx_log.adi later, keep the file backed up and note the time you started so you don't import the same session twice. Dupe checking depends on the contest rules. Some contests count a station once per band, some once per band and mode group, and a few have special exchanges. Set the contest in N1MM+ before the first QSO and make sure the operating category you choose is what you'll submit in the Cabrillo header.

For band maps, spot sources give you a lot of data and little context. A spot is a hint. Filter by band, mode and age, and let the logger flag spots for stations you've already worked on that band, so a stale spot doesn't pull you off frequency. Rotator control from the band map usually works through a rotor program or Hamlib rotctld. The logger needs to know the bearing source, so check that your grid or home coordinates are correct. A wrong grid gives you wrong beam headings even though everything appears to be working.

For submission, read the contest's current rules and their log checking instructions rather than relying on memory. In general: use the Cabrillo header fields exactly as the sponsor's log robot expects, check that the category and band lines match what you actually did, confirm your callsign is as you transmitted it, and look at a few QSO: lines before upload. Frequencies in Cabrillo QSO lines are normally in kHz, with the time in UTC. Keep the original log, and watch the deadline, which differs by contest.

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.