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

Keeping N1MM Logger+, WSJT-X and a master log in sync: ADIF, Cabrillo, LoTW/QRZ/Club Log uploads and CAT sharing

ci_cover.jpg

Many stations end up with three logs: a contest logger (N1MM Logger+ is the usual choice), WSJT-X writing its own wsjtx_log.adi, and a long-term "master" log in Log4OM, DXKeeper, HRD Logbook or Logger32. Each one has a different idea of what a QSO record should contain, and the problems tend to show up at the worst times: a contest log that won't convert cleanly, duplicate QSOs after a re-import, or a CAT port that only one program can open.

This thread is for comparing workflows. Here are the main friction points, and I'd like to hear which approaches hold up.

1. Who owns the radio? Only one program should normally own the serial or USB CAT port. Common setups are to let the main logger or a rig-control program (flrig, OmniRig, Hamlib rigctld, or the vendor's own tool) be the master, and have the other programs connect to that instead of opening the COM port directly. The same applies to rotator control. Decide which program talks to the rotator interface, and let the others use a shared service such as rotctld or PstRotator, or leave rotator control out of them. Band map click-to-tune and band/mode following only work properly if every program agrees on the VFO and split state.

2. WSJT-X into the logger. WSJT-X can log automatically to its ADIF file, and it can broadcast logged contacts over UDP. N1MM Logger+ and Log4OM can both take that feed, though they use different settings. The question is whether a contact is logged once or several times, for instance in WSJT-X's file, the contest logger and the master log. Having one "primary" destination and treating the others as import-only copies cuts down on duplicates.

3. ADIF round trips. ADIF is flexible, but programs differ in how they write or read mode/submode (FT4 is one example that has historically been handled differently depending on ADIF version and software), frequency units, band, and custom fields like contest exchange or APP_ tags. Always back up before a big import, and run a test import with a small date range. Check that TIME_ON is UTC, that BAND and FREQ agree, and that your own grid, CQ zone and ITU zone are right if they're written to the record.

4. Cabrillo is not a log backup. Cabrillo is a contest submission format, and every contest defines its own exchange and category rules. It's good for sending to a sponsor, but it's lossy for your own records. Keep the native contest database and an ADIF export. Before submission, check the header fields (CALLSIGN, CATEGORY-*, CLAIMED-SCORE, operator and club info if needed), the band/mode mapping, and whether the exchange columns match the rules. Then follow the sponsor's upload or email instructions and look for a confirmation or log-receipt page.

5. Confirmations and uploads. LoTW needs TQSL, a valid certificate for the callsign, and a station location that matches the QSO (callsign, grid, DXCC entity and zones). A wrong station location is a common reason for uploads that are signed but never match. QRZ Logbook and Club Log use their own credentials or API keys, and their duplicate handling differs. If you use real-time upload from the logger and also do bulk ADIF uploads, you can create confusing results.

6. Dupe checking and band maps. Contest dupe rules (per band, per mode, or per band-mode) are set in the contest definition, but a master log's "worked before" check is a different concept. Spots on a band map will only be flagged as dupes if the band map uses the contest log's rules. Do you rely on cluster or Reverse Beacon Network spots in contests, and are they marked correctly for needed multipliers?

So what does your workflow look like: one primary logger and periodic ADIF imports into the master log, or live UDP/ADIF feeds into several programs? What do you do about CAT arbitration and about preventing duplicates?

  • Replies 2
  • Views 75
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One way to keep things sane is to treat the logs by role. The contest logger is the authority for the contest period. WSJT-X is just a decoder with a scratch log. The master log gets a clean import afterwards.

For CAT, a single program should own the physical port, and everything else should connect through a shared layer. N1MM+ can handle radio control itself, but if WSJT-X also needs to key the rig or set frequency, then one of them has to give up its direct port, or you have to use a rig-control middleman. Make sure the baud rate, split mode and data mode (USB-D or DATA) are set consistently, or the band map will show confusing frequencies.

After the contest, I'd export ADIF from the contest logger rather than converting from Cabrillo. Cabrillo drops information such as full frequency precision and fields the sponsor doesn't care about. Import the ADIF into the master log into a test copy first, scan for oddities (mode, submode, band, operator, and your own grid), then do the real merge. After that, upload to LoTW, QRZ and Club Log from the master log only, so you have one place where the upload status is recorded.

  • Moderators

On duplicates, it helps to separate two kinds. There are contest dupes, where the same station is worked again on the same band and mode under the contest rules. Then there are database duplicates, where the same QSO record gets imported twice. The first is a rules matter and the logger handles it live. The second is a data-hygiene matter, and you only avoid it with a consistent import path. Most logging programs match on callsign, date and time (within some tolerance), band and mode, but the details vary. A mode mismatch such as MFSK/FT4 versus a plain digital mode, or a time zone error in the import, is enough to defeat the matching.

For LoTW, check the station location before you sign a big batch. If the grid, DXCC entity or zones are wrong, you can end up with a perfectly signed upload that never matches. Re-signing the whole batch takes time, and a mistake might even create duplicate-looking records on the LoTW side. DXKeeper, Log4OM, HRD and Logger32 all have some way to set or confirm this, but the field names differ, so compare the exported ADIF against a record you know is correct.

For Cabrillo submission, the most common errors I'd look for are a wrong category line, a callsign in the header that doesn't match the one used on the air, and exchange fields shifted by a column. Open the file in a text editor before you upload it. If the sponsor's site gives a log-checking report, use it to make sure your own logging setup is right for next time.

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.