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 412.9 km/s
Aurora 1
Updated 14:00 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-radio logging chain: N1MM Logger+ for contests, WSJT-X for digital, and a main log with LoTW, QRZ and Club Log uploads

ci_cover.jpg

This is a workflow discussion about keeping one clean master log when several programs touch the same radio. A common arrangement has N1MM Logger+ for contests, WSJT-X for FT8 and FT4, and a general-purpose logger such as Log4OM, DXKeeper, HRD Logbook or Logger32 as the permanent record. The same QSOs can end up in three places, and that is where the trouble starts: duplicate imports, wrong modes, wrong grids, and uploads that LoTW or Club Log reject.

Here is the chain I would sketch, with the weak points marked. Corrections are welcome.

1. CAT and rotator control. Only one program can normally own a serial port. If N1MM Logger+ and WSJT-X both need frequency and mode, you need a sharing layer. Options include Hamlib's rigctld, flrig, Omni-Rig, DXLab Commander, or a virtual serial port splitter. Which one works depends on the radio and driver. Rotator control has the same ownership problem. Decide which program talks to the rotator hardware and let the others send commands through it, rather than having several programs open the port.

2. Where each QSO is born. For a contest, N1MM Logger+ should be the source of truth for that contest. Its band map, dupe sheet, and exchange parsing exist to support that. For FT8 outside a contest, WSJT-X logs to its ADIF file, and many loggers can take QSOs live over UDP. If you work a digital contest through WSJT-X, check whether you want its UDP/N1MM broadcast feeding the contest logger, or whether you will import the ADIF afterward. Importing afterward is simpler, but you lose live dupe checking.

3. Moving data with ADIF. ADIF is the interchange format between loggers, but it is not perfectly uniform. Check what happens to these fields on import: MODE and SUBMODE (FT4 is handled differently from FT8 in some programs), STATION_CALLSIGN versus OPERATOR, MY_GRIDSTATE, MY_CQ_ZONE and ITU zone, and contest-specific fields like STX, SRX, and CONTEST_ID. Before bulk-importing a whole weekend, try a handful of QSOs and compare them field by field in the destination logger.

4. Cabrillo is for the contest sponsor, not your archive. It is a submission format, and the exact content depends on the contest rules. Generate it from the contest logger, not from the master log. Then check the header (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER, CATEGORY-MODE, CLUB, and so on) and the exchange columns. Digital QSOs are normally written with the Cabrillo mode code DG, but individual contests can differ, so read the rules. Most sponsors have a web upload, and some accept email. Keep the generated file along with the original N1MM database for a while in case the log checker has questions.

5. LoTW, QRZ and Club Log. LoTW needs TQSL and a station location that matches the operating location: DXCC entity, grid, and zones. If you operated from another place, create a separate station location rather than editing the home one. QRZ logbook uploads use an API key tied to the logbook, and access requirements may depend on the account level, so verify them on QRZ. Club Log is useful for DXCC tracking and matching, and it has its own upload and API options. Be careful about uploading the same QSOs from two programs. Pick one program as the uploader for each service and let the other ones stay quiet. Otherwise you get duplicates or confusing confirmation states.

6. Club-level logging. If a club station or multi-op group is involved, there is another layer: network settings between N1MM instances, operator callsigns, and who submits the final log. The entry should be assembled from one merged database, not from several partial exports.

What are people using as the master log, and where do you draw the line for imports? Do you let the contest logger upload to LoTW directly, or always route through the master log first?

  • Replies 2
  • Views 45
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I would keep the contest logger away from the online services except for the contest submission itself. A master log that does the QRZ, LoTW and Club Log uploads gives you one place to check for upload state, and it keeps the same QSO from being sent from two different databases with slightly different fields.

For the import step, the thing to check most carefully is the station information. LoTW will happily sign a record that is internally inconsistent, and the problem only shows up as a mismatch later. If the exported ADIF has a missing or wrong MY_GRIDSQUARE, or a missing station callsign, fix that in the file or in the logger before it reaches TQSL. A text editor is fine for a small ADIF file, but for a large batch use the logger's own bulk edit tools if it has them, so you do not break the record structure.

Also separate the idea of an ADIF import from a log merge. Some programs check for duplicates on import using callsign, band, mode, and time within a tolerance. That is helpful, but the tolerance and the mode comparison are not the same everywhere. FT8 timestamps can sit near a boundary of the window, and a QSO logged at the start and end of a transmission can differ by a minute. Run a test import into a scratch database and see what the program calls a duplicate.

  • Moderators

On the CAT side, the question I would ask first is whether the radio or its driver exposes more than one control path. Some radios present multiple virtual serial ports over USB, but how they are used differs between models and drivers, so check the manual. If you only get one CAT port, rigctld or flrig as a broker is usually less fragile than splitting the serial port at the OS level. WSJT-X can talk to Hamlib's network rig control, and N1MM Logger+ has its own rig options, so check what your version supports before committing to a design.

For band maps and dupe checking, remember that N1MM's band map is only as good as the frequency it reads and the spots feeding it. If you also have a digital program changing the VFO, you can end up with the band map jumping around, or QSOs logged with the wrong frequency. In a contest weekend I would close or pause the other programs that can retune the radio, unless you deliberately want them both in the chain.

For the rotator, N1MM can send a bearing from the entry window or from a band map spot, but a conflict with other rotator software is the same story as the radio port: one owner for the hardware. If DXKeeper, Log4OM or HRD is also configured to command the rotator, turn that off while the contest logger is running.

One last point on submission: after you generate Cabrillo, open the text file and look at the first few QSO lines before you upload. Check callsign, frequency, mode code, date and time in UTC, and the sent and received exchange. A quick look catches most problems that otherwise show up as a rejected or heavily penalized log.

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.