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 master log across N1MM Logger+, WSJT-X and Log4OM: where ADIF, Cabrillo and uploads usually go wrong

ci_cover.jpg

I'd like to compare notes on structuring a logging workflow when several programs touch the same QSOs. A typical case is N1MM Logger+ for CW/SSB contests, WSJT-X for FT8/FT4 on the same rig, and a general-purpose logbook (Log4OM, DXKeeper, HRD Logbook or Logger32) as the long-term record that feeds LoTW, QRZ and Club Log.

These are the points where the chain tends to break, and I'd like to hear how people handle them.

1. Which program owns the master log? Pick one. The contest logger can own the log during the contest, then you export ADIF and import it into the long-term logbook afterward. The alternative is to have everything log live into one database. Mixing both without a rule leads to duplicate records, and those duplicates then get uploaded to LoTW, QRZ and Club Log.

2. ADIF round trips. ADIF is the interchange format, but each program adds its own APP_ fields and handles contest exchange fields differently. Check that the fields you care about survive an import: STX/SRX, SRX_STRING, CONTEST_ID, band, submode and grid. For digital modes, newer ADIF versions record FT8 as MODE=MFSK with SUBMODE=FT8, while older software expects MODE=FT8. If the mode comes through wrong, dupe checking and award tracking suffer.

3. Cabrillo is not an ADIF substitute. Cabrillo is a text format for submitting a contest log, and the QSO line layout depends on the contest. It's usually safest to generate it from the contest logger, which knows the exchange format, rather than converting ADIF with a generic tool. Then read the header (CATEGORY-OPERATOR, CATEGORY-POWER, CATEGORY-BAND, CLUB, and so on) before you send it, because the sponsor's robot will take those at face value.

4. CAT and rotator sharing. A serial port can normally be opened by only one program. If N1MM+ and WSJT-X both need the radio, you need a sharing layer such as flrig, Hamlib's rigctld, OmniRig or the commander component of a suite like DXLab. What is supported varies by program, so check each one's docs. The same goes for rotators, where a single controller or daemon should take commands from the logger's band map or bearing display.

5. Uploads. LoTW needs TQSL and a station location that matches where you actually operated (DXCC entity, grid, CQ and ITU zones). A wrong location setting gives you QSOs that never match. QRZ Logbook and Club Log uploads use credentials or API keys stored in the logger. Decide whether uploads happen live or in batches after you've cleaned up the log.

What order do you use for the post-contest cleanup: export Cabrillo first, or import and dedupe ADIF first? And what's your method for keeping WSJT-X contacts from being logged twice?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the double-logging problem, the cause is usually that two programs each log the same QSO. WSJT-X writes its own wsjtx_log.adi when you confirm a contact. If it also broadcasts the logged QSO over UDP to N1MM+ or Log4OM, you get one copy in the ADIF file and another in the logger's database. That's fine as long as you only import one of them into the master log.

A simple rule is to treat the WSJT-X ADIF as an archive and the logger's database as the working copy. If more than one program needs to listen to WSJT-X's UDP stream, check the address and port settings under Settings > Reporting. Several listeners on the same port can conflict unless you use a multicast address or a relay tool that forwards to each program separately.

Before importing into the long-term log, check the time base. Contest loggers and WSJT-X both record UTC, but if the PC clock has drifted, QSOs will be a few seconds off the other station's log. That can matter for LoTW matching and for sponsor log checking. Keeping the PC synced to an NTP source is cheap insurance.

  • Administrators

For the post-contest order, I'd do the Cabrillo export first, while the contest logger is still the authority for the exchange fields. Before sending it, run the logger's own dupe check and check the score summary, then open the file in a text editor. Look at the header, the callsign, and whether the QSO lines have the expected number of fields. Most sponsors have a web upload page or an email robot that confirms receipt, so keep that confirmation. Rules and deadlines differ from contest to contest, so read the current rules for each one rather than assuming last year's settings still apply.

After that, export ADIF from the contest logger and import it into the long-term logbook. Set a backup point first, because an import is hard to undo cleanly. A few things to check on the import:

Does the band/mode mapping come through correctly, especially for digital submodes? Did the logbook flag duplicates, or just add everything? Are your own station fields (grid, zones, operator) filled in correctly? Only then sign and upload to LoTW, and push to QRZ and Club Log.

On dupe rules: the contest logger applies the contest's own rules, such as one contact per band or per band and mode group. The long-term logbook has no such rule. A QSO that is a dupe for contest scoring is still a valid log entry, so don't delete it from the master log just because the contest logger marked it a dupe.

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.