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 B7.8
Wind 387.9 km/s
Aurora 3
Updated 01: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 contest logging — anybody running both?

so ive been using Log4OM for general logging for a couple years now and honestly i really like it for everyday stuff, the interface isnt too bad once you get used to it and the cloudlog sync works fine for me. but every time a contest comes around i feel like im fighting it. ive tried setting up the contest modules a few times and it just never clicks the way i want it to.

a buddy of mine keeps telling me to just use N1MM for contests and keep Log4OM for regular logging, which i guess makes sense since N1MM is basically built for nothing else. my question is whether anyone here is actually running that kind of dual setup and how much of a pain is it to keep the logs from getting fragmented across two programs. like do you just import the ADIF after the contest or is there some cleaner way to do it.

also separately — anyone using WSJT-X alongside this whole mess. right now WSJT-X logs to Log4OM via UDP and that works fine but i have no idea how that would play with N1MM running at the same time if i ever wanted to do a mixed mode contest. probably a disaster waiting to happen

  • Replies 1
  • Views 95
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah i run exactly that setup, N1MM for contests and Log4OM as the master log. after every contest i just export the ADIF from N1MM and import it into Log4OM, takes maybe five minutes and ive never had a duplicate problem that wasnt already a duplicate in real life. the only thing to watch is making sure your callsign and operator fields are set the same in both programs otherwise the ADIF merge gets a little weird with some of the fields.

for WSJT-X during a contest its honestly easier to just close Log4OM and point WSJT-X at N1MM directly, theres a UDP port config in WSJT-X and N1MM will accept it, they actually work pretty well together once you get the port numbers sorted. i think the default is 2237 for N1MM but double check that. the main thing is you cant have two programs both trying to grab the UDP broadcast from WSJT-X at the same time without a splitter and thats more trouble than its worth for most people

dont overthink the dual logging thing, lots of people do it. ADIF import after the contest is fine. Log4OM handles it pretty cleanly in my experience.

the WSJT-X thing is the part id actually be careful about though, ive had N1MM get confused with FT8 contacts during a contest that also had phone and CW segments, the serial numbers get wonky. probably fine if youre doing a purely digital contest but for something like a state QSO party where everyones on different modes it got messy for me real fast

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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.