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

Logging workflow for contests and daily operating: N1MM+, WSJT-X, Log4OM, ADIF, Cabrillo, LoTW and QRZ

ci_cover.jpg

Question for the group about keeping contest logs and everyday logs from turning into a mess. The scenario is a station that runs N1MM Logger+ for contests, WSJT-X for FT8 and FT4 the rest of the year, and wants one "master" log in something like Log4OM, DXKeeper or HRD Logbook. The master log would feed LoTW, QRZ and Club Log.

Three things seem to cause most of the trouble:

1. Where the master log lives. N1MM+ is built around one database per contest, and it is excellent at dupe checking, band maps, multipliers and Cabrillo output. It is not designed as a lifetime logbook. The usual pattern is to treat each contest database as disposable, export ADIF at the end, and import that into the long-term logger. That leaves open how to avoid duplicate records if the same ADIF gets imported twice, and how to deal with contest-specific exchange fields that land in odd ADIF tags.

2. Digital modes. WSJT-X writes its own wsjtx_log.adi and can also send logged contacts by UDP. Which program should be the one that actually receives the QSO: N1MM+, Log4OM, or a helper in between? If two programs both log the same FT8 contact, the duplicate cleanup afterwards is tedious.

3. Uploads. LoTW needs TQSL and a signed file with a station location that matches where the radio actually was. QRZ and Club Log work from ADIF or API uploads. What is a sane order of operations so a bad import does not get pushed to three services?

Also open: what is the cleanest way to share CAT control between the logger, WSJT-X and a rotator program without fighting over the COM port?

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On CAT, the rule is that only one program can open a physical serial port. Everything else has to talk to that one program or to a splitter. Common patterns:

Let a rig-control layer own the port (flrig, Hamlib's rigctld, OmniRig, or DXLab Commander if you use DXKeeper). Then point the logger and WSJT-X at it as clients. Alternatively, use a virtual serial port pair or splitter so each program gets its own virtual port. The rig-control layer approach is usually more stable, because a splitter adds one more thing to break when Windows renumbers ports.

For PTT and keying, check whether you want it through CAT, a separate RTS/DTR line, or a hardware interface. Contest CW and digital modes often use different methods, so test each mode before the event, not during it. Also confirm baud rate, stop bits and the rig's CAT menu settings match on both ends.

For rotators, treat it the same way. One program talks to the controller (for example PstRotator or the controller's own software), and the logger sends bearings to it. If the logger shows a beam heading but the rotor does not move, check whether another program is holding the port or whether the controller expects a different protocol.

On the WSJT-X side, N1MM+ can receive logged-contact broadcasts from WSJT-X over UDP, and WSJT-X has a Reporting tab with options for logged-contact ADIF broadcast. The ports on both ends have to match, so read the current documentation for both programs before relying on it. Then pick one program as the receiver and leave the other logging paths off. Running JTAlert, GridTracker and a logger all auto-logging the same QSO is a classic source of duplicates.

  • Moderators

On the log-handling side, here is a sequence that limits damage.

Contest end: Check the log inside N1MM+ first: dupes, bad callsigns, wrong band or mode, time errors. The clock matters. Cabrillo times are UTC, and a computer clock that has drifted can cause busted-QSO penalties and mismatches in the sponsor's cross-check. Then generate the Cabrillo file for the sponsor. Cabrillo is a contest-submission format with a header (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND and so on) and QSO lines in an exact column layout. It is not an ADIF substitute. Always read the specific contest's rules for categories, exchange format, deadline and upload method, since sponsors differ, and run the file through the sponsor's checker if they offer one.

Separate step, ADIF export: Export ADIF for the master logger. Before importing, back up the master log. Look at what the import does with fields like MODE and SUBMODE (FT4, for instance, is represented as MFSK with a submode), band, frequency, and the exchange fields (STX, SRX, SRX_STRING and app-specific tags). Import a small test file first. Most loggers have a duplicate-detection option on import, which usually keys on call, band, mode and time within a tolerance. Use it, and spot-check afterwards.

Then uploads: Do LoTW through TQSL. The station location (DXCC entity, grid, CQ and ITU zones) must match where you operated. Portable and contest-expedition logs are the ones that most often get signed with the wrong location. LoTW only accepts files signed by TQSL, so an ADIF cannot be sent raw. QRZ and Club Log accept ADIF uploads or API-based sync, and both can be done from Log4OM, DXKeeper or HRD Logbook. The exact account requirements and API-key setup change over time, so check each service's current help pages. Do a small upload first to confirm the callsign, location and date range, since bad records are annoying to remove from three places.

One more tip: keep the country file (cty.dat, and Club Log's exceptions data) updated in each program. Mismatched prefix data is a common reason one program says a QSO is a new multiplier and another disagrees.

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.