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? Handling N1MM Logger+, WSJT-X and Log4OM without a mess at upload time

ci_cover.jpg

Opening a discussion on log management. Many stations end up with several programs writing QSOs: N1MM Logger+ for contests, WSJT-X for FT8 and FT4, and a general logger such as Log4OM, DXKeeper, HRD Logbook or Logger32 for everyday use. Each one has its own database, and the trouble shows up later, when you export for LoTW, QRZ, Club Log or a contest sponsor.

Here are the points where this usually goes wrong, so we can compare approaches.

1. Where should the master log live? One option is to treat the general logger as the permanent record. Contest logs from N1MM+ and WSJT-X's own ADIF file are then imported into it after each session. The other option is to keep each program's database as its own record and merge only for uploads. The first option makes dupe checks against your whole history easier. The second keeps the contest database clean, which matters because N1MM+ expects each contest to be its own self-contained log.

2. ADIF round trips. ADIF is the common format, but programs do not always handle it the same way. Check how modes and submodes are mapped. FT8 is a mode in current ADIF, while FT4 is normally MFSK with the submode FT4. Older software or older import filters may expect something else. Look at how the import treats fields such as STX/SRX, contest ID, grid squares, TX power and comments. Also watch for duplicate imports. Importing the same ADIF twice into a general logger without a dupe filter on import (call, band, mode, date and time) can fill the log with repeated entries, and those repeats then go to LoTW or QRZ.

3. Cabrillo is not just ADIF with a different extension. Cabrillo is a text format with a header (CONTEST, CALLSIGN, CATEGORY-* and so on) and QSO: lines whose exchange layout depends on the contest. The sponsor's rules decide what is valid. Generate it from the contest program, which knows the exchange layout, rather than converting from a general ADIF. Always open the file in a text editor before submitting. Check the callsign, category, power class, claimed score, and that the QSO time and frequency columns look sane. Then read the sponsor's page for the upload method, since some use a web robot and others use email.

4. CAT and rotator sharing. A serial port can generally be opened by only one program at a time. If WSJT-X and your logger both need frequency and mode, you need a rig control layer (for example Hamlib's rigctld, Omni-Rig on Windows, or FLRig) or a virtual serial port splitter. A stray DTR/RTS setting can also key the transmitter, so check PTT behavior on a dummy load first. Rotator control has the same issue: decide which program owns the rotator port and have the others talk to it over a network interface or a rotator control program.

5. UDP and WSJT-X. WSJT-X can send decoded and logged-QSO messages over UDP, and the default is localhost port 2237. Only one program can bind that port unless you configure multicast. If you run a logger and a helper application together, check this setting before wondering why one of them has no data.

6. Band maps and dupe checking. Spots from a cluster or Skimmer-style feed are only as useful as their worked/dupe status. Check that the band map colors a station as worked only for the right band and mode category. In a contest, check that the dupe rules in the software match the contest rules. Some contests count a repeat contact per band, some per band and mode group, and some have extra rules.

7. Upload hygiene. For LoTW, TQSL has to be set up with the correct callsign certificate, station location and grid or zone data. A wrong location can cause mismatches later. For QRZ and Club Log, use the logbook API key or the app password the site provides rather than your main login, and check what your account type requires. Keep a note of the last uploaded date or QSO so you do not upload the whole log every time.

Do you keep one master log and import into it, or do you keep separate logs and merge selectively? And what is your sanity check before you submit a Cabrillo file?

  • Replies 2
  • Views 17
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

For me the deciding factor is what you do with the log afterward. If you chase awards, a single long-term logbook is worth the effort, because worked-before status, DXCC/WAS progress and confirmation tracking all depend on having everything in one place. In that setup the contest program is a short-term tool. You run the contest in its own database, export ADIF when you finish, and import it into the general logger once, with a dupe filter active.

A few things I would check on the import. Make sure the band and mode columns are not being rewritten into something different, especially for digital modes. Confirm that contest exchange data lands in sensible fields and does not overwrite your normal comment or name fields. Keep the original ADIF file untouched in a backup folder. If an import goes wrong, you can restore a copy of the logbook and try again instead of trying to fix individual records by hand.

The other thing I would flag is clock accuracy. FT8 and FT4 depend on a well-synchronized PC clock, and the time in the log goes out to LoTW and QRZ. A clock that is a few seconds off can hurt decoding, and a bad timezone setting can put QSOs on the wrong date. Log in UTC and use a time sync tool.

  • Moderators

On the CAT side, I would start by drawing the control chain on paper: radio, then one program that owns the port, then everything else connecting through that. Most of the intermittent problems come from two programs fighting over the same COM port, or from a virtual port pair that was set up with different baud rates on each end. The rig and the software need the same baud rate, data bits, stop bits and handshake setting, so check those against the radio menu before blaming the program.

For Cabrillo, the habit that saves the most trouble is reading the generated file before upload. Look at the header, then spot-check a few QSO: lines against what you remember working. Common problems are the wrong category, a missing or extra operator callsign, a power class that does not match the entry, and exchange fields that are blank because a QSO was entered without the required report or serial number. Some sponsors have a log checker or acknowledgement page, so after upload see whether your log was accepted before the deadline instead of assuming it was.

For club-level logs, such as a club station or a multi-operator entry, agree beforehand on how logs are merged. Everyone should be on the same contest and category, the same UTC clock, and the same naming conventions for operators and stations. Merging several ADIF files after the fact is where duplicate and out-of-order QSOs show up. If you run multiple stations on a network, check the contest program's networking features and test the multi-op setup before the contest starts.

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.