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 128
SN 73
A 6
K 1 Quiet
X-Ray B8.2
Wind 388.9 km/s
Aurora 2
Updated 02: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 logging plus contest use — worth having both installed?

so ive been using Log4OM for general logging for about two years now and honestly i like it a lot, the interface took some getting used to but the award tracking stuff is really nice and it plays well with WSJT-X through the JTDX integration or whatever its called. my issue is contest season is coming up and everyone keeps telling me i should just use N1MM for contests which i totally get, N1MM is basically the standard for that stuff.

my question is whether its a pain to have both installed and switch between them or if there's some trick to keeping your logs synced up. like if i work a bunch of stations during a contest in N1MM, getting those QSOs into Log4OM afterward without duplicating stuff or messing up the ADIF import seems like it could be a headache. has anyone actually got a clean workflow for this? i tried importing an ADIF from a previous contest once and it was mostly fine but a few dupes snuck in and i had to clean it up manually which was annoying.

also side question — does anyone run WSJT-X feeding into N1MM during something like a digital contest or do most people just log FT8 separately and merge later. feel like ive seen conflicting info on this.

  • Replies 1
  • Views 117
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah i run both and honestly it's not that bad once you get used to the rhythm. N1MM stays off unless i'm actually contesting, Log4OM handles everything else. after a contest i just export the ADIF from N1MM, then in Log4OM i do the import with duplicate checking turned on — it's under tools or options somewhere, been a while — and it catches most of the dupes based on callsign plus band plus mode. not perfect but close enough that i only ever have to fix a handful manually.

the WSJT-X thing is a bit of a rabbit hole. technically you can have WSJT-X log to N1MM during a contest but the way the two programs handle QSO data isn't always clean, especially for something like ARRL digital where the exchange fields are a bit weird. i've seen guys do it but i just keep them separate and merge the ADIF at the end. less headache.

im in a similar boat actually, been meaning to sort this out before sweepstakes. one thing i noticed with Log4OM is if you set the duplicate check to look at date range instead of all-time it can let stuff through from the same contest, so worth double checking that setting before you import anything. took me an embarassing amount of time to figure out why i kept seeing the same calls twice in my log after field day last year lol.

honestly for straight up FT8 outside of contests i just let WSJT-X log to its own file and then import periodically, works fine. never tried wiring it into N1MM mid-contest though so cant help you there.

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.