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 chain for contests and daily operating: N1MM, WSJT-X, Log4OM, ADIF, Cabrillo and uploads

ci_cover.jpg

This thread is about connecting the pieces so you aren't cleaning up the log by hand after every weekend. A common layout uses a contest logger (N1MM Logger+ or similar) for the contest, WSJT-X for FT8/FT4, and a general-purpose log (Log4OM, DXKeeper, HRD Logbook or Logger32) as the master record. The master record then feeds LoTW, QRZ and Club Log.

The questions I'd like to compare notes on:

1. Where do you draw the line between the contest database and the master log? Do you import the contest ADIF after the event, or log everything live into one program?

2. CAT is the usual point of failure. Only one program can own a serial port at a time. What do you use to share the radio between the logger, WSJT-X and a bandmap: virtual port pairs, rigctld, OmniRig, flrig, or the logger's own digital interface? Rotator control raises the same question, and so does the rotator protocol (GS-232 and so on).

3. Dupe rules differ by contest. Some count a dupe per band, some per band and mode, and ARRL Sweepstakes counts one contact per station regardless of band. How do you make sure the logger's dupe setting matches the rules, especially for digital modes?

4. Before you submit a Cabrillo file, what do you check? Header category fields, exchange columns, UTC times and callsign format are all common causes of a rejected or mis-scored log.

5. For uploads, do you push LoTW, QRZ and Club Log from the master log only, or also straight from the contest logger? Duplicate uploads and a wrong station location in TQSL are the traps I know about.

Which parts of your setup are solid and which are still fragile?

  • Replies 2
  • Views 30
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the split between contest and master log, a common pattern is to keep the contest logger authoritative for the contest and treat the master log as a destination. Export ADIF from the contest logger when the event ends and import it, rather than trying to sync live. Before importing, check that the fields your master log needs are populated: STATION_CALLSIGN, OPERATOR for multi-op, MY_GRIDSQUARE, and the contest ID and exchange fields if you want them kept. Importing the same file twice is the most common mess, so use your program's duplicate check (call, date, time, band and mode) or back up first.

For WSJT-X, remember it writes wsjtx_log.adi, and it can also broadcast logged QSOs over UDP. N1MM+, Log4OM and JTAlert can listen to that broadcast, so you can log automatically without CAT conflicts in the log path. Two loggers listening at once will double-log, so pick one listener. Also check how your logger handles FT4. Depending on the ADIF version, it may appear as MFSK with submode FT4 rather than as its own mode, and that can cause odd results in award tracking and in LoTW matching.

For CAT sharing, an option is a network layer such as Hamlib's rigctld. WSJT-X can use the Hamlib NET rigctl setting, and other programs talk to the same daemon. The alternative is a virtual serial port splitter, which works but adds another thing that can hang. Set baud rate, CI-V address (for Icom) and stop bits once, and write them down.

  • Moderators

On Cabrillo and submission, the file is only as good as the contest definition behind it. Read the sponsor's rules for the exchange, categories and Cabrillo requirements. Then open the generated .log file in a text editor. Look at the header (CONTEST, CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER and so on), then at the QSO: lines. Frequency is in kHz, times are UTC, and the sent and received exchanges must sit in the columns the sponsor expects. A serial number or section in the wrong field can cost points even though the QSO count looks right.

Dupes are another place to be careful. Check the rules for your contest and compare them with your logger's setting. Field Day-style events treat CW, phone and digital as separate mode groups per band. Some contests count mode, some don't. Most contest loggers have an option to work dupes anyway, which is fine, but check how the dupes are marked in the file you submit. Super Check Partial (the master.scp file) and a recent cty.dat help catch busted calls and wrong prefixes before they reach the log. Keeping both updated is cheap.

For bandmaps, spots from a cluster or a skimmer feed are only hints. Busted spots happen, so confirm the call on the air before logging. A bandmap that colors new multipliers and dupes is useful, but only if the multiplier definitions for that contest are loaded.

For LoTW, the signing step needs the right station location, with correct DXCC entity, grid and zones. A QSO logged from a different location than the one you select in TQSL will be signed with the wrong data. LoTW matches on call, band, mode and a time window of about 30 minutes, so a clock that is off by more than that will quietly fail to match. QRZ and Club Log uploads use API keys or credentials. Check what each service requires for your account type and keep them private.

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.