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 clean log across N1MM Logger+, WSJT-X and Log4OM: CAT sharing, ADIF/Cabrillo, and LoTW/QRZ/Club Log uploads

ci_cover.jpg

This thread is for comparing workflows when the same station uses more than one logger. A common setup is N1MM Logger+ for contests, WSJT-X for FT8/FT4, and Log4OM (or DXKeeper, HRD Logbook, Logger32) as the long-term logbook that feeds LoTW, QRZ and Club Log. It works, but the failure points are predictable: a serial port that only one program can open, ADIF fields that don't map cleanly, and duplicate QSOs after an import.

Here is the outline I'd start from, and I'd like corrections.

First, decide which program is the master log. A contest logger is optimised for fast entry, dupe checking and Cabrillo output, so it's usually the master for that contest only. The general-purpose logbook (Log4OM, DXKeeper, etc.) is better as the permanent record because it handles award tracking, QSL status and online-service sync. After each contest, export ADIF from N1MM+ and import it into the long-term log, rather than trying to keep both live-synced.

Second, CAT and rotator control. Most rigs expose one CAT port, and only one application can hold it at a time. The usual ways around that are a CAT hub or sharing layer (OmniRig, FLrig, Hamlib's rigctld, DXLab Commander, or HRD), or virtual serial port pairs. Rotators follow the same rule: one program owns the controller, and others talk to it through a rotator server such as rotctld or a utility like PstRotator. WSJT-X can talk to Hamlib, OmniRig, Commander or HRD, so pick one hub and point every program at it instead of fighting over COM3.

Third, the export chain. For a contest, generate the Cabrillo file from N1MM+ and check the header lines (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER, CATEGORY-MODE, CLUB, and so on) against that contest's current rules, because sponsors differ on accepted category values. For the permanent log, use ADIF. Before importing, confirm that STATION_CALLSIGN, OPERATOR, MY_GRIDSQUARE, MODE and SUBMODE are populated, since LoTW and Club Log rely on them.

Fourth, uploads. LoTW needs TQSL with a station location that matches the callsign, DXCC entity, grid and zones for that operation. LoTW generally ignores QSOs it has already received, but a wrong station location will still produce mismatched or unusable uploads. QRZ Logbook and Club Log both use API-style uploads and need credentials or keys set up in the logger. Test with a small batch before pushing a whole contest weekend.

Fifth, dupes. N1MM+ applies the contest's dupe rules, typically per band, or per band and mode. A general logbook's dupe checker is a different thing, and importing the same ADIF twice can create real duplicate records unless the import has duplicate detection enabled. Keep the original ADIF file and import into a test log first.

Questions for the thread: Which program do you let own CAT during a contest, and what do you use to share it? How do you get WSJT-X QSOs into a contest log without double-logging? And what's your routine for checking a Cabrillo file before upload?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On CAT, the cleanest pattern is to give the rig to exactly one program and make everything else a client of it. If you have WSJT-X plus a contest logger, point both at the same hub (OmniRig, FLrig, or a rigctld instance) instead of using a virtual-port splitter, which adds one more thing to break at 0000Z. If you do use virtual ports, keep the baud rate, data bits and stop bits identical on both sides, and check that PTT and CW keying lines aren't also getting passed through.

For digital contest modes, keep the audio and PTT path in mind too. If WSJT-X keys the rig through CAT or a USB codec while N1MM+ also sends CW or voice-keyer commands, you can end up with two programs fighting over PTT. Decide which application owns transmit for each mode and disable the other's PTT method.

Also check the PC clock. FT8 and FT4 need accurate time, and a log with sloppy timestamps can fail to match on LoTW or in a sponsor's cross-check. Sync before the contest starts, not during it.

For the WSJT-X to contest-logger handoff, the options are either the WSJT-X UDP broadcast (which Log4OM can listen to directly) or a relay tool that sits between them. Whichever you use, run a few test QSOs and confirm the callsign, report, grid, band, mode and time all arrive intact before the contest starts.

  • Moderators

On the post-contest side, I'd separate the two tasks: submitting the contest entry, and updating your permanent log and QSL services. They use different files and don't need to happen in the same session.

For submission, open the Cabrillo file in a text editor and read it before uploading. Check that the callsign and category lines match what you entered, that the QSO lines have the exchange in the order the sponsor expects, and that the band and mode fields aren't blank. Then upload through the sponsor's page and wait for the confirmation or robot reply, and read it. A confirmation that says the log was received is not the same as a log that parsed cleanly. If there are format warnings, fix the header or the exchange fields and resubmit before the deadline.

For the permanent log, import the ADIF export into a copy first. Look at a sample of records for the right MODE and SUBMODE (FT8 and FT4 are the ones that tend to cause trouble), the right band, and the contest exchange fields. Then turn on duplicate detection and import into the real log.

Then upload to LoTW through TQSL, with the correct station location selected. Next, push to QRZ and Club Log through the logger's built-in sync, if it has one. Watch for rejected QSOs in the response, because a bad callsign or an unsupported mode usually shows up there first. If the logger supports it, record each QSO's upload status so you can see what's been sent and what hasn't.

One last tip: keep the untouched original ADIF and Cabrillo files somewhere safe. When a sponsor, LoTW or Club Log disputes something later, the original is your reference.

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.