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 or several? Keeping N1MM+, WSJT-X and Log4OM in sync for contests, LoTW, QRZ and Club Log

ci_cover.jpg

Here's a setup question that comes up whenever someone runs both contest and everyday operating on one station: where should the master log live, and how do QSOs get from one program to another without duplicates or mangled fields?

Take a common arrangement. N1MM+ handles the serious CW and SSB contests. WSJT-X handles FT8 and FT4 on non-contest days, and sometimes in digital contests. Log4OM or DXKeeper is the long-term log that feeds LoTW, QRZ Logbook and Club Log. Meanwhile CAT control, the rotator and the band map all want to share the same radio and the same serial or network resources.

These are the friction points worth sorting out before the next contest weekend:

1. ADIF round trips. ADIF is the common currency, but programs are not equally strict about it. Contest-specific exchange data (STX/SRX, STX_STRING/SRX_STRING, CONTEST_ID, ARRL_SECT, and so on) may be dropped or remapped on import. Mode and submode handling also differs. FT8 is its own MODE in current ADIF versions, while FT4 is carried as MFSK with SUBMODE FT4. An older program may reject or misclassify these. Before trusting any import, load a small test file and check what happened to mode, band, frequency, and the date and time fields.

2. Cabrillo is not a log format for storage. It's a submission format, and each sponsor defines its own exchange layout. Generate it from the contest program with the correct contest selected, not from a general-purpose logger's ADIF. Check the header (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER, and so on) against the rules, and read the QSO lines. Frequency should be in kHz on HF, and the mode code should be CW, PH, FM, RY or DG as appropriate.

3. Upload order. LoTW needs TQSL to sign the file, and the station location (callsign, grid, DXCC entity, zones) has to match the QSOs. QSO dates must also fall inside the certificate's valid range. QRZ Logbook uses a per-logbook API key. Club Log uses account credentials plus an application password or key. If the logging program uploads automatically on every QSO and you also do a bulk ADIF upload later, you can end up with duplicate or conflicting records. Pick one path per service.

4. Shared UDP and CAT. WSJT-X can broadcast logged-QSO and status messages over UDP. If JTAlert, GridTracker, N1MM+ and Log4OM all want that stream, a single unicast port can be claimed by only one listener. Multicast is the usual workaround. Similarly, only one program should open the radio's COM port directly. Everything else should go through a CAT sharing tool, such as Commander in the DXLab suite, OmniRig, Hamlib's rigctld, or the logger's own radio server.

So the question for everyone: do you keep one authoritative log and import into it after each event, or do you let each program upload on its own? And what has the best track record for you with dupes, band maps and rotator control when the pileups start?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd lean toward a single authoritative log and treating contest software as a temporary working copy. The usual pattern is to run the contest in N1MM+, export ADIF and Cabrillo from the same finished contest database, and import the ADIF into the long-term logger afterward. Then you only upload to LoTW, QRZ and Club Log from one place, and the duplicate problem mostly goes away.

Before importing, set up a rule for the contest data. Some loggers will happily put an exchange like a serial number or section into the comment or notes field. That's fine for archive purposes, but it can make later searches messy. Also check whether the import preserves the original QSO time. Some programs write the import time to the log's own timestamp field, which is harmless, but you want TIME_ON to stay intact because LoTW matches on it.

For the UDP issue, if the WSJT-X UDP server is set to a multicast address, several listeners can receive the same stream. A single unicast target is the more fragile setup. Test with every program open at once, log a few QSOs and confirm each one records them exactly once.

One caution on dupes: dupe rules belong to the contest, not the program. In some contests a station can be worked once per band, in others once per band and mode group, and in a few once for the whole event. Select the right contest definition at the start, because changing it midway can leave the dupe sheet disagreeing with the score summary.

  • Moderators

On the contest side, what usually decides the stack is how well the pieces handle the real-time part, which is CAT, band map, rotator and dupe checking, rather than how pretty the log is.

For the band map, spots from a telnet cluster or the Reverse Beacon Network are only useful if they match frequency and mode behavior. If the radio is on a split or in RIT, the band map can show a spotted station slightly off from where you are tuned. Check that the logger is reading the transmit frequency when you're working split, because the wrong frequency in the log can cause a bad match at the checker. Marking spots as worked or as a needed multiplier works only if the contest and the band map share the same dupe database, which is a good reason to keep spotting inside the contest program rather than a second window.

For rotator control, the common arrangement is that the logger sends a bearing to the rotator through its own interface or a helper such as PstRotator. Make sure the helper isn't also trying to talk to the same port the logger uses. Short and long path buttons are worth testing before the contest, not during it.

The same goes for DXKeeper, HRD Logbook and Logger32. They can all work well as a master log. The tradeoff is how tightly each is tied to its own radio control and ecosystem. DXKeeper is part of the DXLab suite, where Commander and the other apps expect to talk to each other. HRD ties logging to the rest of the HRD package. Logger32 is a more self-contained logger with its own interface options. The practical test is simple: export a full ADIF from the program, import it into something else, and see how many fields survive. If it survives that round trip, you aren't locked in.

Last, for submission, don't wait until the deadline. Upload the Cabrillo file early enough to read the confirmation message or log-checking report. If the checker complains about a callsign, category or exchange format, you want time to fix the header and resubmit.

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.