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-shot logging workflow: N1MM+ for contests, WSJT-X/Log4OM for digital, then ADIF to LoTW, QRZ and Club Log. Where does it break?

ci_cover.jpg

I'm planning a logging setup before the next contest season and want to sanity-check the data flow. The goal is one master log I trust, with as little retyping and cleanup as possible.

The plan has three parts:

Contests: N1MM Logger+ with CAT control of the rig, a rotator interface, and a band map fed by a telnet cluster and a CW skimmer. Cabrillo gets exported for the sponsor's log robot, and an ADIF export goes into the main log afterward.

Everyday digital: WSJT-X for FT8 and FT4, using the UDP server so Log4OM 2 picks up the logged QSOs automatically. Log4OM would be the master log.

Confirmations: Log4OM uploads to QRZ Logbook and Club Log, and LoTW goes through TQSL signing.

Here are the places I expect trouble, and I'd like to hear where people have seen them go wrong:

1. CAT port ownership. WSJT-X, N1MM+ and Log4OM all want the radio. I assume the answer is either one program owning the serial port with the others slaved to it, or a shared layer such as Hamlib's rigctld or Omni-Rig. What is the least fragile arrangement when you switch between a contest and a digital session?

2. Mode and submode mapping on ADIF export and import. FT8 and FT4 don't always arrive the same way. FT4 is generally carried as MFSK with an FT4 submode, and some programs mishandle that. I don't want LoTW or a contest scorer to see a mode it doesn't recognize.

3. Cabrillo versus ADIF. I understand Cabrillo is a sponsor-specific, fixed-column text format for scoring, while ADIF is the general-purpose log exchange format. Cabrillo is not a good way to move logs between programs, because it loses fields. Is that right?

4. Dupe rules. Dupe checking depends on the contest rules: per band, per band and mode, or once for the whole contest. How do you make sure the logger is configured for the right ruleset before the first QSO and not discovered halfway through?

5. LoTW upload timing. TQSL needs a station location with the right grid, CQ and ITU zones and DXCC entity, and the certificate has a valid QSO date range. I'd like to know what gets silently rejected when a QSO falls outside that range or the station location doesn't match.

Is this workflow sound, or is there a simpler path? I'm also interested in how DXKeeper, HRD Logbook or Logger32 users would handle the same chain.

  • Replies 2
  • Views 13
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The flow is sound. The biggest weak point is the master log, so I'd treat it as an explicit decision.

On CAT: a serial port can only be opened by one program at a time. If WSJT-X, N1MM+ and Log4OM are all configured for COM5, whichever starts second usually fails or behaves oddly. Practical options are to run only one of them against the radio at a time, to put a rigctld instance in front of the radio and point the programs at it, or to use a virtual serial port splitter. Everything also has to agree on baud rate, data and stop bits, CI-V address if it's an Icom, and the handshake settings. One more thing to check is DTR and RTS. If they are used for PTT or CW keying, an unintended state on a shared port can key the transmitter. In WSJT-X, set PTT to CAT or VOX deliberately, and check what the other programs do with those lines.

On mode mapping: before relying on the chain, export a handful of test QSOs in each mode (CW, SSB, FT8, FT4, RTTY) as ADIF and look at the raw file. Check MODE, SUBMODE, BAND, FREQ, STATION_CALLSIGN, OPERATOR and MY_GRIDSQUARE. If the grid or station callsign is blank, that's often what breaks LoTW matching later. Importing the file into a scratch database before touching the real one costs little.

On Cabrillo: you're right. It's a scoring and submission format. A Cabrillo file has a header (CALLSIGN:, CATEGORY-OPERATOR:, CATEGORY-BAND:, and so on) followed by QSO: lines whose columns depend on the contest. Fields like grid, comments and your own notes don't survive. Dupes may appear as X-QSO: lines depending on how the software writes them. Always export ADIF from the contest database for your master log, and generate Cabrillo only for the sponsor.

Always read the sponsor's rules for the file name, the submission address or upload page, the deadline, and whether a robot sends a confirmation. Those details vary by contest and change over time, so don't trust last year's notes. Most sponsors also publish a Cabrillo checker or accept the file with a log summary, so run your file through that before submitting.

  • Administrators

I'd add a few points about what happens on the contest side and with uploads.

Dupe checking is only as good as the contest setup. In N1MM+ the dupe rules come from the contest you select when creating the database, and a new database is typically created for each contest. If you pick the wrong one, or edit the exchange fields incorrectly, both the dupe sheet and the multiplier counts can be wrong. Check the entry window for a few sample calls on different bands and modes. Mixed-mode contests are the usual trap: some treat CW, phone and digital as separate for dupes, others don't. Also keep the band map sources straight. Spots that appear in a different color for worked stations only help if the log and the contest are set up correctly.

For the band map, a cluster feed and a skimmer feed behave differently. Cluster spots can be wrong or delayed, and skimmer spots depend on the receiver. Treat both as leads, not as guarantees of what's on the air. When a spot of yours looks wrong, check the frequency offset before concluding the other station is off. For rotators, make sure the logger's idea of the beam heading comes from the same controller you actually drive (PstRotator, a hardware controller, or rotctld). Two programs commanding the same rotator is a quick way to get strange headings.

For uploads: after a contest, import the ADIF into your master log, de-duplicate, and then upload. QRZ Logbook uses an API key tied to a specific logbook, and Club Log uses your login or an application password, so store those in the logger settings and don't paste them into forum posts. LoTW is the fussy one, because TQSL signs each upload against a station location and certificate. If the QSO date or entity doesn't match, it can reject the record, so look at the TQSL log after each run instead of assuming everything went up.

If you use DXKeeper or HRD Logbook as the master instead of Log4OM, the same principle holds. Pick one program as the source of truth, import ADIF into it, and run the confirmation uploads from there. Don't upload from several programs to the same service, because that is how duplicate QSOs and confusing confirmation states get created.

Finally, back up the database and the raw ADIF files before any bulk import, and keep the WSJT-X wsjtx_log.adi as an independent copy.

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.