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 96
SN 57
A 7
K 2 Quiet
X-Ray B3.7
Wind 446.6 km/s
Aurora 3
Updated 17:30 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 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 general logging + contest use, anyone running both?

so ive been using Log4OM for about two years now for everyday logging and i genuinely like it, the interface makes sense to me and the QSL manager stuff is decent. but every time contest season rolls around i feel like im fighting it a little bit. a buddy of mine keeps telling me to just switch to N1MM for contests and keep Log4OM for day to day stuff but that means running two separate logs and then trying to merge stuff later which sounds like a nightmare honestly.

the other wrinkle is i run WSJT-X pretty regularly for FT8 and FT4, and right now i have that piped into Log4OM via the UDP stuff which mostly works but i've had it drop spots a few times and i cant always tell if its a WSJT-X thing or Log4OM thing. i tried exporting an ADIF and importing into N1MM once and it was kind of a mess, dupes everywhere and the timestamps were off for some reason.

anyone actually running N1MM as their primary contest logger and then using something else for the rest of the time, and how do you handle keeping it all straight? or am i overthinking this and should just commit to one thing

  • Replies 1
  • Views 31
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah this is kind of the eternal question isn't it. i went through the same thing a couple years back. what i ended up doing was just accepting that N1MM is basically the contest logger and i use it only for that. my everyday logging is in Log4OM and i keep them separate on purpose, like i dont even try to merge them anymore. at the end of a contest i just export the Cabrillo for submission and then separately export an ADIF if i want those QSOs in my main log, but honestly half the time i dont even bother because contest QSOs are kind of their own thing anyway.

the WSJT-X UDP issue you're describing, i had something similar and it turned out i had two programs trying to listen on the same port at the same time which was causing it to drop packets randomly. worth checking your port config if you havent already, make sure nothing else is binding to 2237.

i just use N1MM for everything including FT8 contests like FT8RN and stuff, it handles WSJT-X integration fine once you get the network message setup right. never really got into Log4OM tbh, tried it once and felt like it was doing too much if that makes sense. for regular dx logging outside of contests i just use the N1MM log and call it a day, less moving parts.

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.