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.
☀ Solar
SFI 121
SN 99
A 11
K 3 Unsettled
X-Ray C2.4
Wind 432.2 km/s
Aurora 4
Updated 08:30 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Fair 12/10m Fair
Night 80/40m Fair 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

N1MM vs Log4OM for contests - am i missing something with the integration

so ive been using Log4OM for general logging for probably two years now and i really like it for day to day stuff, the interface is clean and the cloudlog sync works great for me. but every time contest season rolls around i end up switching back to N1MM and its kind of annoying having to maintain two setups.

the thing is i tried running WSJT-X through Log4OM during a recent FT8 contest and it was kind of a mess honestly. the UDP port sharing kept conflicting and i had to restart WSJT-X like three times before it settled down. meanwhile N1MM just... works. you point WSJT-X at it and it picks up the QSOs no problem. not sure if thats a Log4OM config issue on my end or if N1MM is just genuinely better at contest integration

anyone run both and figured out a workflow that doesnt involve switching back and forth? or is the consensus just that N1MM is the contest tool and Log4OM is for the shack log and thats that

  • Replies 1
  • Views 92
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah thats basically how i run it. N1MM for contests full stop, Log4OM for everything else. i spent probably a weekend trying to get Log4OM to behave properly during the ARRL DX contest last year and eventually just gave up. it's a great piece of software but it wasnt really built to be a contest engine the same way N1MM was. N1MM has years of contest-specific stuff baked in, the multiplier tracking, the so2r support if you run that, the bandmap integration - its hard to compete with that.

the WSJT-X conflict thing you're describing sounds like a UDP port issue. Log4OM and WSJT-X both want to talk on 2237 by default i think, you can change the port in WSJT-X settings but its fiddly. still, even if you fix that, during a contest i want N1MM. after the contest i import the ADIF into Log4OM and thats my permanent record. two tools, two jobs.

I came at this from the opposite direction - started with N1MM because thats what the club used for field day and then picked up Log4OM later when i wanted something nicer for tracking DX confirmations and LoTW stuff. Honestly never even tried to use Log4OM for a real contest so cant speak to that.

What i will say is the ADIF import between them has been pretty painless for me. after a contest i just export from N1MM and drag it into Log4OM and it dupes fine, havent had missing fields or anything weird. so the two-tool workflow is at least not painful once you get used to it

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.