Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

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.
Solar
SFI 147
SN 141
A 10
K 2 Quiet
X-Ray C1.0
Wind 430.6 km/s
Aurora 1
Updated 00:00 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 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

N1MM vs Log4OM for everyday use — do people actually switch between them for contests?

 Loading...

so ive been using Log4OM for about a year now for general logging and i really like it, the interface makes sense to me and the QSL tracking stuff is pretty solid. but every time a contest rolls around everyone seems to act like N1MM is the only option and i kind of just... go along with it and fire up N1MM even though i dont really know it that well.

my question is whether people actually maintain two separate logging setups or if theres a smarter way to handle this. like right now i have WSJT-X feeding into Log4OM via UDP for FT8 and that works fine day to day, but when i do something like the ARRL DX contest i switch over to N1MM and then i have to manually import the ADIF afterward and sometimes the duplicate checking gets weird.

is that just the way it is or am i missing something obvious. feels like theres probably a cleaner workflow that i havent figured out yet

  • Replies 1
  • Views 3
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah that's pretty much how most people run it honestly. N1MM is just so purpose-built for contesting that trying to force Log4OM into that role doesnt really make sense, the exchange logging and rate tracking and all that just isnt the same. i've tried doing contests in other software and you end up fighting the tool instead of working the pile.

the ADIF import thing after the fact is annoying but its not that bad once you set up a filter to check for dupes before you merge. what i do is export from N1MM right after the contest ends, open it in a text editor real quick and check the header info is clean, then import into Log4OM with the duplicate detection set to strict. havent had a serious problem with it in a while. the only time it got weird for me was when i had some FT8 QSOs in Log4OM that also showed up in the contest log because i was running both modes during the same event, that confused things for a bit.

the WSJT-X to Log4OM UDP thing works well but just make sure your port settings arent conflicting if you ever try to run N1MM at the same time, i did that once by accident during a VHF contest and had QSOs going to both logs and neither was complete. took me a while to figure out why my dupe checking felt off mid-contest. just something to watch out for if you ever try to run FT8 alongside SSB or CW in a mixed-mode event.

Guest
Reply to this topic...

Account

Navigation

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.