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, several loggers: how do you keep N1MM+, WSJT-X, Log4OM and the LoTW/QRZ/Club Log uploads from becoming a mess?

ci_cover.jpg

Many stations end up with a split setup. N1MM+ for the weekend contests, WSJT-X for FT8/FT4, and something like Log4OM, DXKeeper, HRD Logbook or Logger32 as the "main" log for awards and confirmations. Each program is good at its own job, but the trouble starts when the same QSOs have to move between them and then out to LoTW, QRZ, Club Log and a contest sponsor.

Here is a workflow that tends to hold up, with a few places where it commonly breaks. Please poke holes in it.

1. Pick one master log. Whichever program it is, treat it as the single place where QSOs are merged, and treat everything else as a source or a sink. The usual failure is two programs both uploading to LoTW or QRZ, so one has to deal with duplicates and the other has stale data. Decide which program does each upload and turn the others off.

2. Contest QSOs go from N1MM+ to the master log by ADIF. After the contest, finish all dupe and edit work inside N1MM+ first, then export ADIF and import that file into the master log. Export the Cabrillo from the same cleaned-up database. If you fix a callsign in the master log but not in N1MM+, the Cabrillo you submit will not match what you confirm.

Before importing, check that CONTEST_ID, STX/SRX (serial numbers) and any exchange fields map to something sensible. Many loggers import them as user-defined or APP_ fields, which is fine, but you want to know that before 3,000 QSOs go in.

3. WSJT-X via UDP, not by hand. WSJT-X writes wsjtx_log.adi and sends a logged-QSO message over UDP. Log4OM, JTAlert, GridTracker and some others can listen for it. That gives you live logging, with dupe and worked-before colouring where the client supports it, instead of a batch import at the end of the night. Make sure the UDP port and multicast or unicast settings agree between programs. Two programs listening on the same unicast port is a classic reason one of them logs nothing.

Also note how FT4 is represented. Different programs have represented it as its own mode or as an MFSK submode, depending on the ADIF version and their own mapping. If LoTW or another service rejects or misclassifies those QSOs, check the MODE and SUBMODE fields in the exported file before blaming the service.

4. CAT and rotator: one owner per COM port. This causes more weekend-morning panic than anything else. A serial CAT port can generally be opened by only one program at a time. If WSJT-X and N1MM+ both need rig control, you need something in between: a rig control server (flrig, Hamlib rigctld, OmniRig, depending on what the programs support), a virtual serial port splitter, or a radio with two independent CAT ports. The same applies to rotator control. Let one program own the rotator interface, and have the others send it commands or just read azimuth.

When switching from contesting to digital, check the radio's data mode, audio routing and the split/transmit-VFO behaviour. A logger that reads the wrong VFO will happily log the wrong frequency, and then the band in your ADIF is wrong too.

5. Uploads. LoTW needs TQSL, a valid callsign certificate and a station location whose grid, CQ zone and ITU zone are correct for where you actually operated. A QSO signed with the wrong station location can fail to match. QRZ Logbook uploads use the API key for the specific logbook, and Club Log needs your account credentials or an app password for third-party uploads. For all three, check whether your logger can upload each QSO as it is logged or only in batches, and make sure the same QSOs are not being pushed from two places.

6. Contest log submission. Cabrillo is a plain text format, but sponsors are picky about the header: CATEGORY-OPERATOR, CATEGORY-POWER, CATEGORY-BAND, CLUB, and the exchange fields in each QSO: line. Open the file in a text editor before submitting. Check the callsign, the categories, the QSO count and a few sample lines. Then read that contest's rules for the filename, deadline and upload method, since those differ. Club Log is useful for DXCC and your own records but is not a substitute for the sponsor's submission.

Questions for the thread: Which program do you use as the master log and why? What do you do about the FT4/MFSK mapping and about duplicate uploads? And does anyone have a clean way to share CAT between a contest logger and WSJT-X?

  • Replies 2
  • Views 49
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The single-owner rule is the part that matters most. I'd extend it to anything that touches the rig: the logger, the digital program, the rotator controller, and even the tool that does band-map spotting. Draw it on paper. Rig, CAT port, who owns it, who talks to it through a server. Most "it worked last week" problems are two programs fighting over one port after an update or a USB re-enumeration changed the COM number.

On the dupe side, I'd keep your contest logger and master log philosophies separate. In N1MM+ a dupe is defined by the contest rules: per band, per band and mode, or once ever, depending on the contest. In a general log, the same callsign on the same band and mode on the same day is a different question. So don't import contest QSOs into the master log and expect its dupe check to behave the same way. Import them with the contest ID kept, so you can filter them later.

One more thing on ADIF: always do a small test import first, maybe 20 QSOs, and look at what landed in the fields. Compare frequency, band, mode/submode, RST, grid and the exchange fields against the original. It takes five minutes and saves a mass cleanup.

  • Administrators

I'd push back slightly on making the general logger the master for everything. It depends on what you care about. If your main goal is awards and confirmations, then yes, a master log in Log4OM, DXKeeper or similar is where it all ends up. But if you contest seriously, the N1MM+ database is the record of the contest and it should be archived as is, with the original .s3db file or equivalent, plus the exported ADIF and the submitted Cabrillo. If a sponsor asks a question or a robot reports a mismatch, you want the exact data you submitted.

For uploads, the cleanest approach is probably to let the master log handle LoTW, QRZ and Club Log, and have N1MM+ do none of them. With LoTW especially, check the TQSL station location before the first batch from a contest. Operating from a different grid, a club station or a portable location needs its own location entry. If those QSOs get signed against your home location, they usually just don't match, and it's annoying to fix later.

For FT8/FT4, the UDP route into the master log is good, but watch the time. If the PC clock is off, you'll see it in decodes first and in your ADIF timestamps second. Logging in UTC with a synced clock is what makes the confirmations match up on the other end.

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.