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

Contest-to-confirmation workflow: N1MM+, WSJT-X, ADIF cleanup, Cabrillo, then LoTW, QRZ and Club Log

ci_cover.jpg

Looking for a sanity check on a logging pipeline for mixed-mode weekends. The plan is N1MM Logger+ as the main contest log, WSJT-X for FT8/FT4 outside the contest or in digital-friendly events, and a general-purpose logbook (Log4OM, DXKeeper, HRD Logbook and Logger32 all seem to be in use) as the permanent record. After each operating session, the logs would go to LoTW, QRZ and Club Log, and the contest log would go out as Cabrillo.

The pain points I keep reading about are these:

1. Which log is the master? If N1MM+ holds contest QSOs, WSJT-X writes its own ADIF, and the permanent logbook also receives UDP logged-QSO messages, it is easy to end up with the same QSO in three places and then upload it three times.

2. ADIF export and import between programs. Mode and submode handling for newer digital modes, contest exchange fields (STX/SRX, SRX_STRING, CONTEST_ID) and app-specific fields do not always survive a round trip.

3. Cabrillo is a separate output from ADIF, with its own header and its own per-contest column layout. A clean ADIF export does not guarantee a Cabrillo file the sponsor's checker will accept.

4. CAT and rotator sharing. Only one program can normally own a serial port, so the radio, the logger, WSJT-X and the rotator controller all want the same resources.

How do you structure this so the data goes one direction and nothing gets uploaded twice or mangled? Is there an order of operations you would insist on?

  • Replies 2
  • Views 40
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Pick one program per job and make the data flow one way. A reasonable split is that the contest logger owns contest QSOs, the permanent logbook owns the long-term record, and the upload services are downstream of the logbook rather than of every program.

For the contest itself, let N1MM+ do the dupe checking, the exchange parsing and the Cabrillo output, because those are all driven by the contest's rule definition. Dupe rules are per contest, and band and mode grouping can differ. Digital usually counts as one mode category for dupes, but that is a rule of the logger's contest definition, so confirm the setting in the logger and the sponsor's rules and do not assume it.

After the contest, export ADIF from N1MM+ and import it into the permanent logbook once. Then spot-check a handful of QSOs for frequency, band, mode, time and the exchange fields. Look at time first. Everything should be UTC, and a PC clock that is off, or a local-time setting somewhere, will quietly cause not-in-log errors for your partners. Most logbooks check for duplicates on import, but the matching window and the fields they compare vary, so verify rather than trust it.

For uploads, send from the logbook only. LoTW (through TQSL) and Club Log both tolerate re-sending QSOs they already have, and QRZ's logbook generally does too, but a clean single source still makes troubleshooting easier. If you ever need to work out why a QSO is not confirming, you want exactly one place to look.

  • Moderators

On the CAT and WSJT-X side, a common fix for serial contention is to stop letting every program open the COM port directly. Run one rig-control layer (Hamlib's rigctld, OmniRig on Windows, or flrig, depending on the radio and the programs) and point the loggers at it. N1MM+, WSJT-X and most of the general logbooks have support for at least one of these, but check the exact list for the versions you run, because it changes. The rotator follows the same logic. Keep one owner for the rotator interface and have the logger talk to it through whatever it supports, rather than two programs opening the same port.

WSJT-X's UDP messages work the same way. It sends to one address and port by default, and if two programs bind that port the second one usually fails or only one receives data. Multicast on the UDP server address, or a relay or forwarder tool, lets several listeners see the same stream. That is how you get one logged QSO to land in the contest logger and the logbook without exporting files. Just remember that this creates exactly the duplicate problem from your point 1, so decide up front which one is the record and treat the other as a view.

For the ADIF mismatches, test with a small file before a big weekend. Make a few FT8, FT4, CW and SSB QSOs, export, import into the second program, then export again and compare. Watch the MODE and SUBMODE fields in particular. If a QSO's mode or submode is wrong on import, LoTW may reject it or Club Log may count it differently, and it is much easier to fix the mapping before you have thousands of records.

Last, before you submit a Cabrillo file, read the sponsor's instructions for the header (category, operator class, club name for club scoring, soapbox, address) and for where the file goes, whether that is a web upload or an email address. Open the .log in a text editor and read the first dozen QSO lines. If the columns look wrong there, they are wrong to the checker as well.

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.