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-station logging workflow: N1MM+ for contests, WSJT-X into Log4OM, and keeping ADIF, Cabrillo, LoTW and QRZ in sync

ci_cover.jpg

I'm putting together a logging setup that covers both contest weekends and everyday operating, and I'd like to compare notes on where the pieces tend to break. The idea is to use N1MM Logger+ for contests, WSJT-X for FT8/FT4 with its QSOs forwarded to Log4OM, and Log4OM as the long-term master log. The master log would push to LoTW, QRZ and Club Log. DXKeeper, HRD Logbook and Logger32 are all reasonable alternatives to that last piece, so feel free to say how they would handle the same job.

These are the points where I expect trouble:

1. Moving QSOs between programs. The contest log lives in N1MM+ and has to end up in the master log. ADIF export from N1MM+ and import into Log4OM works, but contest exchanges can land in odd places. Serial numbers, zones and state/province fields do not always map onto standard ADIF fields the way you would expect. Before importing a whole weekend, it is worth testing a small batch and checking where the exchange data ends up. Import settings that suppress duplicates are also important, so a re-import doesn't create doubles.

2. Cabrillo. Cabrillo is generated from the contest program, not from the master log. The usual order is to finish and clean the log in N1MM+, check the header fields (category, operator class, power, bands, club name, address), export the Cabrillo file, and read it in a text editor before submitting. Each sponsor's rules decide which categories are valid and how the file must be sent, whether by web upload or email, so the rules page matters more than the software defaults.

3. CAT and rotator control. Most rigs only give you one serial port for CAT, so N1MM+ and WSJT-X cannot both open it directly. The common ways around that are a virtual serial port splitter, OmniRig, or Hamlib's rigctld. Rotator control has the same limit: one program owns the port. Where the rig and rotor interfaces allow it, I'd like to hear which approach people consider least fragile.

4. Uploads. LoTW needs TQSL with a valid certificate, and the station location in TQSL has to match what you operated from (grid, DXCC entity, zones). QRZ Logbook and Club Log use API keys. Check which account level your QRZ access requires before building automation around it. Club Log's API access also depends on keys and application permissions.

So: what is the cleanest way to make sure each QSO exists once in the master log, with the right station callsign, operator and grid, no matter which program first logged it? And has anyone found a good way to keep contest-only data out of the uploads?

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Start with the fields that identify the station. If STATION_CALLSIGN, OPERATOR, MY_GRIDSQUARE and MY_STATE (or the equivalent) are missing or inconsistent, the other fixes only hide the problem. Set them once in each program's station profile. A contest exported with a club callsign as station and your own call as operator is handled very differently by LoTW and QRZ than one where both fields say the same thing. That mismatch can cause rejected or unmatched uploads.

Time is the second common source of doubles. ADIF expects UTC date and time, and an import with the wrong timezone assumption shifts QSO times. Dupe checking in the master log then fails, because a QSO that is the same contact looks like a different one. Test the import with a handful of QSOs near midnight UTC, since date rollover is where mistakes show first.

On Cabrillo, I'd treat the exported file as a read-only artifact. If something is wrong in the file, fix the log in N1MM+ and re-export, rather than editing the Cabrillo by hand. Hand edits tend to be forgotten, and the next export overwrites them. The exception is a header typo, which is fine to change in a text editor as long as the file still follows the sponsor's format.

For dupes during the contest itself, N1MM+ checks by callsign plus band, and for mode it uses mode groups (CW, phone, digital), not each mode separately. That matches how most contests count QSOs, but some sponsors count differently. Look at the contest's rules before assuming the defaults suit it.

  • Moderators

On CAT, the simplest arrangement is to let only one program talk to the radio and have the rest read frequency and mode from it. N1MM+ can do that for digital work through its own interface to WSJT-X, and Log4OM can read from a CAT-sharing layer. A splitter is fine if your radio and driver behave, but two programs polling the same radio at different rates can produce odd frequency jumps. If you see the VFO bounce back to the previous band, a polling conflict is the first thing to rule out.

Don't run the WSJT-X log and the N1MM+ log as two masters. WSJT-X writes its own ADIF file, which is a convenient hand-off, but it is not the same as the master log. A tool like JTAlert or Log4OM's WSJT-X integration can forward each QSO as it's logged, which avoids a manual import after the session. Watch the pop-up confirmation. If you accept a QSO in two places, the dupes you create can be hard to find later.

For band maps, one useful habit is to let the cluster feed run in only one program at a time. Otherwise you get the same spot twice, and in a contest the spot you work in the other program doesn't mark the station as worked in the first. Check that spots are marked as dupes from the log you're actually using.

For uploads, I'd keep LoTW as a manual or scheduled batch from the master log, since a bad station location is better caught before signing. QRZ and Club Log can be more automatic, but send a few test QSOs first and look at the results on the website. Having a deliberate pause between logging and upload also gives you time to fix a busted callsign before it spreads to three services.

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.