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 C2.2
Wind 403.6 km/s
Aurora 2
Updated 23: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 contests — am i missing something with the WSJT-X integration

so ive been using Log4OM for general logging for about two years now and honestly love it for day to day stuff, the QRZ lookups work great and keeping track of my DXCC progress is way easier than whatever i was doing before. but every time contest season rolls around i end up switching back to N1MM and it feels like im maintaining two completely separate lives on my radio desk.

the thing thats been bugging me lately is the WSJT-X integration. i run FT8 pretty heavily during some of the bigger contests like CQ WW and i cant figure out if im better off just committing to N1MM full time or if Log4OM can actually handle the contest side of things without me wanting to throw the laptop out the window. ive read the Log4OM docs but they kind of assume you already know what youre doing with the contest module which, i dont really.

anyone run both and settled on one? or is the answer just use N1MM for contests and Log4OM for everything else and accept that ADIF exports between them are part of the workflow now

  • Replies 1
  • Views 56
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

honestly the two-logger setup is just kind of the accepted reality for a lot of people. N1MM is basically the standard for contesting and theres a reason it stays that way — the rate display, the dupe checking, the way it handles multipliers in real time, nothing else really touches it for that stuff. Log4OM is genuinely better for the everyday DX hunting and awards tracking side of things though so i get why you'd want both.

for WSJT-X during contests what i do is have WSJT-X log to N1MM directly via the UDP port, N1MM listens on 2237 by default and WSJT-X has the setting right there under reporting. works pretty reliably in my experience, occasionally it misses one if youre running fast but not often enough to stress about. after the contest i just export the N1MM log as ADIF and import it into Log4OM to update the master log. takes maybe ten minutes and its not as painful as it sounds once youve done it a few times.

the Log4OM contest module is fine for casual stuff but if youre doing anything serious i wouldnt try to run CQWW through it, you'll spend more time troubleshooting than operating

yeah the UDP integration between WSJT-X and N1MM is pretty solid, been doing it that way for a couple years. just make sure youre not also accidentally logging to a file at the same time or you end up with duplicates when you go to merge things later, learned that the hard way during last years ARRL DX

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.