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 logging workflow for contests and daily operating: N1MM+, WSJT-X, Log4OM, ADIF, Cabrillo, LoTW and QRZ

ci_cover.jpg

I'm trying to design a logging setup that doesn't turn every contest weekend into a data-cleanup project. The goal is to avoid keeping three or four logs that disagree with each other. Here is the layout I'm considering, and I'd like corrections from people who have run something similar.

Contest logging would live in N1MM Logger+, with a fresh database per contest. N1MM handles dupe checking, the band map, rig CAT, rotator control and Cabrillo export. Everyday operating, including WSJT-X modes, would go into a general-purpose logger such as Log4OM. That logger would be the master log and the source for LoTW, QRZ and Club Log uploads. After a contest, I'd export ADIF from N1MM and merge it into the master log.

These are the points I think will cause trouble:

First, CAT sharing. Only one program can normally open a serial port, so N1MM, WSJT-X and the general logger can't all talk to the radio directly. The usual answers are a rig-control layer (Hamlib rigctld, OmniRig or flrig, depending on the radio and program support) or a virtual COM port splitter. I'd like to know which approach holds up best when WSJT-X and a logger need frequency and mode at the same time.

Second, ADIF mapping. ADIF is a standard, but programs differ in how they write modes, submodes, contest IDs and exchange fields. FT4 is a good example: depending on the ADIF version and the program, it can appear as its own mode or as a submode of MFSK. Before a bulk import into the master log, I plan to test with a small batch and check mode, band, frequency, station callsign and any contest-specific fields. If a mode comes out wrong, LoTW matching can fail even though the QSO itself is fine.

Third, Cabrillo. N1MM can generate the file, but the sponsor's rules decide what is valid: category, operator and power class, club name, and sometimes the soapbox or address lines. I'd rather read the contest's log submission instructions and fix the header fields in N1MM before export than edit the Cabrillo text by hand afterward. I'd also run the file through the sponsor's checker or upload page if one is offered, and keep the original ADIF.

Fourth, uploads. LoTW needs TQSL, a certificate for the callsign, and a station location that matches where the operating happened. A mismatched grid, DXCC entity or callsign is a common reason uploads get rejected or don't match. QRZ and Club Log use their own credentials or API keys. I'd test with a few QSOs first, since a bad bulk upload is annoying to undo. I'd also keep the PC clock accurate, because time errors hurt matching.

Finally, I'm unsure how to handle club operations. If several operators log on the same station, should each use a separate database or one shared one? And what's the cleanest way to hand a log to a club log coordinator without exposing credentials?

What would you change in this plan? I'm especially interested in CAT arrangements, dupe-sheet habits, and any ADIF import problems worth knowing about before the next contest.

  • Replies 2
  • Views 67
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

The split you describe is sensible, and the biggest risk is the merge step. I'd back up the master log before importing contest ADIF, and import only after checking a sample. Some loggers treat an incoming record as a duplicate if call, band, mode and time are close, while others just import everything. If you're unsure how your logger behaves, run the import into a test database first. Also decide in advance whether contest QSOs should be uploaded from N1MM or only from the master log. Uploading the same QSOs from both places can create duplicate entries on QRZ or Club Log.

On CAT, the right choice depends on the radio. If the radio's CAT is serial over USB, a single program owning the port is simplest, with the others reading through a Hamlib or flrig layer. For rotators, N1MM can control one directly, but if the same controller also serves another program, use a shared interface rather than letting two programs fight over the port.

One more item for the plan: keep the ADIF export from the contest log untouched. If the master log import goes wrong, you can redo it without regenerating anything.

  • Administrators

I'd add dupe handling to the list, because it behaves differently in the two places. In a contest, dupe checking follows that contest's rules, usually by band and often by mode. Your everyday logger probably has looser rules, so a contest QSO might look like a duplicate of an earlier casual contact once merged. Check that the import doesn't delete or skip records just because call and band match.

For WSJT-X, the decode and log flow is a little different. WSJT-X can write its own ADIF log, and it can send logged QSOs by UDP to other programs. A general logger can listen for those. Decide which one is the source of truth and don't import the same QSO from both the UDP feed and the ADIF file. If you also run N1MM+ for a digital contest, read its documentation on WSJT-X support, as the setup depends on the version and contest.

For club use, a shared database can work, but separate files per operator are easier to audit. Merge them after the event, then submit a single Cabrillo. Whoever submits should confirm the callsign, category and operator list against the contest rules before sending, because those header fields are easy to get wrong and hard to fix later.

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.