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 log, many tools: keeping N1MM+, WSJT-X, Log4OM and the LoTW/QRZ/Club Log uploads from fighting each other

ci_cover.jpg

Most logging problems seem to come from having too many programs that each believe they own the log, the radio, or the COM port. This thread is for comparing how to split those jobs. Below is a layout to react to, followed by the points where it tends to break.

Contest log versus general log. Treat the contest program as a per-event database. N1MM Logger+ keeps one database per contest, with its own dupe sheet, multiplier tracking and exchange parsing. At the end you generate the Cabrillo file for the sponsor and export ADIF for your permanent log. The permanent log, whether Log4OM, DXKeeper, HRD Logbook or Logger32, takes that ADIF import. Treat the contest program as the source of truth for the contest, and the main logger as the source of truth for everything else.

WSJT-X in the middle. WSJT-X writes its own wsjtx_log.adi and also broadcasts decoded and logged-QSO messages over UDP. The default is 127.0.0.1 port 2237. The trap is that two programs cannot always listen on the same unicast port. If you want a logger plus something like a decode viewer or alert tool, use a multicast address in the UDP server settings, or put a relay in the chain. Also make sure the logger is not set to receive from WSJT-X while you also import wsjtx_log.adi by hand, or you will log every FT8 QSO twice.

CAT and rotator control. A serial port can usually be opened by only one program. If the logger, WSJT-X and a rotator or band-decoder utility all want frequency and mode, pick one owner. Options are the logger itself, a CAT manager (Commander in the DXLab suite, HRD, or Omni-Rig/Hamlib's rigctld), or a virtual serial port splitter. Every extra layer adds a place for baud rate, stop bit or PTT mismatches. Rotator control is similar: use one program that talks to the controller, and have the logger send bearings to it rather than opening the port too.

Uploads. LoTW uploads go through TQSL, so the station location (callsign, grid, DXCC entity, CQ and ITU zones) must match the certificate and where you operated. A wrong location in a signed batch is the classic way to produce QSOs that never match. QRZ Logbook and Club Log both take ADIF and have their own API or key mechanisms for automatic uploads. Be deliberate about whether the contest program, the main logger, or both are doing automatic uploads. Pick one path per service.

Fields that matter in ADIF. Check that STATION_CALLSIGN, OPERATOR, MY_GRIDSQUARE, MODE/SUBMODE, BAND and the QSO date and time in UTC survive the export and re-import. Digital submodes are the usual casualty, because programs map them differently. FT4, for example, has been handled as a MODE or as a SUBMODE depending on the software and ADIF version in use.

Before you submit a contest log. Confirm that the Cabrillo header matches the sponsor's current rules. That means the CONTEST name, category lines, claimed score and operator or club fields. Check that the exchange columns look right in a few QSO: lines, and that time and frequency are in the units the sponsor expects. Then use the sponsor's upload page or log robot, and keep the confirmation.

Where does your workflow split differently? In particular: who owns CAT, where do you do dupe checking when running both a contest program and a main logger, and do you let anything auto-upload during a contest?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the CAT question, the cleanest arrangement is usually one program that talks to the radio and shares that connection out to everything else. If the radio supports it through a USB interface, remember that many rigs present two virtual COM ports, one for CAT and one for digital or CW keying. Keep track of which is which, because swapping them produces symptoms that look like logging bugs: the band map follows the radio but PTT is dead, or the logger shows frequency but never changes mode.

For dupe checking, the contest program should be the only authority during the event. A general logger's "worked before" indicator is based on all-time history. The contest's dupe rules depend on the sponsor, such as per band, per band and mode, or per day. Make sure the contest database is set up for the right contest before the first QSO, since changing it mid-event can leave you with a bad dupe sheet.

One more point on the band map: spot sources can include cluster nodes and skimmer feeds. Spots on a band map can be off in frequency or wrong in callsign, so treat them as leads to verify with your own ears or decoder, not as logged contacts.

  • Administrators

I'd add that time is the quiet dependency across the whole chain. FT8 and FT4 decoding depend on an accurate PC clock, and LoTW matching depends on QSO times being close enough between both logs. So whatever sync method you use, confirm it is actually running before a contest. A clock that has drifted can make a perfectly good log mismatch on the other end.

For the post-contest flow, I'd do it in this order. First, generate Cabrillo and submit it, since that has a deadline. Second, export ADIF from the contest program and look at it in a text editor or a viewer before importing. Check mode, submode, the exchange fields and the station fields. Third, import into the permanent log and run its own duplicate detection on the import. Only after that, upload to LoTW, QRZ and Club Log, so a bad import does not propagate to three services you then have to clean up.

For multi-operator or club events, also decide up front which callsign goes in STATION_CALLSIGN and which goes in OPERATOR. That affects how the QSOs look in Club Log and LoTW, and it is much harder to fix after the upload.

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.